ORA-39143: dump file "c:\....dmp" may be an original export dump file

 

ORA-39143 dump file may be an original export dump file

 

Problem Description

C:\>impdp directory=gg dumpfile=ggexp.dmp userid=system/xxxxx

ORA-39001: invalid argument value
ORA-39000: bad dump file specification
ORA-39143: dump file "C:\oracle\ggexp.dmp" may be an original export dump file

Cause of the problem
The above problem happened whenever you try to use the Import Data Pump client (impdp) to import a dumpfile that was created with the original Export client (exp).

Though not related but similar error occured.
Like whenever you try to import from an empty file,

C:\>impdp directory=gg dumpfile=ggexp.dmp userid=system/xxxxx


ORA-39001: invalid argument value
ORA-39000: bad dump file specification
ORA-31619: invalid dump file "C:\oracle\ggexp.dmp"
ORA-27091: unable to queue I/O
ORA-27070: async read/write failed
OSD-04006: ReadFile() failure, unable to read from file
O/S-Error: (OS 38) Reached the end of the file.

Whenever you try to import from invalid dump file or corrupted dump file then you may get following error,

C:\>impdp directory=gg dumpfile=ggexp.dmp userid=system/xxxxx



Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
ORA-39001: invalid argument value
ORA-39000: bad dump file specification
ORA-31619: invalid dump file "C:\oracle\ggexp.dmp"

Solution of the Problem

-Data pump export client(impdp) can't read file created by the original export client (exp).



-Data exported by data pump client(expdp) can't be readable by original import client(imp).

So to import dumpfile that was created with the original Export client (exp) you must have to use imp.

Like,

imp userid=system/xxxxx  file=c:\oracle\ggexp.dmp

Otherwise you can export the dumpfile using expdp and then try impdp while importing.