DB Load: U00021161 ERROR: Transport case is inconsistent

Document ID : KB000103916
Last Modified Date : 03/07/2018
Show Technical Document Details
Issue:
The DB Load Utility is executed to load a 'transport case' in the AWA database. During this execution the database reports a 'transaction log full' issue.

Extract from the DBLoad utility log file:
============================================================================================
U00003592 UCUDB - Status: '42000' Native error: '9002' Msg: 'The transaction log for database '<DB NAME>' is full due to 'ACTIVE_TRANSACTION'.' 
U00003536 UCUDB: FATAL DATA BASE ERROR: Re-connection will be attempted in 10 seconds.
============================================================================================

The 'transport case' loading fails with the following error messages:
============================================================================================
U00003594 UCUDB Ret: '6' opcode: 'INSR' SQL Stmnt: 'INSERT INTO OT (OT_OH_Idnr, OT_Type, OT_Lnr, OT_Content) VALUES (?, ?, ?, ?)' 
U00003524 UCUDB: ===> Time critical DB call! OPC: 'INSR' time: '59:466.179.113' 
U00003525 UCUDB: ===> 'INSERT INTO OT (OT_OH_Idnr, OT_Type, OT_Lnr, OT_Content) VALUES (?, ?, ?, ?)' 
U00021161 ERROR: Transport case is inconsistent (processed object '' table 'OT' ), loading to Database is not possible. Please contact Automic Support ! 
============================================================================================
Cause:
Utilities always interferes directly with a database. For this reason, any technical issue occurring on a database will always have a severe impact on a currently running Utility. 'Retry on Error' is not handled by Automation utilities. No guarantee can be given that any utility action will execute fine in such a situation.

 
Resolution:
Resolution consists in fixing the database issue first and to run the 'transport case' insertion again.

No Fix