DataPump Jobs Suddenly Starts To Fail With ORA-31626: Job Does Not Exist
(Doc ID 2197898.1)
Last updated on SEPTEMBER 14, 2024
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.1 and laterOracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
Nightly export jobs that run using DataPump and the "old" export utility have been running fine for a long time.
Suddenly the jobs used to export, through DataPump Utility, a schema has started to fail with:
No other errors are reported.
No additional information is reported in alert.log. No useful information is seen in a trace file and nothing in the Export log except: Job "<SCHEMA_NAME>"."SYS_EXPORT_SCHEMA_02" stopped due to fatal error at Mon Oct 24 07:41:21 2016 elapsed 0 00:00:22.
Changes
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 |
Changes |
Cause |
Solution |
References |