When you see the full message ORA-39126: Worker unexpected fatal error in KUPW$WORKER.PREPARE_DATA_IMP [71] ORA-01403: no data found , the [71] portion is an internal sequence number of the Oracle procedure that failed. In this instance, the primary failure is often accompanied by an ORA-01403: no data found error, which indicates that the Data Pump worker is trying to locate data that does not exist in the expected location.
If any are INVALID , you may need to recompile them or run the Data Pump component upgrade scripts ( @?/rdbms/admin/catdp.sql ). Step 3: Use Content=Data_Only When you see the full message ORA-39126: Worker
is a critical, generic unhandled internal exception thrown by Oracle Data Pump during an import operation ( impdp ). This error indicates that the background worker process crashed during the setup phase of loading table data. Step 3: Use Content=Data_Only is a critical, generic
| Cause | Description | |-------|-------------| | | File transfer errors (binary vs. ASCII), incomplete dump, or storage corruption | | Character set mismatch | Source and target databases have incompatible character sets, especially with NCLOB/NVARCHAR2 | | Invalid table definition | Table on target has columns that conflict with dump file (data type, length, partition differences) | | Object already exists | Table exists but with constraints/triggers that block Data Pump transformation | | Oracle Bug | Known issues in specific versions (especially 11.2, 12.1, 18c, and early 19c) | | Insufficient privileges | Worker cannot perform a required operation due to missing grants | ASCII), incomplete dump, or storage corruption | |
Run a check on the target schema before restarting the import:
For the specific bug causing ORA-39126 in PREPARE_DATA_IMP [71] with ORA-01403 , Oracle has documented a concrete solution in .
Solution A: Exclude StatisticsIn many cases, the crash occurs while Data Pump is trying to recalculate or import optimizer statistics. Add EXCLUDE=STATISTICS to your IMPDP command.