ORA-04088: Error During Execution Of Trigger 'SYS.XDB_PI_TRIG' When Running Batch D1-UTCRN
(Doc ID 2764421.1)
Last updated on NOVEMBER 27, 2023
Applies to:
Oracle Utilities Meter Data Management - Version 2.3.0.0.0 and laterInformation in this document applies to any platform.
Goal
**Disclaimer:** This KM article may include the following abbreviations:
MDM - Oracle Utilities Meter Data Management
UT - Usage Transaction
SQL - Standard Query Language
DB - Database
When running D1-UTCRN to generate Usage Transaction the following error is encountered;
10:26:51,532 [VAMSAJOB2Worker:14] ERROR (org.hibernate.engine.jdbc.spi.SqlExceptionHelper) ORA-04088: error during execution of trigger 'SYS.XDB_PI_TRIG'
ORA-00604: error occurred at recursive SQL level 2
ORA-04025: maximum allowed library object lock allocated for BEGIN
BEGIN
IF (sys.is_vpd_enabled(sys.dictionary_obj_owner, sys.dictionary_obj_name, xdb.DBMS_XDBZ.IS_ENABLED_CONTENTS)) THEN
xdb.XDB_PITRIG_PKG.pitrig_truncate(sys.dictionary_obj_owner, sys.dictionary_obj_name);
ELSIF (sys.is_vpd_enabled(sys.dictionary_obj_owner, sys.dictionary_obj_name, xdb.DBMS_XDBZ.IS_ENABLED_RESMETADATA)) THEN
xdb.XDB_PITRIG_PKG.pitrig_dropmetadata(sys.dictionary_obj_owner, sys.dictionary_obj_name);
END IF;
EXCEPTION
WHEN OTHERS THEN
null;
END;
END;
ORA-06512: at "CISADM.D1_TRUNC_GTT_PROC", line 16
ORA-06512: at line 1
As a result, Many UTs were stuck in the CALCULATE state and were not sent to the target JMS queue.
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Goal |
Solution |
References |