search cancel

Load of Transport case fails

book

Article ID: 113351

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

The load of a Transport Case with the DB Load Utility (ucybdbld) fails a with the error: 
U00000001 NO DATA (end of file, invalid key, no message...)

When setting a trace in ucybdbld.ini an error resembling the following appears close to the end of the trace:
20180907/112758.438  INSERT INTO OFS (OFS_Idnr, OFS_OH_Idnr_F, OFS_Level, OFS_OH_Idnr_O, OFS_Link, OFS_ModDate) VALUES (?, ?, ?, ?, ?, ?)
20180907/112758.453 - U00029108 UCUDB: SQL_ERROR    Database handles  DB-HENV: a3ed20  DB-HDBC: 178484e0
20180907/112758.453 - U00003591 UCUDB - DB error info: OPC: 'SQLExecDirect' Return code: 'ERROR'
20180907/112758.453 - U00003592 UCUDB - Status: '23000' Native error: '547' Msg: 'The INSERT statement conflicted with the FOREIGN KEY constraint "FK_OFS_OH_F". The conflict occurred in database "AE", table "<table>", column 'OH_Idnr'.'
20180907/112758.453 - U00003594 UCUDB Ret: '2' opcode: 'INSR' SQL Stmnt: 'INSERT INTO OFS (OFS_Idnr, OFS_OH_Idnr_F, OFS_Level, OFS_OH_Idnr_O, OFS_Link, OFS_ModDate) VALUES (?, ?, ?, ?, ?, ?)'
 

Cause

This is cause by a corruption of the folder structure of the client from which the objects are exported.

Environment

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

Resolution

Workaround:
In the client from which the objects are exported, move the object that are corrupt to the "root" of the folder structure and move them back.