EXPDP – ORA-39006,ORA-39213 Metadata processing is not available.

EXPDP – ORA-39006,ORA-39213 Metadata processing is not available


While Taking full database export using “EXPDP” i was getting below mentioned error :


###############################################


$ expdp directory=datapump dumpfile=expdp_hrs92dmo.dmp logfile=expdp_hrs92dmo.log full=y


Export: Release 11.2.0.2.0 – Production on Thu Feb 27 10:48:09 2014


Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
Username : sys@hrs92dmo as sysdba
Password:


Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 – 64bit Production
With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,
Data Mining and Real Application Testing options
ORA-39006: internal error
ORA-39213: Metadata processing is not available


###############################################


I tried it many times but the error remains the same.


==> Problem Solution :


(1) Check all the oracle registry entry are in valid state. If not check the issue :


###########################################################


SQL> SELECT comp_id, version, status FROM dba_registry;


COMP_ID VERSION STATUS
—————————— —————————— ———–
EM 11.2.0.4.0 VALID
CATALOG 11.2.0.4.0 VALID
CATPROC 11.2.0.4.0 INVALID
###########################################################



(2) Check for Permission :


During dbms_metadata_util.load_stylesheets we read the directory $ORACLE_HOME/rdbms/xml/xsl and load the XSL files using DBMS_LOB package.


If the files cannot be read (most of cases by missing rwx privileges for oracle user), then we raise the errors above.


Re-load the stylesheets using the dbms_metadata_util.load_stylesheets procedure after the permission issue is solved and then retry DataPump export ( expdp ).


###########################################################


SQL> execute dbms_metadata_util.load_stylesheets


PL/SQL procedure successfully completed.


###########################################################





(3) Repair Registry :


In case you have INVALID status in dba_registry. Check it and try to find a solution for it. In my case “CATPROC” was invalid. 
To resolve this i run “CATPROC.sql” file which is present in “$ORACLE_HOME/RDBMS/admin/” directory :


###########################################################


SQL> ?/rdbms/admin/catproc.sql
###########################################################


###########################################################


Add the more space in Temporary tablespace
###########################################################
This solved my issue.

  • August 31, 2017 | 15 views
  • Comments