My Oracle Support Banner

On Datapump Import, Using JOB_NAME Parameter Can Raise ORA-39129 and ORA-39130 (Doc ID 760716.1)

Last updated on MAY 22, 2020

Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.3 to 11.1.0.8 [Release 10.2 to 11.1]
Oracle Database Cloud Schema Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database 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.
This problem can occur on any platform.
Oracle Server - Enterprise Edition - Version: 10.2.0.3

Symptoms

While executing a datapump import job and using the JOB_NAME parameter, the following errors may be raised:
    ORA-39129: Object type TABLE:"USER_NAME"."SOME_JOB_NAME not imported.
                          Name conflicts with the master table
    ORA-39130: Object type INDEX:"USER_NAME"."SYS_TABLE_000202490_IND_1" not imported.
                          Base object name conflicts with the master table

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
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.