Tuesday, 18 April 2017

UDE-31626: operation generated ORACLE error 31626 | Oracle EXPDP/IMPDP

UDE-31626: operation generated ORACLE error 31626 | Oracle EXPDP/IMPDP


Export and Import are daily basis activity for an Oracle DBA. But the below mentioned error is not that you see everyday. Although the error is ignorable as per Oracle Support.


C:\>expdp directory=DB_DUMP dumpfile=export_dptest_310117.dmp logfile=export_dptest_310117.log full=y

Export: Release 11.2.0.3.0 - Production on Tue Jan 31 17:11:38 2017

Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.

Username: sys@dptest as sysdba
Password:

Connected to: Oracle Database 11g Release 11.2.0.3.0 - 64bit Production
Starting "SYS"."SYS_EXPORT_FULL_02":  sys/********@dptest AS SYSDBA directory=DB_DUMP dumpfile=export_dptest_310117.dmp logfile=export_dptest_310117.log full=y
Estimate in progress using BLOCKS method...
Processing object type DATABASE_EXPORT/SCHEMA/TABLE/TABLE_DATA

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

Solution:


1) Mainly this error indicates that the job has been finished so simply ignore the error and check the export log for the completion of the process. Go to the end of the log where it will show you whether the operation has completed or has been terminated in the middle. Often this error causes confusion that whether the operation has failed but it's not.

2) This usually happens due to inconsistency between Database Pump Master Jobs/Worker Jobs and Sha20dows Process running behind all the scenario. Sometimes data pump jobs write messages in the queue faster than they gets removed via a Shadow Process. And this inconsistency makes this happen.

For more information, you can follow Oracle Support Document - Doc ID 1970322.1

Oracle Support has also mentioned a Bug Id - 17966375 for the same. This doesn't mean that you definitely need to apply the particular bug in your Environment but if you still want to avoid similar messages in the upcoming future, you can use it.

The same error has been fixed in 12.1.0.2 and 12.2.0.1 and upcoming versions.

No comments:

Post a comment