My Oracle Support Banner

Datapump Export EXPDP Full Fails With ORA-20022 (Doc ID 1413725.1)

Last updated on SEPTEMBER 24, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.1 and later
Information in this document applies to any platform.
***Checked for relevance on 02-Aug-2013***

Symptoms

11.2 Datapump Export expdp raises multiple occurrences of the following bunch of errors:

ORA-31693: Table data object "<SCHEMA_NAME>"."<TABLE_NAME>" failed to load/unload and is being skipped due to error:
ORA-20022: Error in <TRIGGER_NAME> trigger: Failed to query <VIEW_NAME> view


and expdp failed with:

ORA-39126: Worker unexpected fatal error in KUPW$WORKER.FETCH_XML_OBJECTS [TABLE_DATA:"<SCHEMA_NAME>"."<TABLE_NAME>"]
ORA-31642: the following SQL statement fails:
BEGIN "SYS"."DBMS_SCHED_EXPORT_CALLOUTS".SCHEMA_CALLOUT(:1,1,1,'11.02.00.00.00'); END;
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 86
ORA-06512: at "SYS.DBMS_METADATA", line 1749

ORA-20022: Error in TRIGGER_NAME trigger: Failed to query VIEW_NAME view
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
0x11cb4a980 20462 package body SYS.KUPW$WORKER
0x11cb4a980 9028 package body SYS.KUPW$WORKER
0x11cb4a980 10935 package body SYS.KUPW$WORKER
0x11cb4a980 2728 package body SYS.KUPW$WORKER
0x11cb4a980 9697 package body SYS.KUPW$WORKER
0x11cb4a980 1775 package body SYS.KUPW$WORKER
0x11cb4d140 2 anonymous block
Job "SYSTEM"."SYS_EXPORT_FULL_01" stopped due to fatal error at 17:40:24

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.