Routine 'UCGENX_R' forces trace because of error.
Article ID: 228559
Updated On:
Products
Issue/Introduction
The Automic engine tries to generate workflows tasks twice with the same runID. The issue happens when a Workflow is started and the associated JOBG is started afterwards:
25 - 20210818/120836.020 - U00007000 '.FRM.RC#.RUNTIME_CORE_LZ_EV_AV.DBJOB' activated with RunID '0075099045'.
17 - 20210818/120836.237 - U00000002 EXISTS
17 - 20210818/120836.387 - U00000002 EXISTS
14 - 20210818/120842.524 - U00007000 '.FRM.RC#.RUNTIME_CORE_LZ_EV_AV.DBJOB' activated with RunID '0075099045'.
75099045 runID is duplicated
The following error is generated:
20210818/120836.235 - INSERT INTO EJPP (EJPP_AH_Idnr, EJPP_Lnr, EJPP_Status, EJPP_JobStatus, EJPP_OType, EJPP_Object, EJPP_WElse, EJPP_PreCnt, EJPP_PreOpen, EJPP_TimeOk, EJPP_Row, EJPP_Col, EJPP_MsgNr, EJPP_RetCode, EJPP_Restart, EJPP_RefNr, EJPP_Active, EJPP_RElse, EJPP_RRepMTimes, EJPP_RRepWait, EJPP_RRepTimes, EJPP_MrtMethod, EJPP_Mrt, EJPP_MrtTime, EJPP_MrtErt, EJPP_Srt, EJPP_SrtErt, EJPP_TaskIdnr, EJPP_ConFlag, EJPP_RExecFlag, EJPP_ModFlag, EJPP_USR_Idnr, EJPP_PreCntExt, EJPP_PreExtOpen, EJPP_ExtSLTWithin, EJPP_ExtTimeout, EJPP_ExtFirstCheck, EJPP_TimeoutFlag, EJPP_CmtFlag, EJPP_CondOpen, EJPP_EJPPV_Flag, EJPP_PreCondFlag, EJPP_PostCondFlag, EJPP_ShowPrompt, EJPP_PromptAtGen, EJPP_BranchType, EJPP_RunPerPatch, EJPP_RollbackFlag, EJPP_RBPreOpen, EJPP_RollbackMark, EJPP_RunPerTarget) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)
20210818/120836.236 - U00029108 UCUDB: SQL_ERROR Database handles DB-HENV: 251a160 DB-HDBC: 2565d28
20210818/120836.236 - U00003591 UCUDB - DB error info: OPC: 'OCIStmtExecute' Return code: 'ERROR'
20210818/120836.236 - U00003592 UCUDB - Status: '' Native error: '1' Msg: 'ORA-00001: unique constraint (UC4.PK_EJPP) violated'
20210818/120836.236 - U00003594 UCUDB Ret: '2' opcode: 'INSR' SQL Stmnt: 'INSERT INTO EJPP (EJPP_AH_Idnr, EJPP_Lnr, EJPP_Status, EJPP_JobStatus, EJPP_OType, EJPP_Object, EJPP_WElse, EJPP_PreCnt, EJPP_PreOpen, EJPP_TimeOk, EJPP_Row, EJPP_Col, EJPP_MsgNr, EJPP_RetCode, EJPP_Restart, EJPP_RefNr, EJPP_Active, EJPP_RElse, EJPP_RRepMTimes, EJPP_RRepWait, EJPP_RRepTimes, EJPP_MrtMethod, EJPP_Mrt, EJPP_MrtTime, EJPP_MrtErt, EJPP_Srt, EJPP_SrtErt, EJPP_TaskIdnr, EJPP_ConFlag, EJPP_RExecFlag, EJPP_ModFlag, EJPP_USR_Idnr, EJPP_PreCntExt,
20210818/120836.236 - UCUDB32 INSR RET 0002 HSTMT: 0x0000000ab53820 VALUE: 0x00000000000001 ALL: 0.00205 DB: 0.00129 ODBC: 0.00008 UDB: 0.00068
20210818/120836.236 - DB-OPC: CLSTA DB-RET: 0 HSTMT: 0x00000009573a60 VALUE: (nil)
20210818/120836.236 - UCUDB32 CLAL RET 0000 HSTMT: 0x00000009573a60 VALUE: (nil) ALL: 0.00036 DB: 0.00000 ODBC: 0.00029 UDB: 0.00007
20210818/120836.237 - U00003620 Routine 'UCGENX_R' forces trace because of error.
20210818/120836.237 - U00000002 EXISTS
Environment
Release : 12.3 Component : AUTOMATION ENGINE
Cause
This is a defect of the Automation Engine.
Correction done:
A bug was fixed on workflows generated at activation time.If the workflow had tasks generated at activation time, the workflow was in the wrong state.
Thus activation of the JOBG would retrigger the generation of the workflow incorrectly. The correct state is now set on the workflow.
Resolution
This bug is now fixed, the fix will be delivered in the following version of the Automation Engine.
Automation Engine 12.3.9 available
Automation Engine 21.0.3 available
Feedback
