DataPump Export Failed With Error ORA-44203 On TRIGGER SYSMAN.MGMT_STARTUP

郑全

DataPump Export Failed With Error ORA-44203 On TRIGGER SYSMAN.MGMT_STARTUP (Doc ID 2045957.1)
To Bottom

In this Document
Symptoms
Changes
Cause
Solution
References

Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.1 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
DataPump export (EXPDP) returns the following errors:
ORA-39126: Worker unexpected fatal error in KUPW$WORKER.FETCH_XML_OBJECTS [TRIGGER:"SYSMAN"."MGMT_STARTUP"]
ORA-44203: timeout waiting for lock on cursor
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPW$WORKER", line 9001
----- PL/SQL Call Stack -----
object line object
handle number name
0x973ef7f0 20462 package body SYS.KUPW$WORKER
0x973ef7f0 9028 package body SYS.KUPW$WORKER
0x973ef7f0 10935 package body SYS.KUPW$WORKER
0x973ef7f0 2728 package body SYS.KUPW$WORKER
0x973ef7f0 9697 package body SYS.KUPW$WORKER
0x973ef7f0 1775 package body SYS.KUPW$WORKER
0xdb2f5460 2 anonymous block
Changes
The fix for bug 3395082 is present or the database was upgraded from earlier releases (10.1.0.4, 10.2.0.1 or later version).
The MGMT_STARTUP trigger was introduced through the fix for bug 3395082 SYSMAN PLSQL objects should be kept at instance startup (Doc ID 3395082.8)
Cause
The problem was analyzed in unpublished bug 10037605 MGMT_STARTUP TRIGGER PRESENT IN THE REPOSITORY FOR DBCONSOLE 11.1.0.7.
Solution
The trigger SYSMAN.MGMT_STARTUP is no more required. You can either remove it with:
SQL> drop trigger SYSMAN.MGMT_STARTUP;
Or disable the trigger with:
SQL> alter trigger SYSMAN.MGMT_STARTUP disable;
and restart the database.