JWP 'hangs' right at Start-Up after system has been renamed

book

Article ID: 84909

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine AUTOMIC WORKLOAD AUTOMATION

Issue/Introduction

Error Message :
U00003590 UCUDB - DB error: '23000', 'ORA-00001: Unique Constraint (UC4.PK_OH) violated', '1', 'java.sql.SQLIntegrityConstraintViolationException'

or similar for other Databases

After the system name has been changed, i.e. for an update installation, the JWP stops processing right after startup. From an OS perspective the process stays idle. The last lines within the log  file show a database error message regarding primary key violation. Example for Oracle (similar message on other DB):
 

....
20170922/152502.690 -           JWP/JCP registered as WO121 VWGSUP12 192.168.0.49
20170922/152502.700 - U00003488 Server 'JWP VWGSUP12 192.168.0.49 ' was started as instance '9'.
20170922/152502.750 - U00003490 Connection to '192.168.0.49:14270' initiated, client connection '1'
20170922/152502.954 - U00003489 Server 'WO121#WP001' logged on (Client connection='1').
20170922/152502.956 - U00003490 Connection to '192.168.0.49:14217' initiated, client connection '2'
20170922/152502.964 - U00003490 Connection to '192.168.0.49:14219' initiated, client connection '3'
20170922/152502.974 - U00003489 Server 'WO121#CP001' logged on (Client connection='2').
20170922/152502.979 - U00003489 Server 'WO121#CP003' logged on (Client connection='3').
20170922/152502.980 - U00003491 There is a time difference of '0/00:00:00' or '0' seconds to the Primary Server.
20170922/152502.987 - U00003475 Server 'WO121#WP001' is the primary server of the system 'WO121'.
20170922/152503.315 - U00003590 UCUDB - DB error: '23000', 'ORA-00001: Unique Constraint (UC4.PK_OH) verletzt
', '1', 'java.sql.SQLIntegrityConstraintViolationException'


As a primary key violation can have many different root causes a trace (database=2, tcp=4) needs to be created for verification:

<Please see attached file for image>

0EMb0000000IZsb.png
The issue can be identified by the failing INSERT into OH after the SELECT and UPDATE on IDS.

 

Cause

Cause type:
Defect
Root Cause: The issue was caused in the ID cache management for OH_IDNRs.

Environment

Release: AUTWAB99000-12.0-Automic Workload Automation-Base Edition
Component:

Resolution

Update to a fix version listed below or a newer version if available.

Fix Status: Released

Fix Version(s):
Component(s): Automation.Engine & Initialdata

Automation Engine 12.1.1 - Available

Additional Information

Workaround :
Restart the JWP. It might be necessary to restart multiple times until the JWP passes the erroneous part of the initialization.

Attachments

1558704588305000084909_sktwi1f5rjvs16lms.png get_app