When transferring objects from a previous version to a newer version via the DBLoad utility (transport case) or REST import, the folder structure in Client 0 may become corrupted.
The utility imports the objects but fails to place them in the correct directories.
Instead, the database load treats the client template object (CLNT) as a folder, creating subfolders invisibly underneath it rather than in the expected root Explorer path.
Product: CA Automic Workload Automation - Automation Engine
Component: DB Load Utility
Versions Affected: 24.4.2 (including HF2 and HF3)
Upgrading From: 21.0.9
Database: Oracle 19c
Operating System: Windows Server
This issue is caused by defect ID DE181281 in how the DBLoad utility handles folder creation specifically within Client 0.
A permanent fix for Defect DE181281 is targeted for a future release.
Component: Utility
Automic Automation Engine 24.4.4 - Available
Public Title:
Fix DBLoad Folder Corruption in Client 0
Public Description:
This fix resolves an issue in the DBLoad utility that caused corrupted folder structures when importing objects into Client 0.
To prevent the generation of corrupted entries during an upgrade, you can bypass the defect by ensuring the utility does not need to create the folders.
Before loading the transport cases, manually create the required folder structure in the target system. Depending on the objects being imported, you should manually create the following directories:
FOLDER1\FOLDER1
FOLDER1\FOLDER2
FOLDER1\FOLDER3
FOLDER1\FOLDER4
By creating these folders in advance, DBLoad will recognize the existing structure and successfully place the imported objects without corrupting the CLNT template.
Article title: How to register to Broadcom Software Product updates and Critical Alerts
https://knowledge.broadcom.com/external/article?articleId=133819