ORA-24177 error after upgrading to Applications Manager 9.6

Products

• CA Automic Applications Manager (AM)

Issue/Introduction

After installing or upgrading to Applications Manag version 9.6, performance issues are seen including but not limited to Jobs not processing, updating statuses, or client not refreshing.

These behavior are accompanied with the below error seen either as a RmiServer pop-up message or seen in the RmiServer logs:

ErrorMsg: AwE-5001 Database Query Error
Details: ORA-24177: 1063
ORA-06512: at "APPWORX.AM_AQ", line 348
ORA-06512: at "SYS.DBMS_AQADM", line 2093
ORA-06512: at "SYS.DBMS_AQADM_SYS", line 16191
ORA-06512: at "SYS.DBMS_AQADM_SYS", line 16407
ORA-06512: at "SYS.DBMS_AQADM_SYSCALLS", line 973
ORA-06512: at "SYS.DBMS_AQADM_SYS", line 16326
ORA-06512: at "SYS.DBMS_AQADM_SYS", line 16179
ORA-06512: at "SYS.DBMS_AQADM", line 2086
ORA-06512: at "APPWORX.AM_AQ", line 333
ORA-06512: at "APPWORX.AWAPI3", line 3592
ORA-06512: at "APPWORX.AWAPI3", line 3592
ORA-06512: at "APPWORX.AWAPI3", line 3570
ORA-06512: at "APPWORX.SQLOPER_SOJOBQUEUE", line 121
ORA-04088: error during execution of trigger 'APPWORX.SQLOPER_SOJOBQUEUE'
ORA-06512: at "APPWORX.AW2", line 198
ORA-06512: at "APPWORX.AW2", line 252
ORA-06512: at "APPWORX.AW2", line 252
ORA-06512: at "APPWORX.AW5", line 1646
ORA-06512: at "APPWORX.AW5", line 1929
ORA-06512: at line 1

Environment

Applications Manager 9.6

Cause

Bug in code within $AW_HOME/sql/am_aq.sql or %AW_HOME%\sql\am_aq.sql (Windows OS) which allowed an AQ purge to be attempted during on ongoing AQ purge

Resolution

A fix will be included in the next version of Applications Manager

Workaround:

Apply an updated am_aq.sql.  To apply fix:

1. Download attached am_aq2.zip and unzip.
1. Copy am_aq2.sql into the $AW_HOME/sql or $%AW_HOME%\sql (Windows OS) directory
2. stop all Applications Manager processes or Service (Windows OS)
3. cd to the sql directory and sqlplus into the database as the AM Oracle User
4. execute script by typing "@am_aq2.sql" and hitting enter
5. Exit sqlplus and restart AM processes or service