Impdp Error Reporting ORA-39001, ORA-39000, ORA-31619

Not long ago, when I used the data pump tool impdp for data import, an error was reported, prompting that the dunp file was invalid. I found it through the query documentation because it was incompatible with the previous version.

Not long ago, when I used the data pump tool impdp for data import, an error was reported, prompting that the dunp file was invalid. I found it through the query documentation because it was incompatible with the previous version.

Not long ago, when I used the data pump tool impdp for data import, an error was reported, prompting that the dunp file was invalid. I found out that it was caused by incompatibility between the higher version and the lower version ,, the solution is as follows.

Import Error

C: \ Documents ents and Settings \ hoegh> impdp hoeghto/ilovehoegh directory = data_pump_directory

Dumpfile = 20150826dynamic. dmp remap_schema = hoeghfrom: hoeghto remap_tablespace = hoeghfrom: hoeghto

Import: Release 10.1.0.2.0-Production on Tuesday, 01 August 1, 2015

Copyright (c) 2003, Oracle. All rights reserved.

Connected to: Oracle Database 10g Enterprise Edition Release 10.1.0.2.0-Produc

Tion

With the Partitioning, OLAP and Data Mining options

ORA-39001: invalid argument value

ORA-39000: bad dump file specification

ORA-31619: invalid dump file "d: \ data_pump_directory \ 20150826dynamic. dmp"

C: \ Documents ents and Settings \ hoegh>

Source database version

SQL> select * from v $ version;

BANNER

----------------------------------------------------------------

Oracle Database 10g Enterprise Edition Release 10.2.0.4.0-64bi

PL/SQL Release 10.2.0.4.0-Production

CORE 10.2.0.4.0 Production

TNS for 64-bit Windows: Version 10.2.0.4.0-Production

NLSRTL Version 10.2.0.4.0-Production

SQL>

Target database version

SQL>

SQL> select * from v $ version;

BANNER

----------------------------------------------------------------

Oracle Database 10g Enterprise Edition Release 10.1.0.2.0-Prod

PL/SQL Release 10.1.0.2.0-Production

CORE 10.1.0.2.0 Production

TNS for 32-bit Windows: Version 10.1.0.2.0-Production

NLSRTL Version 10.1.0.2.0-Production

SQL>

Add version Parameters
The source database version is 10.2.0.4.0, the target database version is 10.1.0.2.0, and the source database version is later than the target database version. The solution is simple. Add the target version when exporting data from the source database, see the SQL statement:

Expdp hoeghfrom/ilovehoegh directory = data_pump_directory dumpfile = 20150826dynamic. dmp tables = (HOEGH) version = 10.1.0.2.0

Next, we can execute the impdp statement again.

ORA-31693 & ORA-31640 & ORA-19505 & ORA-27037

Oracle Import and Export expdp IMPDP details

Solution to Oracle 10g expdp export error ORA-4031

Oracle 10gr2 rac expdp error UDE-00008 ORA-31626

Use of expdp/impdp to back up databases in Oracle

Oracle backup recovery (expdp/impdp)

Problems and Solutions of impdp ORA-39002, ORA-39166 and ORA-39164

This article permanently updates the link address: