Expdp encountered ORA-39006, ORA-39065, ORA-01403, ORA-39097 Error

An error was reported when I used the expdp Data Pump to export data today. [Oracle @ srccatdumpdp] $ expdpsrcbsrcbdirectorydumpdirdumpfilesrcb.20120221.dm

An error was reported when I used the expdp Data Pump to export data today. [Oracle @ srccat dumpdp] $ expdp srcb/srcb directory = dumpdir dumpfile = srcb.20120221.dm

An error was reported when I used the expdp Data Pump to export data today.

[Oracle @ srccat dumpdp] $ expdp srcb/srcb directory = dumpdir dumpfile = srcb.20120221.dmp

Export: Release 10.2.0.4.0-Production on Tuesday, 21 February, 2012 11:11:20

Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.4.0-Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
ORA-39006: internal error
ORA-39065: unexpected master process exception in DISPATCH
ORA-01403: no data found

ORA-39097: Data Pump job encountered unexpected error 100

Although it is not like other people on the Internet also encountered a ORA-00600 error, but according to the practice of the Internet, re-generate some datapump api used to view the problem solved:

Refer to the Metalink article:

Expdp fails with ORA-600 [unable to load xdb library] [ID 736049.1]

Modification time 23-JUN-2010 type PROBLEM status PUBLISHED

In this Document

Applies to: Oracle Server-Enterprise Edition-Version: 10.2.0.1 to 10.2.0.5.0-Release: 10.2 to 10.2

SymptomsThis article is written specifically for when Data Pump export (EXPDP) fails with the following ORA-00600 error seen in the alert log and also reported from the export log:

ORA-00600: internal error code, arguments: [unable to load XDB library], [], []

It may be that this article will solve for other situations where the error is seen but as the error
Is quite general and can be see due to> 1 reason there is no guarantee. If in doubt please
Raise a SR to ORACLE Support.

The following symptoms will be seen :-

A) EXPDP session/log will look something like :-

Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.3.0-64bit Production
With the Partitioning, OLAP and Data Mining options

Starting "xx". "SYS_EXPORT_SCHEMA_01": gsa /********
Estimate in progress using BLOCKS method...
Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
Total estimation using BLOCKS method: 11.16 GB
Processing object type SCHEMA_EXPORT/USER
Processing object type SCHEMA_EXPORT/SYSTEM_GRANT
Processing object type SCHEMA_EXPORT/ROLE_GRANT
Processing object type SCHEMA_EXPORT/DEFAULT_ROLE
Processing object type SCHEMA_EXPORT/TABLESPACE_QUOTA
Processing object type SCHEMA_EXPORT/PRE_SCHEMA/PROCACT_SCHEMA
Processing object type SCHEMA_EXPORT/SEQUENCE
ORA-39014: One or more workers have prematurely exited.
ORA-39029: worker 1 with process name "DW01" prematurely terminated
ORA-31671: Worker process DW01 had an unhandled exception.
ORA-00600: internal error code, arguments: [unable to load XDB library], [], []
ORA-06512: at "SYS. KUPW $ WORKER", line 1342
ORA-06512: at line 2

Job "xx". "SYS_EXPORT_SCHEMA_01" stopped due to fatal error at 11:03:15

B) The ORA-00600 trace will contain the SQL :-

SELECT/* + rule */SYS_XMLGEN (VALUE (KU $), XMLFORMAT. createFormat2 ('Cluster _ t ',
'7'), KU $. OBJ_NUM, KU $. SCHEMA_OBJ.NAME, KU $. SCHEMA_OBJ.NAME, 'cluster', KU $. SCHEMA_OBJ.OWNER_NAME from sys. KU $ _ CLUSTER_VIEW KU $ where not (BITAND (KU $. SCHEMA_OBJ.FLAGS, 16) = 16) and ku $. SCHEMA_OBJ.OWNER_NAME =: SCHEMA1 and not exists (SELECT 1 from sys. KU $ NOEXP_TAB a where. OBJ_TYPE = 'cluster' and. NAME = KU $. SCHEMA_OBJ.NAME and. SCHEMA = KU $. SCHEMA_OBJ.OWNER_NAME) and not exists (SELECT 1 from sys. KU $ NOEXP_TAB a where. OBJ_TYPE = 'scheme' and. NAME = KU $. SCHEMA_OBJ.OWNER_NAME );

----- PL/SQL Call Stack -----
Object line object
Handle number name
C0000000b9a60d98 1050 package body SYS. DBMS_METADATA
C0000000b9a60d98 1256 package body SYS. DBMS_METADATA
C0000000b9a60d98 1583 package body SYS. DBMS_METADATA
C0000000b9a60d98 1891 package body SYS. DBMS_METADATA
C0000000b9a60d98 4224 package body SYS. DBMS_METADATA
C0000000b9ac55a0 2005 package body SYS. KUPW $ WORKER
C0000000b9ac55a0 6854 package body SYS. KUPW $ WORKER
C0000000b9ac55a0 1259 package body SYS. KUPW $ WORKER
C0000000b0534cc0 2 anonymous block

C) ORA-00600 trace file call stack will be similar :-

Kgerinv <-example <-qmtLoadSharedData <-qmtbInit <-qmtInit <-qmtLookup <-qmtAddRef <-example <-qctcopn <-qctsvcti <-qctcopn <-xtyopn <-kokvbwoc <-kokvaroid <-kkmevw <-example <-qcsprfro <-example <-qcspafq <-qcspqb <-example <-qcsevw <-kkmevw <-example <-qcsprfro <-example <-qcspafq <-qcspqb <- signature <-kkmevw <-example <-qcsprfro <-example <-qcspafq <-qcspqb <-Example <-qcspqb <-qcsevw <-kkmevw <-weight <-qcsprfro <-weight <-qcspafq <-qcspqb <-kkmdrv <-opiSem <-opiDeferredSem <-opitca <-example <-rpiswu2 <-example <-kksfbc <-opiexe <-opipls <-opiodr <-rpidrus <-skgmstack <-rpidru <-rpiswu2 <- rpidrv <-psddr0 <-psdnal <-pevm_OPND <-example <-pfrrun <-plsql_run <-peicnt <-kkkxexe <-opiexe <-kpoal8 <-opiodr <<-upirtrc <-kpurcsc <-kpuexecv8 <-kpuexec <-OCIStmtExecute <-kupprdp <-opirip <-opidrv <-sou2o <-opimai_real
<-Main <-$ START $

D) Environment variables have been reviewed against Note 351650.1
But are considered to be valid.

CauseThe cause seems linked to some temporary upted KU $ objects but how the database gets into this
Position is unclear from the ORA-600 trace.



Solution

As the SYSDBA user, please run the following scripts :-