Skip to Main Content

Database Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

import gets failure

JhilAug 18 2015 — edited Aug 20 2015

Hello everyone,


# Export parameters

DUMPFILE=dp:f1.dmp

LOGFILE=dp:f1.log

SCHEMAS=MAYA

EXCLUDE=PROCEDURE:"LIKE'PRO%'"

EXCLUDE=SEQUENCE,TABLE:"IN('EMP','DEPT')"

EXCLUDE=STATISTICS,VIEW,PACKAGE,FUNCTION

EXCLUDE=INDEX:"LIKE 'IN%'"



$ impdp system/manager dumpfile=dp:f1.dmp remap_schema=maya:hr

Import: Release 11.2.0.1.0 - Production on Tue Aug 18 21:29:43 2015

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

Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production

With the Partitioning, OLAP, Data Mining and Real Application Testing options

Master table "SYSTEM"."SYS_IMPORT_FULL_03" successfully loaded/unloaded

Starting "SYSTEM"."SYS_IMPORT_FULL_03":  system/******** dumpfile=dp:f1.dmp remap_schema=maya:hr

Processing object type SCHEMA_EXPORT/USER

Processing object type SCHEMA_EXPORT/SYSTEM_GRANT

Processing object type SCHEMA_EXPORT/ROLE_GRANT

Processing object type SCHEMA_EXPORT/DEFAULT_ROLE

Processing object type SCHEMA_EXPORT/TABLESPACE_QUOTA

Processing object type SCHEMA_EXPORT/PRE_SCHEMA/PROCACT_SCHEMA

ORA-39126: Worker unexpected fatal error in KUPW$WORKER.LOAD_METADATA [SELECT process_order, flags, xml_clob, NVL(dump_fileid, :1), NVL(dump_position, :2), dump_lengt h, dump_allocation, NVL(value_n, 0), grantor, object_row, object_schema, object_long_name, partition_name, subpartition_name, processing_status, processing_state, bas e_object_type, base_object_schema, base_object_name, base_process_order, property, size_estimate, in_progress, original_object_schema, original_object_name, creation_ level, object_int_oid FROM "SYSTEM"."SYS_IMPORT_FULL_03" WHERE  process_order between :3 AND :4 AND duplicate = 0 AND processing_state NOT IN (:5, :6) ORDER BY proces s_order]

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 8164

----- PL/SQL Call Stack -----

  object      line  object

  handle    number  name

0x6942a0d4     19028  package body SYS.KUPW$WORKER

0x6942a0d4      8191  package body SYS.KUPW$WORKER

0x6942a0d4      4172  package body SYS.KUPW$WORKER

0x6942a0d4      8874  package body SYS.KUPW$WORKER

0x6942a0d4      1651  package body SYS.KUPW$WORKER

0x693c35e0         2  anonymous block

ORA-39126: Worker unexpected fatal error in KUPW$WORKER.LOAD_METADATA [SELECT process_order, flags, xml_clob, NVL(dump_fileid, :1), NVL(dump_position, :2), dump_lengt h, dump_allocation, NVL(value_n, 0), grantor, object_row, object_schema, object_long_name, partition_name, subpartition_name, processing_status, processing_state, bas e_object_type, base_object_schema, base_object_name, base_process_order, property, size_estimate, in_progress, original_object_schema, original_object_name, creation_ level, object_int_oid FROM "SYSTEM"."SYS_IMPORT_FULL_03" WHERE  process_order between :3 AND :4 AND duplicate = 0 AND processing_state NOT IN (:5, :6) ORDER BY proces s_order]

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 8164

----- PL/SQL Call Stack -----

  object      line  object

  handle    number  name

0x6942a0d4     19028  package body SYS.KUPW$WORKER

0x6942a0d4      8191  package body SYS.KUPW$WORKER

0x6942a0d4      4172  package body SYS.KUPW$WORKER

0x6942a0d4      8874  package body SYS.KUPW$WORKER

0x6942a0d4      1651  package body SYS.KUPW$WORKER

0x693c35e0         2  anonymous block

Job "SYSTEM"."SYS_IMPORT_FULL_03" stopped due to fatal error at 21:29:46

Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Sep 17 2015
Added on Aug 18 2015
2 comments
953 views