DataPump Export (expdp) Fails With ORA-1801 During Schema Export
(Doc ID 842957.1)
Last updated on MARCH 07, 2019
Applies to:Oracle Database - Enterprise Edition - Version 10.2.0.1 to 220.127.116.11 [Release 10.2 to 11.2]
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.
DataPump (expdp) schema export fails with:
Processing object type SCHEMA_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS
ORA-39125: Worker unexpected fatal error in KUPW$WORKER.UNLOAD_METADATA while calling DBMS_METADATA.FETCH_XML_CLOB [TABLE_STATISTICS]
ORA-01801: date format is too long for internal buffer
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 105
ORA-06512: at "SYS.KUPW$WORKER", line 6313
----- PL/SQL Call Stack -----
object line object
handle number name
0xd2b90628 15032 package body SYS.KUPW$WORKER
0xd2b90628 6372 package body SYS.KUPW$WORKER
0xd2b90628 2396 package body SYS.KUPW$WORKER
0xd2b90628 6944 package body SYS.KUPW$WORKER
0xd2b90628 1314 package body SYS.KUPW$WORKER
0xd2b92fc8 2 anonymous block
Job "SIT"."EXP_SIT" stopped due to fatal error at 21:50:46
Note that the problem also occurs with EXCLUDE=STATISTICS. The solution suggest in <Note 374600.1> doesn't help.
Customer cannot delete and regather the database statistics of the production DB as described in <Note 564771.1> since it could severely affect the DB global performance and the recreation of all statistics is a very time consuming process.
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