Oracle Database / Multitenant, Patching & Deployment
ORA-39126: find the worker error beneath a Data Pump failure
A worker fatal-error message usually accompanies a more specific failure. Preserve the full job log and object context.
Environment and inputs: Oracle Database 19c baseline · SQL*Plus-compatible SQL unless RMAN, DGMGRL, ADRCI or a host shell is specified. Check release, patch level, edition and container first.
Start with this diagnostic
Use the stated SQL, RMAN, DGMGRL or host shell and replace sample names with approved targets. DBA and V$ views need authorized catalog access in the correct container. Do not grant broad privileges for an example.
SELECT owner_name, job_name, operation, job_mode, state, attached_sessions FROM dba_datapump_jobs;Read the result
The view identifies known jobs and their current states. A master-table entry can remain after a job stops and is not proof a worker is running.
Resolve and verify
Find the first specific error in the log and correlate it with the failed object and release compatibility. Repair the cause before choosing a supported restart or rerun.
Operational precautions
Do not drop the master table or recreate the job before deciding whether resumable work and evidence should be preserved.