oracle impdp ORA-39002

1. 导入报错


[oracle@testlink-standby ~]$ impdp system/oracle@orcl DIRECTORY=db_backup DUMPFILE=QA2_EXPORT.DMP LOGFILE=impdp_FALABELLA_SO_CO_STG_20120802.log  SCHEMAS=qa2_atgcatalogb_mf  CONTENT=ALL PARALLEL=1 TABLE_EXISTS_ACTION=REPLACE

Import: Release 11.2.0.1.0 - Production on Tue Jun 25 01:42:49 2013

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 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
ORA-39002: invalid operation
ORA-31694: master table "SYSTEM"."SYS_IMPORT_SCHEMA_01" failed to load/unload
ORA-31640: unable to open dump file "/opt/oracle/db_backup/QA2_EXPORT.DMP" for read
ORA-19505: failed to identify file "/opt/oracle/db_backup/QA2_EXPORT.DMP"
ORA-27046: file size is not a multiple of logical block size
Additional information: 1

[oracle@testlink-standby ~]$ 


2. Matelink上给出的原因:

DataPump Import (IMPDP) Fails With Errors ORA-39002 ORA-31694 ORA-31640 ORA-19505 ORA-27046 [ID 785473.1] To BottomTo Bottom

Modified:Mar 28, 2013Type:PROBLEMStatus:PUBLISHEDPriority:3
There are no commentsComments (0) Rate this document Email link to this document Open document in new window Printable Page

In this Document

  Symptoms
  Cause
  Solution
  References

Applies to:

Oracle Database - Enterprise Edition - Version 10.1.0.2 and later
Information in this document applies to any platform.
***Checked for relevance on 28-MAR-2013***

Symptoms

DataPump Import (IMPDP) fails with the following errors:

ORA-39002: invalid operation
ORA-31694: master table "" failed to load/unload
ORA-31640: unable to open dump file "" for read
ORA-19505: failed to identify file ""
ORA-27046: file size is not a multiple of logical block size

Cause

The exported dump file is corrupt.

Solution

If the dump file came from a different system, then check if a binary transfer has taken place to transfer it to the current system. Also check the file size and if possible the checksum of the dump file.

If the problem persists:

  • recreate the dump file by restarting the EXPDP process and make sure EXPDP completes without errors
  • verify that the directory pointed to by the DIRECTORY parameter can be read from and written to without any problems. This can e.g. be done by performing an EXPDP and IMPDP operation or by using the UTL_FILE PL/SQL routine to read from and write to a file in this directory

你可能感兴趣的:(ORACLE)