Problem with DB (Un)Load fault folder structure - - DB Load Endless Loop (Transport Case)

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

Problem with DB (Un)Load fault folder structure - - DB Load Endless Loop (Transport Case)

Environment

Release: AOATAM99000-9.0-Automic-One Automation Tools-Application Manager
Component:

Resolution

Detailed Description and Symptoms

 

Due to a false XDUPLICATEOBJECT folders which are directly created in a Client get a wrong OFS_Level (2 instead of 1). This error was caused by the Initialdata 9.00A SP2 and was corrected by 9.00A SP2 HF4.

If this occurred the folder structure can be corrected with an SQL statement (please see below). This error has been fixed in SP2 HF4.

A short summary how the error affects the system:
If the error is in the source system of DB Load a faulty Transportcase is created. This is mostly recognized by an endless loop while loading the Transportcase. The loop has been corrected already in DB Load and will be implemented in DB Load V9.00A SP3.

Till then we need to point out the faulty Transportcase and be able to correct the situation. Follow the steps below:

?

Investigation

Email from +dev (BAC)?

Solution

 

e.g.: the object \ROOT_FOLDER\OBJEKT.IM.ROOT.FOLDER in client is being unloaded.
The O-Record {Folder} in the Transportcase should look like O\ROOT_FOLDER{} but it looks like O100\ROOT_FOLDER{}

A listing of all broken folders in the Transportcase brings eg. Notepad++ when searching the regular expression "^O[^\\]" (without quotation marks, Regular-Expression Checkbox has to be set).
To correct this use the "Find&Replace" function and search for the expression "^O([^\\]*)" and replace it with "O" (each without quotation marks, Regular-Expression Checkbox has to be set)

Using Unix use the following command line: sed -i -e "s/^O\([^\\]*\)/O/" uc_data.txt

Loading a Transportcase into a System with a faulty folder structure could lead into errors as well, if the target folder is affected by this error.
In this situation DBLoad does not recognize that the folder already exists and tries to create it. This leads into a Unique Constraint Violation. For this there is no fix in DBLoad. The folder structure has to be corrected on the target system.

Please contact Automic Support for access to the SQL statements.