My Oracle Support Banner

DataPump Import (IMPDP) Fails With Errors ORA-39126 ORA-6512 When Using A Network Link (Doc ID 1148584.1)

Last updated on JULY 28, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.1 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
***Checked for relevance on 15-Apr-2013***


NOTE: In the images and/or the document content below, the user information and data used represents fictitious data .Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.

Symptoms

The DataPump import log can report similar to the following errors:

Starting "STRMADMIN"."SYS_IMPORT_TABLE_03":
ORA-39126: Worker unexpected fatal error in KUPW$WORKER.POST_MT_INIT [SELECT SYS.KUPM$MCP.GET_ENDIANNESS@<DB_LINK> FROM SYS.DUAL]
ORA-04054: database link TMS does not exist
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPW$WORKER", line 8164
----- PL/SQL Call Stack -----
object line object
handle number name
700000121234170 19028 package body SYS.KUPW$WORKER
700000121234170 8191 package body SYS.KUPW$WORKER
700000121234170 2072 package body SYS.KUPW$WORKER
700000121234170 1438 package body SYS.KUPW$WORKER
7000001138a2748 2 anonymous block
Job "STRMADMIN"."SYS_IMPORT_TABLE_03" stopped due to fatal error at 12:30:48


The parameter file is similar to the following:

QUERY=(TMS.PROBLEM:"WHERE tmsactivity_id = 21",TMS.ACTION:"WHERE exists (select null from tms.problem@ttms p where p.aa_id = pr_ac and tmsactivity_id = 21)")
LOGFILE=imp_wh_tms.log
TABLE_EXISTS_ACTION=REPLACE
CONTENT=ALL
TABLES=(TMS.PROBLEM,TMS.ACTION,TMS.EMPLOYEE,TMS.ACTCODE,TMS.CLIENT)
flashback_scn=39586847872
network_link='TMS'
REMAP_TABLESPACE=EXT:USERS
REMAP_TABLESPACE=SETUP:USERS
REMAP_TABLESPACE=IDX:USERS
REMAP_TABLESPACE=DATA:USERS
REMAP_TABLESPACE=LOB:USERS
REMAP_SCHEMA=TMS:STAR_WH_PROX

Changes

 NONE

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


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