expdp输出与log记录不一致

lixz_2008

SQL> select * from dba_directories;

OWNER                          DIRECTORY_NAME
------------------------------ ------------------------------
DIRECTORY_PATH
--------------------------------------------------------------------------------
SYS                            EXPDP_BAK
+fradg/expdp

SYS                            EXPDP
/oracle/expdp
导出的命令如下：
expdp system/oracle directory=expdp_bak dumpfile=full_%U.dmp PARALLEL=4  full=y logfile=EXPDP:full.log
输出错误：
UDE-31626: operation generated ORACLE error 31626
ORA-31626: job does not exist
ORA-39086: cannot retrieve job information
ORA-06512: at "SYS.DBMS_DATAPUMP", line 3326
ORA-06512: at "SYS.DBMS_DATAPUMP", line 4551
ORA-06512: at line 1

而EXPDP目录下的日志记录结果却是：
Dump file set for SYSTEM.SYS_EXPORT_FULL_02 is:
  +FRADG/expdp/full_01.dmp
  +FRADG/expdp/full_02.dmp
  +FRADG/expdp/full_03.dmp
  +FRADG/expdp/full_04.dmp
Job "SYSTEM"."SYS_EXPORT_FULL_02" successfully completed at 22:43:22

为什么？

psufnxk2000

怪异。  等等看答案

Maclean Liu(刘相兵

这是一个BUG ，expdp工具本身使用data pump API 监控  dm、dw等进程工作， 由于内部bug导致 这种监控失败， 但是 dm、dw进程在后台还是能顺利完成导出工作 并写出日志        可以忽略该问题


ODM FINDING:


DataPump Export (EXPDP) Client Gets UDE-8 ORA-31626 ORA-39086

Applies to:
Oracle Server - Enterprise Edition - Version: 10.2.0.2 to 11.2.0.3 - Release: 10.2 to 11.2
Information in this document applies to any platform.
*** Checked for relevance on 29-FEB-2012 ***
Symptoms
DataPump export from the client side completes with errors. Example:

expdp system/password full=y dumpfile=full_exp.dmp logfile=full_explog

...
. . exported "CALYPSO"."KICKOFF_CFG" 0 KB 0 rows
. . exported "CALYPSO"."LE_AGR_CHILD" 0 KB 0 rows
. . exported "CALYPSO"."LE_ATTR_CODE" 0 KB 0 rows

UDE-00008: operation generated ORACLE error 31626
ORA-31626: job does not exist
ORA-39086: cannot retrieve job information
ORA-06512: at "SYS.DBMS_DATAPUMP", line 2745
ORA-06512: at "SYS.DBMS_DATAPUMP", line 3712
ORA-06512: at line 1

However, reviewing the log file shows that the "job successfully completed"
Cause
This issue has been discussed in Bug 5969934 EXPDP CLIENT GETS UDE-00008 ORA-31626 WHILE THE SERVER SIDE EXPORT IS OK
Solution
The expdp client makes calls to DBMS_DATAPUMP package to start and monitor export job. Once the export job is underway, the client just monitors the job status by issuing DBMS_DATAPUMP.GET_STAUS. Therefore, if the export logfile says "job successfully completed", the dump file generated by the job should be fine.

You can simply ignore the errors, since the dump file is still valid for an import.

In the 10.2.0.2 release, there were a number of problems that caused the expdp and impdp clients to exit prematurely, interpreting a nonfatal error as a fatal one, giving the appearance that the job had failed when it hadn't. In fact, inspection of the log file, if one was specified for the job, showed that the job ran successfully to completion. Often a trace file written by one of the Data Pump processes would provide more detail on the error that had been misinterpreted as a fatal one. Many of these errors involved the queues used for communication between the Data Pump processes, but there were other issues as well.
.
With each subsequent release, these problems have been addressed, and the client has become more robust and rarely, if ever, runs into situations like this. However, this is the result of many bug fixes in subsequent releases, some in Data Pump and some in supporting layers. It's impossible to know, at this point, what combination of bug fixes would address this specific failure, and even if that was possible, it wouldn't address other possible failures that look very similar on the client side.
.
Relying on information in the log file is one way to verify that the job actually completed successfully. Problems like this one became much more intermittent by the 10.2.0.4 release and are rarely, if ever, seen in 11.1 or later.
References
BUG:5969934 - EXPDP CLIENT GETS UDE-00008 ORA-31626 WHILE THE SERVER SIDE EXPORT IS OK


DataPump Job Shows As Failed ORA-31626 From Grid But Successfully Completed From Log File

Applies to:
Oracle Server - Enterprise Edition - Version: 10.1.0.2 to 10.2.0.4 - Release: 10.1 to 10.2
Information in this document applies to any platform.
***Checked for relevance on 07-DEC-2011***
Symptoms
Grid Control shows the DataPump jobs fail with error, but the DataPump log on target server says "successfully completed".

Grid Control job log shows:

. . exported "SYSMAN"."MGMT_METRICS_RAW" 0 KB 0 rows
. . exported "SYSMAN"."MGMT_METRICS_RAW" 0 KB 0 rows
Execute Failed: ORA-31626: job does not exist
ORA-39086: cannot retrieve job information
ORA-6512: at "SYS.DBMS_DATAPUMP", line 2772
ORA-6512: at "SYS.DBMS_DATAPUMP", line 3886
ORA-6512: at line 27 (DBD ERROR: OCIStmtExecute)"

DataPump log shows:

. . exported "SYSTEM"."REPCAT$_USER_PARM_VALUES" 0 KB 0 rows
. . exported "SYSTEM"."SQLPLUS_PRODUCT_PROFILE" 0 KB 0 rows
. . exported "TSMSYS"."SRS$" 0 KB 0 rows
Master table "SYSTEM"."DP_EMREP_DBA-OD" successfully loaded/unloaded
Cause
This is Bug 5969934 EXPDP CLIENT GETS UDE-00008 ORA-31626 WHILE THE SERVER SIDE EXPORT IS OK also described in Note 549781.1 EXPDP CLIENT GETS UDE-00008 ORA-31626 ORA-39086.
Solution
You need to rely on information in the log file to verify that the job actually completed successfully.

In some cases, there was another traditional export job running on the Grid server at the same time. The rescheduled DataPump export (not conflicting with the regular export) showed as completed.

Make sure there are no other exports (traditional exp) running at the same time as the DataPump export.
References
NOTE:549781.1 - DataPump Export (EXPDP) Client Gets UDE-8 ORA-31626 ORA-39086

lixz_2008

在RAC中，我从单实例+CLUSTER=N，导出并未遇见这个BUG，导入ASM+cluster=Y才出现这个问题。