【问题描述】

从10g数据库导入到19c数据库，原端库是10g 10.2.0.5   目标库是19c rac，在原端产生上执行导出正常，命令如下：

expdp system/oracle DIRECTORY=EXPDATA dumpfile=findb2139930.dmp logfile=findb_2139930.log schemas=INFA_DOM,ODS1,ODS2,FSD,SCH,FIN,DAMT,ODS,INFA_REP,ADM,EP2EAS,TPS,TEST,SUB PARALLEL=2

导入时报错：

[oracle@findb1:/dmp]$impdp system/oracle DIRECTORY=EXPDATA dumpfile=findb2139930.dmp logfile=findb_213101110.log schemas=INFA_DOM,ODS1,ODS2,FSD,SCH,FIN,DAMT,ODS,INFA_REP,ADM,EP2EAS,TPS,TEST,SUB exclude=PROCACT_INSTANCE cluster=no PARALLEL=2  

Import: Release 19.0.0.0.0 - Production on 星期三 3月 10 11:18:36 2021
Version 19.8.0.0.0

Copyright (c) 1982, 2019, Oracle and/or its affiliates.  All rights reserved.

连接到: Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
已成功加载/卸载了主表 "SYSTEM"."SYS_IMPORT_SCHEMA_04" 
启动 "SYSTEM"."SYS_IMPORT_SCHEMA_04":  system/******** DIRECTORY=EXPDATA dumpfile=findb2139930.dmp logfile=findb_213101110.log schemas=INFA_DOM,ODS1,ODS2,FSD,SCH,FIN,DAMT,ODS,INFA_REP,ADM,EP2EAS,TPS,TEST,SUB cluster=no PARALLEL=2 exclude=PROCACT_INSTANCE 
处理对象类型 SCHEMA_EXPORT/USER
ORA-39126: 在 KUPW$WORKER.LOAD_METADATA [TABLE_DATA:"SYSTEM"."SYS_IMPORT_SCHEMA_04"] 中 Worker 发生意外致命错误
SELECT process_order, flags, xml_clob, NVL(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_object_type, base_object_schema, orig_base_object_schema, base_object_name, orig_base_object_name, base_process_order, parent_process_order, property, size_estimate, in_progress, original_object_schema, original_object_name, creation_level, object_path_seqno, object_type, object_type_path, object_int_oid, metadata_io,option_tag FROM "SYSTEM"."SYS_IMPORT_SCHEMA_04" WHERE  process_order between :3 AND :4 AND duplicate = 0 AND processing_state NOT IN (:5, :6, :7) ORDER BY process_order
ORA-39183: 出现内部错误 -19 (在解压缩阶段 2)

ORA-06512: 在 "SYS.DBMS_SYS_ERROR", line 105
ORA-06512: 在 "SYS.KUPW$WORKER", line 12620
ORA-06512: 在 "SYS.DBMS_SYS_ERROR", line 105
ORA-06512: 在 "SYS.KUPW$WORKER", line 5386
ORA-06512: 在 "SYS.KUPF$FILE", line 8008
ORA-06512: 在 "SYS.KUPF$FILE_INT", line 962
ORA-06512: 在 "SYS.KUPF$FILE", line 7995
ORA-06512: 在 "SYS.KUPW$WORKER", line 5179

----- PL/SQL Call Stack -----
  object      line  object
  handle    number  name
700010009bb2b68     33476  package body SYS.KUPW$WORKER.WRITE_ERROR_INFORMATION
700010009bb2b68     12641  package body SYS.KUPW$WORKER.DETERMINE_FATAL_ERROR
700010009bb2b68      5499  package body SYS.KUPW$WORKER.LOAD_METADATA
700010009bb2b68     13781  package body SYS.KUPW$WORKER.DISPATCH_WORK_ITEMS
700010009bb2b68      2429  package body SYS.KUPW$WORKER.MAIN
70001006ca3d930         2  anonymous block

KUPW: Checking existence of new_seqno row
KUPW: Type completion row exist count is: 0
KUPW: Inserting new row at seqno: 100000001
KUPW: Created type completion for seqno 100000001
KUPW: Process order range is 439164 to 439177
DBMS_LOB.CREATETEMPORARY l_md_src_blob
KUPF$FILE.READ_LOB
KUPF$FILE.CLOSE_CONTEXT
KUPF$FILE.CLOSE_CONTEXT
KUPW: In procedure DETERMINE_FATAL_ERROR with ORA-39183: 出现内部错误 -19 (在解压缩阶段 2)
ORA-06512: 在 "SYS.KUPW$WORKER", line 5386
ORA-06512: 在 "SYS.KUPF$FILE", line 8008
ORA-06512: 在 "SYS.KUPF$FILE_INT", line 962
ORA-06512: 在 "SYS.KUPF$FILE", line 7995
ORA-06512: 在 "SYS.KUPW$WORKER", line 5179

ORA-39126: 在 KUPW$WORKER.LOAD_METADATA [SELECT process_order, flags, xml_clob, NVL(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_object_type, base_object_schema, orig_base_object_schema, base_object_name, orig_base_object_name, base_process_order, parent_process_order, property, size_estimate, in_progress, original_object_schema, original_object_name, creation_level, object_path_seqno, object_type, object_type_path, object_int_oid, metadata_io,option_tag FROM "SYSTEM"."SYS_IMPORT_SCHEMA_04" WHERE  process_order between :3 AND :4 AND duplicate = 0 AND processing_state NOT IN (:5, :6, :7) ORDER BY process_order] 中 Worker 发生意外致命错误
ORA-39183: 出现内部错误 -19 (在解压缩阶段 2)

ORA-06512: 在 "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: 在 "SYS.KUPW$WORKER", line 12613
ORA-06512: 在 "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: 在 "SYS.KUPW$WORKER", line 5386
ORA-06512: 在 "SYS.KUPF$FILE", line 8008
ORA-06512: 在 "SYS.KUPF$FILE_INT", line 962
ORA-06512: 在 "SYS.KUPF$FILE", line 7995
ORA-06512: 在 "SYS.KUPW$WORKER", line 5179

----- PL/SQL Call Stack -----
  object      line  object
  handle    number  name
700010009bb2b68     33476  package body SYS.KUPW$WORKER.WRITE_ERROR_INFORMATION
700010009bb2b68     12641  package body SYS.KUPW$WORKER.DETERMINE_FATAL_ERROR
700010009bb2b68      5499  package body SYS.KUPW$WORKER.LOAD_METADATA
700010009bb2b68     13781  package body SYS.KUPW$WORKER.DISPATCH_WORK_ITEMS
700010009bb2b68      2429  package body SYS.KUPW$WORKER.MAIN
70001006ca3d930         2  anonymous block

KUPW: Checking existence of new_seqno row
KUPW: Type completion row exist count is: 0
KUPW: Inserting new row at seqno: 200000001
KUPW: Created type completion for seqno 200000001
KUPW: Process order range is 439164 to 439177
DBMS_LOB.CREATETEMPORARY l_md_src_blob
KUPF$FILE.READ_LOB
KUPF$FILE.CLOSE_CONTEXT
KUPF$FILE.CLOSE_CONTEXT
KUPW: In procedure DETERMINE_FATAL_ERROR with ORA-39183: 出现内部错误 -19 (在解压缩阶段 2)
ORA-06512: 在 "SYS.KUPW$WORKER", line 5386
ORA-06512: 在 "SYS.KUPF$FILE", line 8008
ORA-06512: 在 "SYS.KUPF$FILE_INT", line 962
ORA-06512: 在 "SYS.KUPF$FILE", line 7995
ORA-06512: 在 "SYS.KUPW$WORKER", line 5179

作业 "SYSTEM"."SYS_IMPORT_SCHEMA_04" 因致命错误于 星期三 3月 10 11:23:41 2021 elapsed 0 00:05:01 停止

[oracle@findb1:/dmp]$

【问题分析】

这个报错，是由于dump文件集不全导致的。为什么文件集不全呢？

如果导出命令里面使用了parallel选项，那么dumpfile名字应该包含通配符才可以。

例如：

impdp system/oracle full=y directory=TEST_DATA_PUMP dumpfile=TEST_20151222_%U.dmp logfile=TEST_20151223.log parallel=8

【解决方法】

再次导出数据，将dumpfile文件增加通配符。

【参考文档】

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