Ora-39126 Worker Unexpected Fatal Error In Kupw-worker.prepare-data-imp 71 Apr 2026

impdp ... transform=segment_attributes:n # bypass storage clashes

-- Pre-create target table with partitions impdp ... exclude=table_data # import only metadata first -- Then retry with data and TABLE_EXISTS_ACTION=APPEND ORA-06512: at "SYS

ORA-39126: Worker unexpected fatal error in KUPW-WORKER.PREPARE-DATA-IMP 71 ORA-06512: at "SYS.DBMS_SYS_ERROR", line ... ORA-06512: at "SYS.KUPW_WORKER", line ... ORA-xxxxx: underlying error message – that’s the real cause. 3.2 Identify Failing Table Search for Processing object lines just before the error: CLOB→VARCHAR2): If the error persists

impdp directory=DUMP_DIR dumpfile=your.dmp full=y sqlfile=check.sql If that fails, dump file may be corrupt. 4.1 Immediate Workarounds | Strategy | Command/Approach | When to Use | |----------|------------------|--------------| | Retry with no parallel | parallel=1 | Random worker crash | | Skip failing table | exclude=table_data:"IN ('BAD_TABLE')" | One table causes error | | Retry with external table mode | access_method=external_table | Direct-path load conflict | | Disable constraints/triggers | transform=disable_archive_logging:y + sqlfile pre-script | Dependency issue | | Re-extract with older version | Use expdp version=11.2 (if target is older) | Version mismatch | 4.2 Targeted Fixes If datatype mismatch (e.g., CLOB→VARCHAR2): dump file checksum

If the error persists, contact Oracle Support with the full import log, dump file checksum, and parfile used.

grep -A 20 "ORA-39126" import.log Typical stack: