There are a number of bizarre error cases encountered during the use of Oracle data pumps (_oracle)

There are a number of bizarre error cases encountered in the use of Oracle data pumps, which summarize some of the problems and solutions that you have encountered while using the data pump. Are the problems encountered in the use of the process, and then encountered the data pump (database Dump) error cases, will be supplemented in this article.

Error Case 1:

An unexpected main process exception error occurred in Ora-39065:dispatch; ORA-44002: Invalid object name

Windows Platform Error Tip:

Linux Platform Error Tip

Workaround:

-->

[Oracle@db-server admin]$ oerr ora 39065 39065, 00000
, "Unexpected master process exception in%s"
//*cause:an U Nhandled exception is detected internally within the master
/control process for the Data Pump job. This is a internal error.
Messages would detail the problems.
*action:if problem persists, contact Oracle Customer Support.
[Oracle@db-server admin]$ oerr ora 39097 39097, 00000
, "Data Pump job encountered error%s"
//Unexpected: A unexpected, potentially non-fatal error occurred while
//processing a Data Pump job.
*action:contact Oracle Customer Support.

This problem can be resolved by executing the Catmet2.sql,utlrp.sql two SQL files under the $oracle_home/rdbms/admin directory.

-->

[Oracle@db-server ~]$ cd $ORACLE _home/rdbms/admin
 
oracle@db-server admin]$ sqlplus/as sysdba
 
: Release 10.2.0.1.0-production on Sun Sep 7 08:24:23 2014
 
Copyright (c) 1982,%, Oracle. All rights reserved.
 
Connected to a idle instance.
 
sql> @catmet2. sql 
 

Error Case 2:

Encountered ora-39006:internal error;ora-39213:metadata processing is notavailable error using EXPDP/IMPDP

[Oracle@db-server backup]$ IMPDP frnt/frnt directory=dum_dir dumpfile=20120420.frnt_02.dmp;

Import:release 10.2.0.1.0-64bit Production on Wednesday, April, 14:41:48,

Copyright (c) 2003,%, Oracle. All rights reserved.

Connected to:oracle Database 10g Enterprise Edition release 10.2.0.1.0-64bit Production
with the partitioning, OLAP and Data Mining options
ora-39006:internal error
ora-39213:metadata processing is not available

Workaround:

The reason for the error is as follows, because the data pump cannot use the metadata API because the XSL stylesheets is not set properly. Need to perform dbms_metadata_util.load_stylesheets with SYSDBA

-->

[Oracle@db-server admin]$ oerr ora 39213 39213, 00000
 
, "Metadata processing is not available"
 
//*cause:the Data Pump could not use the Metadata API. Typically,
 
//This are 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.

Sql>exec dbms_metadata_util.load_stylesheets

Error Case 3:

The error is as follows:

ETL@NMS_ODS_NDB1[/JKFILE/KLBTMP] #expdp userid=username/password@tnsname dumpfile=ref.dmp Directory=DUMP_TEST Schemas=ref content=all logfile=ref.log 

export:release 10.2.0.3.0-64bit Production on Saturday, March, 2013 10:2 8:25 

Copyright (c) 2003,%, Oracle. All rights reserved. 

Connected to:oracle Database 10g Enterprise Edition release 10.2.0.3.0-64bit Production 

with the partitioning  Application clusters, OLAP and Data Mining options 

ora-39002:invalid operation to 

open the log File. 

Ora-29283:invalid file Operation 

ora-06512:at "SYS. Utl_file ", line 475 

ora-29283:invalid FILE operation 

Workaround:

This error occurs when you need to check your directory directory and when you create your directory, Oracle does not check that the operating system directory already exists

First check the directory directory dump_test the corresponding Directory_path, and then check the operating system to verify that the directory exists.

-->

Sql> SELECT * from dba_directories WHERE directory_name= ' dump_test ';
 
OWNER              directory_name      directory_path
 
-------------------------------------------------------------- ---------
 
SYS                dump_test       /jkfile/klbtmp/
 

The result check found that the directory was deleted and the directory was created to resolve the problem.

In another case, if you create a directory, there is a newline, there will be the error message above, this kind of error play difficult to find, very toss people. So you need to be very careful.

Sql> Create directory dump_test as '/jkfile/klbtmp/

';

Error Case 4:

As shown below:

ETL@NMS_ODS_NDB1[/JKFILE/WORK/KLB] #expdp userid=etl/sunrise@wgods1 dumpfile=ref.dmp directory=dump_dir schemas=ref Content=all logfile=ref.log 

export:release 10.2.0.3.0-64bit Production on Saturday, March, 2013 10:50:25 

Cop Yright (c) 2003, +, Oracle. All rights reserved. 

Connected to:oracle Database 10g Enterprise Edition release 10.2.0.3.0-64bit Production 

with the partitioning Application clusters, OLAP and Data Mining options 

ora-31631:privileges are required ora-39109:unprivileged use 

RS may isn't operate upon other users ' schemas 

Workaround:

ETL account is mainly the lack of exp_full_database permissions, to the ETL account to grant Exp_full_database permissions, the above problems resolved.

# su-oracle 

$ sqlplus/as sysdba 

sql*plus:release 10.2.0.3.0-production on Sat Mar 2 10:58:37 2013 

Ight (c) 1982, 2006, Oracle. All Rights Reserved. 

Connected to: 

Oracle Database 10g Enterprise Edition release 10.2.0.3.0-64bit Production 

with the partitioning, Real application clusters, OLAP and Data Mining options 

sql> Grant exp_full_database to ETL; 

Grant succeeded. 

Error Case 5:

ETL@NMS_ODS_NDB1[/ETL1_CX/ETL]EXPDP etl/sunrise@wgods1 DUMPFILE=DM. Tm_alarm_log.dmp Directory=dump_dir TABLES=DM. Tm_alarm_log query= ' date_cd >=20121201 and Date_cd <=20130131 '; 

Lrm-00101:unknown parameter name ' > ' 

Workaround:

ETL@NMS_ODS_NDB1[/ETL1_CX/ETL]EXPDP etl/sunrise@wgods1 DUMPFILE=DM. Tm_alarm_log.dmp Directory=dump_dir TABLES=DM. Tm_alarm_log query= "Date_cd \>\=20121201 and Date_cd \<\=20130131"; 

Error Case 6:

LRM-00121: ' Data_only ' is not a allowable value for ' compression '. As shown below:

Etl@nms_ods_ndb1[/etl1_cx/etl] #expdp etl/sunrise@wgods1 dumpfile=ref.dmp directory=dump_dir Dumpfile=DM. Tm_alarm_log201212.dmp TABLES=DM. Tm_alarm_log compression=data_only query= ' date_cd >=20121201 and Date_cd '; 

LRM-00121: ' Data_only ' is not a allowable value for ' compression ' 

Workaround:

First look at the version of the EXPDP tool, as follows:

Etl@nms_ods_ndb1[/etl1_cx/etl] #expdp version 

export:release 10.2.0.3.0-64bit Production on Monday, March, 2013 1 4:46:47 

Copyright (c) 2003,%, Oracle. All rights reserved. 

Password: 

Note that under Oracle 10g compression has only metadata_only and none two options, and the Data_only option is available under Oracle 11g. So the newspaper is a mistake. So before using, please note the version of the EXPDP tool.

Error Case 7:

[oracle@db-server]$ EXPDP system/***** Tables=invenrty. INV_STK_HD dumpfile=inv_stk_hd.dmp logfile=1.log directory=cur_dump_dir 

export:release 10.2.0.4.0-production on Sunday, July, 2013 8:27:16 

Copyright (c) 2003, 2007, Oracle. All rights reserved. 

Connected to:oracle Database 10g release 10.2.0.4.0-production 

ora-31626:job does not exist 

Ora-31637:cannot Create job sys_export_table_01 for user SYSTEM 

ora-06512:at "SYS. Dbms_sys_error ", line 

ora-06512:at" SYS. Kupv$ft_int ", line 

ora-39080:failed to create queues" kupc$c_1_20130714082716 "and" kupc$s_1_20130714082716 " For Data Pump job 

ora-06512:at "SYS. Dbms_sys_error ", line 

ora-06512:at" SYS. Kupc$que_int ", line 1606 

ora-00832:no streams pool created and cannot create one 

Workaround:

This case I have previously introduced, specific reference to my blog EXPDP derivative error ORA-00832

Error Case 8:

[oracle@testlnx01 u03]$ cd tmp/ 

[oracle@testlnx01 tmp]$ EXPDP system/***** directory=dumpdir Schemas=escmuser logfile=escmuser.log 

export:release 10.2.0.4.0-64bit Production on Wednesday, August, 2014 16:3 0:46 

Copyright (c) 2003, 2007, Oracle. All rights reserved. 

Connected to:oracle Database 10g release 10.2.0.4.0-64bit Production 

ora-31626:job does not exist 

Ora-31633:u Nable to create master table "SYSTEM. Sys_export_schema_05 the " 

ora-06512:at" SYS. Dbms_sys_error ", line 

ora-06512:at" SYS. Kupv$ft ", line 871 

ora-00959:tablespace ' TOOLS ' does not exist 

Workaround:

This case is a little special, just met the time, it is a bit inexplicable, after a hard search, to find out after the discovery, there would have been a tools table space, do not know who is the head of the Fever, actually specify the system user's default table space for tools, but the table space was deleted. So there is such a case.

sql> ALTER USER system DEFAULT tablespace system; 

User altered. 

The problem is resolved after the

modifies the default tablespace for user system.