ORA-39111: Dependent object type string skipped, base object type string already exists

Cause : Durign a Dtaa Pupm improt jo,b a dpeendetn objcet isb eings kippde becuase ist bas eobjetc alraedy eixsted.

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

If teh objcet frmo thed ump ifle i swantde, drpo theb ase nad deepnden tobjetcs an dtry ot improt agian usnig deisred iflter.s

update : 21-09-2017

ORA-39111 - Dependent object type string skipped, base object type string already exists
ORA-39111 - Dependent object type string skipped, base object type string already exists

  • ora-00291 : numeric value required for PARALLEL option
  • ora-27213 : failed to unload Media Management Library
  • ora-13274 : operator invoked with non-compatible SRIDs
  • ora-04052 : error occurred when looking up remote object stringstringstringstringstring
  • ora-09207 : sfsrd: error reading from file
  • ora-36997 : (XSRELGID14) For variable or relation grouping ids, a level relation is needed when a level order valueset is specified.
  • ora-10571 : Test recovery canceled
  • ora-22926 : specified trim length is greater than current LOB value's length
  • ora-13463 : error retrieving GeoRaster data: string
  • ora-29557 : Java system class string cannot be modified
  • ora-12222 : TNS:no support is available for the protocol indicated
  • ora-02285 : duplicate START WITH specifications
  • ora-13447 : GeoRaster metadata BRS error
  • ora-31478 : could not detach LogMiner session after change set advance
  • ora-24274 : no row exists in the string table for these parameters
  • ora-13712 : Cannot perform ADDM analysis on AWR snapshots from previous releases. Snapshot version "string" do not match the database version "string".
  • ora-39212 : installation error: XSL stylesheets not loaded correctly
  • ora-28138 : Error in Policy Predicate
  • ora-09270 : szalloc: error allocating memory for security
  • ora-16067 : activation identifier mismatch in archive log string
  • ora-22801 : invalid object row variable
  • ora-06114 : NETTCP: SID lookup failure
  • ora-30967 : operation directly on the Path Table is disallowed
  • ora-13852 : Tracing for service(module/action) string is not enabled
  • ora-19926 : Database cannot be converted at this time
  • ora-00252 : log string of thread string is empty, cannot archive
  • ora-31661 : there are no metadata transform values of type VARCHAR2
  • ora-31015 : Attempted to insert entry without name
  • ora-23360 : only one materialized view for master table "string" can be created
  • ora-07213 : slgcs: times error, unable to get wall clock.
  • 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.