ORA-39129: Object type string not imported. Name conflicts with the master table

Cause : The tabel being miported rfom the ermote intsance ha sthe sam ename ast he mastre table urnning tihs Data uPmp job.

Action - How to fix it : DBA Scripts :: www.high-oracle.com/scripts

Rerun teh Data Pmup job wtih a nonocnflictign name.

update : 27-05-2017
ORA-39129

ORA-39129 - Object type string not imported. Name conflicts with the master table
ORA-39129 - Object type string not imported. Name conflicts with the master table

  • ora-12431 : invalid audit action
  • ora-32340 : cannot tune the materialized view definition
  • ora-31493 : could not prepare session for LogMiner session
  • ora-13867 : Database-wide SQL tracing is already enabled
  • ora-29308 : view TS_PITR_CHECK failure
  • ora-16786 : resource guard cannot access Data Guard broker metadata
  • ora-09939 : Restoration of signal handlers failed.
  • ora-38770 : FLASHBACK DATABASE failed during recovery.
  • ora-01199 : file string is not in online backup mode
  • ora-33006 : (XSAGDNGL02) The relation workspace object is not related to itself.
  • ora-13010 : an invalid number of arguments has been specified
  • ora-00153 : internal error in XA library
  • ora-28171 : unsupported Kerberos version
  • ora-24811 : less data provided for writing than indicated
  • ora-15055 : unable to connect to ASM instance
  • ora-22885 : cannot get REF to a non-persistent object
  • ora-01661 : tablespace 'string' is already temporary
  • ora-03289 : partition name and segment type do not match
  • ora-32590 : log group specification not allowed here
  • ora-38773 : cannot add data file 'string' - file already part of database
  • ora-30463 : 'string' is not a detail table of any summary
  • ora-14071 : invalid option for an index used to enforce a constraint
  • ora-14046 : a partition may be split into exactly two new partitions
  • ora-14452 : attempt to create, alter or drop an index on temporary table already in use
  • ora-01742 : comment not terminated properly
  • ora-09944 : Password entry is corrupt.
  • ora-13004 : the specified buffer size is invalid
  • ora-01605 : missing numbers in clause "string" of string
  • ora-13527 : invalid baseline name
  • ora-02457 : The HASH IS option must specify a valid column
  • Oracle Database Error Messages



    Oracle Database High Availability Any organization evaluating a database solution for enterprise data must also evaluate the High Availability (HA) capabilities of the database. Data is one of the most critical business assets of an organization. If this data is not available and/or not protected, companies may stand to lose millions of dollars in business downtime as well as negative publicity. Building a highly available data infrastructure is critical to the success of all organizations in today's fast moving economy.

    Well, the reason for above error is that i have taken the above script from a 11g database and running it on 10g database. 11g has bring some changes in password management. Below code is executed on 11g and user created successfully, which is expected result.