Update of version 11.2.4 HF.2.build.777 fails with “U00000002 EXISTS” error

Document ID : KB000084727
Last Modified Date : 14/04/2018
Show Technical Document Details
Issue:
Error Message :
U00000002 EXISTS

When upgrading the Automation Engine to version 11.2.4+hf.2.build.777, the DB Load utility will fail with the error message when attempting to load the Initialdata (UC_UPD.TXT).

This is only affects AE version using the Inital Data version 11.2.4+hf.2.build.777.

In case the very same error message shows up, but Initial Data is not on version “11.2.4+hf.2.build.777”, the resolution in this article will not be effective.
 
Due to a bug in the Initial Data version mentioned above, the object name and object number of an Initial Data object was mixed up.
This has no impact to the system at all! Everything is working as expected.

However the next update of the Automation Engine will fail. That means, once this version is installed, an update to a newer version will not work.

During the upgrade of the AE database, the load of the Initialdata “UC_UPD.TXT”, the DB Load will fail with the error:
U00000002 EXISTS

This is what the DB Load log looks like:
0EMb0000001QybG.png
This error doesn’t necessary mean, that it is exactly this issue. Only a database trace level 4 of the DB Load process shows the affected object and will look like:

 
20170425/115229.584 - U00038002 DLL 'ucybdbld', version '11.2.4+build.772'. Start parameter: '-I./ucybdbld.ini -B -X/opt/uc4/utility/db/general/11.2/UC_UPD.TXT ', (changelist '1484131397').20170425/115229.585 - ----------------------------------------------------------------------------------------------------20170425/115233.546 - U00038081 Version of database objects: '11.2.4+hf.2.build.777'Loading in mode 'UPGRADE'.20170425/115238.310 - U00038042 Loading Initialdata ...20170425/115244.830 - U00021103 Table OH was exported on: 2017-04-19 13:56:1220170425/115252.534 - U00009909 TRACE: (BINDPAR:  OH_Name           )             0x7f6efd71f6ff 000019                                00000000  584A5343 48544153 4B50524F 50455254  >XJSCHTASKPROPERT<                                00000010  494553                               >IES<20170425/115252.534 - U00009909 TRACE: (BINDPAR:  OH_Idnr           )             0x7f6efd71f7c8 00000420170425/115252.534 -                                        >49212<20170425/115252.534 - INSERT INTO OH (OH_Client, OH_OType, OH_Name, OH_Idnr, OH_CrUserIdnr, OH_CrDate, OH_ModUserIdnr, OH_LastUserIdnr, OH_LastCnt, OH_JPP_Count, OH_C0Ref, OH_NoStatUpd, OH_DeleteFlag, OH_ExpFlag, OH_MaxWait, OH_MaxParallel2, OH_MPElse, OH_OpenUserIdnr, OH_MaxRetCode, OH_MrtMethod, OH_Mrt, OH_MrtErt, OH_Frt, OH_Ert, OH_ErtCnt, OH_ErtCorr, OH_ErtIgn, OH_ErtMinCnt, OH_ErtMethod, OH_ErtTrend, OH_Srt, OH_SrtErt, OH_FcstStatus, OH_UC4Priority, OH_RefIdnr, OH_OX_ContentLen, OH_OpenSession, OH_OV_Flag, OH_OV_Mode, OH_OPU_Flag, OH_OEO_Flag, OH_IsTemplate, OH_RollbackFlag, OH_Inactive, OH_DeactDelay, OH_AEVersion) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)20170425/115252.535 - U00029108 UCUDB: SQL_ERROR    Database handles  DB-HENV: 18555c0  DB-HDBC: 18a475020170425/115252.535 - U00003591 UCUDB - DB error info: OPC: 'OCIStmtExecute' Return code: 'ERROR'20170425/115252.535 - U00003592 UCUDB - Status: '' Native error: '1' Msg: 'ORA-00001: unique constraint (UC4.UK_OH_NAME) violated'20170425/115252.535 - U00003594 UCUDB Ret: '2' opcode: 'INSR' SQL Stmnt: 'INSERT INTO OH (OH_Client, OH_OType, OH_Name, OH_Idnr, OH_CrUserIdnr, OH_CrDate, OH_ModUserIdnr, OH_LastUserIdnr, OH_LastCnt, OH_JPP_Count, OH_C0Ref, OH_NoStatUpd, OH_DeleteFlag, OH_ExpFlag, OH_MaxWait, OH_MaxParallel2, OH_MPElse, OH_OpenUserIdnr, OH_MaxRetCode, OH_MrtMethod, OH_Mrt, OH_MrtErt, OH_Frt, OH_Ert, OH_ErtCnt, OH_ErtCorr, OH_ErtIgn, OH_ErtMinCnt, OH_ErtMethod, OH_ErtTrend, OH_Srt, OH_SrtErt, OH_FcstStatus, OH_UC4Priority, OH_RefIdnr, OH_OX_Con20170425/115252.535 - UCUDB32 INSR RET 0002 HSTMT: 0x000000018c8f30 VALUE:            (nil) ALL:  0.00170 DB:  0.00118 ODBC:  0.00001 UDB:  0.0005120170425/115252.592 - U00000002 EXISTS20170425/115252.592 - U00000002 EXISTS20170425/115252.592 - U00000002 EXISTS
 
This is what the DB Load trace looks like:
0EMb0000001Qyba.png


 
Environment:
OS Version: N/A
Cause:
Cause type:
Other
Root Cause: Wrong object ID was assigned during build.
Resolution:

The issue can be resolved right away, even no update is planned yet. There is a repair script which can be loaded into the database using the DB Load Utility.

It is recommended to apply this repair script as soon as possible, even the system will remain on version “11.2.4+hf.2.build.777”. It is mandatory to apply it, before an update to any newer version is started, at the latest.

The steps blow explains how it is applied correctly. Those steps can be performed during the Automation Engine system is up and running, no downtime in needed.

 
  1. Launch the DB Load utility and choose the file “upgrade.txt”. The file is attached to this article.
    0EMb0000001QybL.png

     
  2. Confirm the load action by clicking the “Ok” button.
    0EMb0000001QybQ.png

     
  3. After it was loaded successfully the system is ready for upgrading to any higher version with standard upgrade procedure.
    0EMb0000001QybV.png

     

 

Fix Status: No Fix

Fix Version(s):
N/A
Additional Information:
Workaround :
N/A
File Attachments:
upgrade.zip