Datapump Errors: ORA-31626 ORA-31637 ORA-31635: unable to establish job resource synchronization
(Doc ID 1924218.1)
Last updated on JULY 02, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.1 to 11.2.0.4 [Release 11.2]Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
After a failed Datapump job, a process can be left alive and not cleaned up. Subsequent attempts to export fail with the following errors:
ORA-31626: job does not exist
ORA-31637: cannot create job SYS_EXPORT_TABLE_01 for user SYS
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPV$FT_INT", line 798
ORA-31635: unable to establish job resource synchronization
ORA-31637: cannot create job SYS_EXPORT_TABLE_01 for user SYS
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPV$FT_INT", line 798
ORA-31635: unable to establish job resource synchronization
Cleaning up the abandoned process using the following Note fails:
<Note 453338.1> : Errors ORA-31635 ORA-31637 ORA-6512 With DataPump Export (EXPDP)
Because attempts to identify the serial# of the abandoned process shows that the serial# keeps changing, and is changing too quickly to be able to identify it and kill it before it changes again.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |