Starting the secondary RmiServer may sometimes throw the below error in the secondary RmiServer's log file.
ErrorMsg: AwE-5001 Database Query Error
Details: ORA-24018: STOP_QUEUE on AM.RMI_PIPE944105729 failed, outstanding transactions found
ORA-06512: at "AM.AM_AQ", line 151
ORA-06512: at "AM.AM_AQ", line 788
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 86
ORA-06512: at "SYS.DBMS_AQADM_SYS", line 8398
ORA-06512: at "SYS.DBMS_AQADM", line 783
ORA-06512: at "AM.AM_AQ", line 139
ORA-06512: at "AM.AM_AQ", line 170
ORA-06512: at "AM.SO_SESSION_DEL", line 27
ORA-04088: error during execution of trigger 'AM.SO_SESSION_DEL'
ORA-06512: at "AM.AW_RMI_SERVERS_NOTIFY", line 12
ORA-04088: error during execution of trigger 'AM.AW_RMI_SERVERS_NOTIFY'
ORA-06512: at "AM.AW5", line 1341
ORA-06512: at "AM.AW5", line 1270
ORA-06512: at line 1
When this error occurs, Agents may not failover to the secondary RmiServer if the Primary is stopped or becomes unavailable.
Applications Manager version 9.6 and 9.6.1
needed to add exception to handle the STOP_QUEUE when there is an outstanding transaction
Fixed in Applications Manager 9.6.2 and/or 9.7
Workaround:
A fix will be included in Applications Manager version 9.6.2 and/or 9.7
Workaround for 9.6 and 9.6.1:
A patch can be applied by running two sql scripts that are attached to this article, am_aq_aq_fix.sql and aw_operation_body_aq_fix.sql.
To revert changes: