search cancel

DB load terminated abnormally

book

Article ID: 202719

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

DB load going to 12.3 is receiving the following error:

 

The loading process was terminated abnormally. The Database might be in an inconsistent condition. Please contact Automic Support.
Application return code = 1

Load Log shows (indicators of actual problem bolded as the nonbolded are system specific):
20201104/102737.226 - U00029108 UCUDB: SQL_ERROR    Database handles  DB-HENV: 11c0160  DB-HDBC: 12b0078
20201104/102737.226 - U00003591 UCUDB - DB error info: OPC: 'OCIStmtExecute' Return code: 'ERROR'
20201104/102737.226 - U00003591 UCUDB - Status: '' Native error: '4088' Msg: 'ORA-04088: error during execution of trigger 'SYSTEM.BEFORE_CREATE_OR_ALTER_TABLE'
ORA-00604: error occurred at recursive SQL level 1
ORA-20001: An attempt was made to create or alter a table to contain clobs or blobs.  Please get approval from ORACLE DBA Management before proceeding.
ORA-06512: at line 59'
20201104/102737.226 - U00003594 UCUDB Ret: '3590' opcode: 'EXEC' SQL Stmnt: '

ALTER TABLE OVD ADD (OVD_SqlPostgres CLOB NULL)'
20201104/102737.226 - U00003590 UCUDB - DB error: 'OCIStmtExecute', 'ERROR   ', '', 'ORA-04088: error during execution of trigger 'SYSTEM.BEFORE_CREATE_OR_ALTER_TABLE'
ORA-00604: error occurred at recursive SQL level 1
ORA-20001: An attempt was made to create or alter a table to contain clobs or blobs.  Please get approval from ORACLE DBA Management before proceeding.
ORA-06512: at line 59'
20201104/102737.228 - U00038068 ABORTING due to error.

Environment

Release : 12.1

Component : AUTOMATION ENGINE

Cause

This is caused by custom triggers on creating or altering table

Resolution

Based on the combination of:
Native error: '4088' Msg: 'ORA-04088: error during execution of trigger
ORA-20001

this is caused by a custom trigger on the database.  A DBA will need to be involved to see what is causing this.
In this case, a DBA disabled the trigger that was causing the problem and the load was able to run correctly.