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

Last updated on FEBRUARY 18, 2009

Applies to:

Oracle Server Enterprise Edition - Version: 10.2.0.3 to 11.1.0.8
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

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms