My Oracle Support Banner

Data Pump Import (IMPDP) Fails With Error: ORA-39183: internal error -19 ocurred during decompression phase 2 (Doc ID 2092469.1)

Last updated on APRIL 03, 2020

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.1 and later
Oracle 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 Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
***Checked for relevance on 31-May-2017***

NOTE: In the document content below, the user information and data used represents fictitious data .Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.

Symptoms

On : 11.2. version, Data Pump Import (IMPDP)

When attempting to perform an import of a dumpfile set, the following errors occur.

Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Master table "user"."SYS_IMPORT_FULL_01" successfully loaded/unloaded
Starting "<user>"."SYS_IMPORT_FULL_01":user/******** full=y directory=TEST_DATA_PUMP dumpfile=TEST_20151222_%U.dmp logfile=TEST_20151223.log parallel=8
Processing object type DATABASE_EXPORT/TABLESPACE
ORA-39126: Worker unexpected fatal error in KUPW$WORKER.LOAD_METADATA [SELECT process_order, flags, xml_clob, NV
L(dump_fileid, :1), NVL(dump_position, :2), dump_length, dump_allocation, NVL(value_n, 0), grantor, object_row,
object_schema, object_long_name, partition_name, subpartition_name, processing_status, processing_state, base_ob
ject_type, base_object_schema, base_object_name, base_process_order, property, size_estimate, in_progress, origi
nal_object_schema, original_object_name, creation_level, object_int_oid FROM "user"."SYS_IMPORT_FULL_01" WHER
E process_order between :3 AND :4 AND duplicate = 0 AND processing_state NOT IN (:5, :6, :7) ORDER BY process_o
rder]
ORA-39183: internal error -19 ocurred during decompression phase 2
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPW$WORKER", line 9001
----- PL/SQL Call Stack -----
object line object
handle number name
0x10eadc180 20462 package body SYS.KUPW$WORKER
0x10eadc180 9028 package body SYS.KUPW$WORKER
0x10eadc180 4185 package body SYS.KUPW$WORKER
0x10eadc180 9725 package body SYS.KUPW$WORKER
0x10eadc180 1775 package body SYS.KUPW$WORKER
0x10eae1cb0 2 anonymous block
ORA-39126: Worker unexpected fatal error in KUPW$WORKER.LOAD_METADATA [SELECT process_order, flags, xml_clob, NV
L(dump_fileid, :1), NVL(dump_position, :2), dump_length, dump_allocation, NVL(value_n, 0), grantor, object_row,
object_schema, object_long_name, partition_name, subpartition_name, processing_status, processing_state, base_ob
ject_type, base_object_schema, base_object_name, base_process_order, property, size_estimate, in_progress, origi
nal_object_schema, original_object_name, creation_level, object_int_oid FROM "user"."SYS_IMPORT_FULL_01" WHER
E process_order between :3 AND :4 AND duplicate = 0 AND processing_state NOT IN (:5, :6, :7) ORDER BY process_o
rder]
ORA-39183: internal error -19 ocurred during decompression phase 2
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPW$WORKER", line 9001

 

The file has not been FTP'd so there is no file transfer corruption.

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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.