How to troubleshoot ORA-39006 and ORA-39213 errors

ORA-39213: metadata processing is not available2010-05-26

I reported an error when using expdp to export data today. It is strange that my operation steps are correct. ORA-39006: Internal error ORA-39213: metadata processing is not available. The following is my troubleshooting information Operating System: Linux infodb111.com 2.6.9-42.0.0.0.1.elsmp #1 SMP sun Oct 15 14:02:40 PDT 2006 i686 i686 i386 GNU/Linux Database Version Information: Oracle Database 10g Enterprise Edition Release 10.2.0.4.0-Prod PL/SQL release 10.2.0.4.0-Production Core 10.2.0.4.0 Production TNS for Linux: Version 10.2.0.4.0-Production Nlsrtl version 10.2.0.4.0-Production The procedure is as follows: [Root @ infodb111 ~] # Su-Oracle [Oracle @ infodb111/] $ mkdir/Oracle/dump_dir [Oracle @ infodb111/] $ sqlplus/As sysdba SQL> create directory dump_dir as '/Oracle/dump_dir '; SQL> grant read, write on directory dump_dir to Scott; Grant succeeded. [Oracle @ infodb111/] $ expdp Scott/Scott tables = mevent directory = dump_dir dumpfile = dump1.dmp Export: Release 10.2.0.4.0-production on Wednesday, 26 May, 2010 11:02:10 Copyright (c) 2003,200 7, Oracle. All rights reserved. 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-39213: metadata processing is not available. [Oracle @ infodb111/] $ oerr ora 39006 39006,000 00, "internal error" // * Cause: An Unexpected error occurred while processing a Data Pump job. // Subsequent messages supplied by dbms_datapump.get_status // Will further describe the error. // * Action: Contact Oracle customer support. [Oracle @ infodb111/] $ oerr ora 39213 39213,000 00, "metadata processing is not available" // * Cause: the data pump cocould not use the Metadata API. Typically, // This is caused by the XSL stylesheets not being set up properly. // * Action: connect as sysdba and execute dbms_metadata_util.load_stylesheets // To reload the stylesheets. Execute exec dbms_metadata_util.load_stylesheets according to the oerr ora 39213 prompt; The export operation is normal and the problem is solved.