|
In this Document
APPLIES TO: Oracle Database - 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 03-FEB-2014 *** SYMPTOMS DataPump import or export from the client side completes with errors. Example: expdp system/password@inst full=y dumpfile=full_exp.dmp logfile=full_explog In 10g, you may see errors such as: 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 Similar behavior is also seen in 11g: UDI-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 2862
ORA-06512: at "SYS.DBMS_DATAPUMP", line 4052
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 data pump client makes calls to DBMS_DATAPUMP package to start and monitor the job. Once the export/import job is underway, the client just monitors the job status by issuing DBMS_DATAPUMP.GET_STATUS. Therefore, if the 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.
Given the above, there is no actual fixed provided via Bug 5969934.
However, Bug 5969934 also mentions another case that resulted in this error that is being tracked separately in Bug 17966375 and for which a generic patch is available for 11.2.0.3. REFERENCES
BUG:5969934 - EXPDP CLIENT GETS UDE-00008 ORA-31626 WHILE THE SERVER SIDE EXPORT IS OK
BUG:17966375 - SUCCESSFUL EXPDP JOB SHOWS UDE-31626 AND ORA-31626 IN CLIENT OUTPUT (CRON) |
