impdp ... sqlfile=deploy.sql
Then review and manually execute the DDL, adjusting problem columns.
The worker process requires enough Program Global Area (PGA) to prepare data, especially for large rows, LOBs, or row batches. If PGA_AGGREGATE_TARGET is too low, the worker may abort.
impdp directory=DATA_PUMP_DIR dumpfile=your.dmp \
transform=segment_attributes:n:lob_storage:n \
exclude=statistics \
parallel=1 \
logfile=test.log
If the error persists, the dump file is likely irrecoverably corrupted, and you will need to recreate it from the source.
Summary
Immediate impact
Probable causes (ranked)
Evidence to collect (immediately)
Short-term remediation steps
Long-term recommendations
Suggested immediate next actions for you
If you want, I can draft a concise incident report email for stakeholders including timeline, impact, and next steps — tell me the desired recipients and tone.
Related search suggestions (automatically generated)
This error, ORA-39126: Worker unexpected fatal error in KUPW-WORKER.PREPARE-DATA-IMP 71, occurs during an Oracle Data Pump import (using impdp). It is a generic "catch-all" fatal error indicating that a worker process died unexpectedly while preparing to load data into a table. Then review and manually execute the DDL, adjusting
The "71" refers to a specific internal trace point in the Data Pump code. It almost always indicates metadata or data corruption in the dump file, object definition incompatibility, or a bug in the Data Pump client/database version.
If Data Pump consistently fails, try the original imp utility (if export was done with original exp).
If the dump file was transferred via FTP: