My Oracle Support Banner

Errors ORA-39126 ORA-4052 ORA-12154 On DataPump Import Using NETWORK_LINK (Doc ID 1301472.1)

Last updated on JANUARY 16, 2020

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.2 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.
***Checked for relevance on 08-Jun-2015***

Symptoms

When importing data from source database version 10.2.0.4 to a RAC target database version 11.2.0.2 using a DataPump NETWORK_LINK and parallelism, it is possible to get the following errors:

ORA-39126: Worker unexpected fatal error in KUPW$WORKER.POST_MT_INIT [SELECT SYS.KUPM$MCP.GET_ENDIANNESS@<DBLINK_NAME> FROM SYS.DUAL]
ORA-04052: error occurred when looking up remote object SYS.KUPM$MCP@<DBLINK_NAME>
ORA-00604: error occurred at recursive SQL level 3
ORA-12154: TNS:could not resolve the connect identifier specified

ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPW$WORKER", line 8358

----- PL/SQL Call Stack -----
object line object
handle number name
0x45559bc50 19208 package body SYS.KUPW$WORKER
0x45559bc50 8385 package body SYS.KUPW$WORKER
0x45559bc50 2182 package body SYS.KUPW$WORKER
0x45559bc50 1474 package body SYS.KUPW$WORKER
0x45964d818 2 anonymous block

The DataPump import parameters are:

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.