Datapump IMPDP Fails With ERRORS ORA-39097 ORA-39065 ORA-12801 ORA-1460 In RAC Environment [ID 1427537.1]

Import: Release 11.2.0.2.0 - Production on Lun. Févr. 6 10:07:26 2012

Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
;;;
Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,
Data Mining and Real Application Testing options
Master table "AGRT997"."IMPDP_MDHP1_201202006100500" successfully loaded/unloaded
Starting "AGRT997"."IMPDP_MDHP1_201202006100500": AGRT997/******** PARFILE=D:\Batch\script_gen\DP_IMP_MDHP1_pour_S1.PAR
Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
. . imported "AGRMDHS1"."DOCMNIMAGE"          4.455 GB      65505 rows
ORA-39097: Data Pump job encountered unexpected error -12801
ORA-39065: unexpected master process exception in MAIN
ORA-12801: error signaled in parallel query server PZ99, instance QUBC1-SGBDA16N:accp2 (2)
ORA-01460: unimplemented or unreasonable conversion requested
Job "AGRT997"."IMPDP_MDHP1_201202006100500" stopped due to fatal error at 10:19:51

Cause

This issue was investigated in bug 13654760.

Solution

Use the following available workaround to resolve this issue:

- set parameter PARALLEL_DEGREE_POLICY=MANUAL.

Unfortunately there are no patches available for this issue and no other workarounds available.


Regards,
Suresh.G

Datapump NETWORK_LINK Option:

I found good option using datapump Network_link which saves lot of time of time avoiding export and diskspace for the export dumps.

Steps to be followed:

Eg: Source Database is ABC ( Production)
      Target  Database is XYZ ( QA)

Prerequisites :

1) Create DB_LINK from XYZ database on QA to ABC Database on Production.
2) Grant  Roles of EXP_FULL_DATABASE and IMP_FULL_DATABASE to target database (XYZ)  and EXP_FULL_DATABASE to Source Database (ABC)

3) Make sure you provide the username & password of Target Database which is QA here in the example.
4) Start the import using network_link option as below.

Syntax:

From Target Database.


impdp userid= usrename/password@targetdb  network_link=ABC.WORLD parfile= ABC.par

Conclusion:

This option works majorly for larger schemas where we cannt afford time for export & ftp and having space issues on the server.


Regards,
Suresh.G