Workflow was stuck in "generating" and caused an emergency trace when ORA-12592 encountered

Document ID : KB000087813
Last Modified Date : 14/04/2018
Show Technical Document Details
Issue:
Error Message :
U0003594 UCUDB-Ret: '3590' Opcode: 'SLCO' SQL-Stmnt: 'SELECT * FROM MQSRV WHERE MQSRV_Type=? OR MQSRV_Type=? OR MQSRV_Type=?'
20160312/110425.126 - U0003590 UCUDB - DB-Fehler: 'OCIStmtExecute', 'ERROR ', '', 'ORA-12592: TNS:bad packet'

If an Oracle error, ORA-12592, is encountered while executing a Workflow errors similar to these are displayed.
 
20160312/110425.126 - U0003594 UCUDB-Ret: '3590' Opcode: 'SLCO' SQL-Stmnt: 'SELECT * FROM MQSRV WHERE MQSRV_Type=? OR MQSRV_Type=? OR MQSRV_Type=?'
20160312/110425.126 - U0003590 UCUDB - DB-Fehler: 'OCIStmtExecute', 'ERROR ', '', 'ORA-12592: TNS: Ungültiges Paket'
20160312/110425.126 - U0003590 UCUDB - DB-Fehler: 'OCIStmtExecute', 'ERROR ', '', 'ORA-12592: TNS:bad packet'

Expected:  The database transactions should be rolled back when the ORA-12592 is encounterd and the Workflow should fail.

Actual:  The database transaction is not rolled back when the ORA-12592 is encountered and the Workflow remains stuck in a "generating" status and an emergency trace is created.
 
Cause:
Cause type:
Defect
Root Cause: db-transactions are not rolled back on Oracle error "ORA-12592". The aborted transactions cause a forced trace and processing of executions like workflow generation fails.
Resolution:
This field was added on 30/03/2017. This article has not been updated yet. Refer to the "Description" or "Workaround" sections for solution information.

Fix Status: Released

Fix Version(s):
Automation Engine 11.1.4 - Available
Automation Engine 10.0.8 - Available
Additional Information:
Workaround :
Workflow has to be modified manually to remove it from activity window.