Skip to content
Home » Oracle » How to Resolve ORA-39143 Error Message

How to Resolve ORA-39143 Error Message

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

Was trying to import the data using impdp, but it threw an error ORA-39143.

ORA-39143: dump file "/oradata/recovery_area/full.dmp" may be an original export dump file

Rationale

This error has already told us the reason why the dump file cannot be used. ORA-39143 means that this dump file does not come from data pump, it's an old-fashioned dump file exported by original or legacy exp utility.

This error has already told us the reason why the dump file cannot be used. Because this dump file does not come from data pump, it's an old-fashioned dump file exported by original or legacy exp utility.

Let's see the content of ORA-39143

Description

ORA-39143: dump file "string" may be an original export dump file

Cause

A dump file was specified for an import operation which appears to have been created using the original export utility. These dump files cannot be processed by the Data Pump import utility.

Action

Try using the original import utility to process this dump file.

Solutions

Now, you have two choices to avoid ORA-39143. One way is to use original imp utility to import the dump file. The other is to get another dump file which is generated from data pump, i.e. expdp utility.

That is, the original export-import and data pump utilities can't use each other's dump files. Because they have their own format.

For transferring your shell scripts from the old exp to the new expdp, Oracle data pump provides a legacy mode to facilitate you to achieve this.

For dump files generated by the data pump expdp, you can't use the original utility imp to import the file.

By the way, we normally use system who has enough but not too much privileges to migrate data from one to another, however you can also use expdp AS SYSDBA instead to migrate data.

Leave a Reply

Your email address will not be published. Required fields are marked *