Set Event requirement information for Applications Manager and Oracle 18c

Products

• CA Automic Applications Manager (AM)

Issue/Introduction

For Applications Manager version 9.3.0 and 9.3.1, the below "set event" is required for Applications Manager to work with Oracle 18c.

This is no longer required in Applications Manager version 9.3.2 and above when compatibility for both 18c and 19c were added.

This article is was written to reference the legacy requirement as the noted requirement is was removed from all online documentation after Applications Manager 9.3.2 was released.

Reference to the below requirement is still available via offline documentation for Applications Manager 9.3.0 and 9.3.1.

Environment

Release : 9.3

Component : APPLICATIONS MANAGER

Resolution

Notes for Oracle 18c
In Oracle 18c, some system views that Applications Manager depends on have changed. It is necessary to set an Oracle event to revert the behavior changes for Applications Manager to function properly. This is a DBA task. Please work with your DBA if needed to implement the changes at the database level. All SQL statements here are done in the SYS account of the container DB (CDB).

1. The database is started with the latest SPFILE in default location.

The default location of the SPFILE can be found by this:

SQL> show parameter spfile                                                       
NAME                                 TYPE        VALUE                           
------------------------------------ ----------- ------------------------------  
spfile                               string      /u01/app/oracle/product/18.0.0  
                                                 /dbhome_1/dbs/spfilecuidev18.ora

Back up this SPFILE

2. Change the SPFILE in the default location with the following:

SQL> alter system set event="10946 trace name context forever, level 65536" scope=SPFILE;

Warning! The scope can only be SPFILE, not BOTH.

3. Shutdown the database and restart:

SQL> STARTUP

4. To verify that the current system has the event set, run the following script:

SET SERVEROUTPUT ON                                                                                    
DECLARE                                                                                                
        l_event NUMBER:=10946;                                                                         
        l_level NUMBER;                                                                                
BEGIN                                                                                                  
                dbms_system.read_ev (l_event,l_level);                                                 
        IF l_level > 0 THEN                                                                            
            dbms_output.put_line ('Event '||TO_CHAR (l_event)||' is set at level '||TO_CHAR (l_level));
                ELSE                                                                                   
                    dbms_output.put_line ('Event '||TO_CHAR (l_event)||' not set');                    
        END IF;                                                                                        
END;                                                                                                   
/                                                                                                      

You should see:

SQL> Event 10946 is set at level 65536

5. In case you need to remove the event, do the following:

SQL> alter system set event="10946 trace name context forever,off" scope=SPFILE