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 : 25-09-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-02279 : duplicate or conflicting MINVALUE/NOMINVALUE specifications
  • ora-08209 : scngrs: SCN not yet initialized
  • ora-16750 : resource guard encountered errors while activating logical primary database
  • ora-16503 : site ID allocation failure
  • ora-32821 : subscriber queue and exception queue must have same payload type
  • ora-02470 : TO_DATE, USERENV, or SYSDATE incorrectly used in hash expression.
  • ora-07287 : sksagdi: unsupported device for log archiving.
  • ora-00474 : SMON process terminated with error
  • ora-13614 : The template string is not compatible with the current advisor.
  • ora-02347 : cannot grant privileges on columns of an object table
  • ora-25950 : missing where clause in join index specification
  • ora-16055 : FAL request rejected
  • ora-30752 : column or table string is not substitutable
  • ora-23359 : error on creating a ddl record for a repcatlog record
  • ora-38612 : FI item length cannot exceed half of one database block.
  • ora-29344 : Owner validation failed - failed to match owner 'string'
  • ora-19598 : can not backup SPFILE because the instance was not started with SPFILE
  • ora-06772 : TLI Driver: error sending command
  • ora-24802 : user defined lob read callback error
  • ora-14108 : illegal partition-extended table name syntax
  • ora-03252 : initial extent size not enough for LOB segment
  • ora-19691 : %s is from different database: id=string, name=string
  • ora-13767 : End snapshot ID must be greater than or equal to begin snapsho ID.
  • ora-40215 : model string is incompatible with current operation
  • ora-16817 : unsynchronized Fast-Start Failover configuration
  • ora-16038 : log string sequence# string cannot be archived
  • ora-12203 : TNS:unable to connect to destination
  • ora-31420 : unable to submit the purge job
  • ora-29297 : The compressed representation is too big
  • ora-01916 : keyword ONLINE, OFFLINE, RESIZE, AUTOEXTEND or END/DROP expected
  • 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.