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 : 28-07-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-16533 : inconsistent Data Guard broker state
  • ora-32332 : cannot refresh materialized view "string"."string" as type evolution has occured
  • ora-13024 : polygon has less than three segments
  • ora-26515 : no master log available for 'string.string'
  • ora-25454 : error during evaluation of rule set: string.string for iterator: string
  • ora-15152 : cluster in rolling upgrade
  • ora-32608 : missing INCREMENT or DECREMENT keyword in FOR loop
  • ora-31443 : deadlock detected while acquiring lock on string
  • ora-06000 : NETASY: port open failure
  • ora-15121 : ASM file name 'string' contains an invalid diskgroup name
  • ora-33338 : (DSSEXIST05) You cannot specify the EXPTEMP analytic workspace.
  • ora-30155 : An I/O Error occured during an OCIFile function call
  • ora-00371 : not enough shared pool memory, should be atleast string bytes
  • ora-02433 : cannot disable primary key - primary key not defined for table
  • ora-13505 : SYSAUX tablespace can not be made read only
  • ora-21612 : key is already being used
  • ora-31468 : cannot process DDL change record
  • ora-38730 : Invalid SCN/TIMESTAMP expression.
  • ora-16748 : resource guard encountered errors during database open
  • ora-02060 : select for update specified a join of distributed tables
  • ora-29356 : These parameters can be specified only for directives that refer to consumer groups
  • ora-19958 : potential deadlock involving DIAG process
  • ora-16038 : log string sequence# string cannot be archived
  • ora-35076 : (QFHEAD04) CAUTION: The textual data in EIF file string is encoded in a character set that is not recognized by this version of string.
  • ora-13415 : invalid or out of scope point specification
  • ora-09890 : osnTXtt: malloc failed
  • ora-30072 : invalid time zone value
  • ora-29531 : no method string in class string
  • ora-13467 : unsupported GeoRaster metadata specification: string
  • ora-39765 : stream must be reset before used in a column array conversion
  • 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.