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 : 27-04-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-26024 : SKIP_UNUSABLE_INDEXES requested and index segment was initially unusable
  • ora-27093 : could not delete directory
  • ora-28151 : more than one user name specified for command
  • ora-30038 : Cannot perform parallel insert on non-partitioned object
  • ora-32312 : cannot refresh a secondary materialized view "string"."string"
  • ora-00017 : session requested to set trace event
  • ora-09290 : sksaalo: error allocating memory for archival
  • ora-39021 : Database compatibility version string is not supported.
  • ora-00350 : log string of instance string (thread string) needs to be archived
  • ora-31604 : invalid string parameter "string" for object type string in function string
  • ora-29318 : datafile string is online
  • ora-30979 : Partitioned XML Index not yet supported.
  • ora-01216 : thread string is expected to be disabled after CREATE CONTROLFILE
  • ora-33274 : (DBERR07) Timed out while trying to lock analytic workspace string for string.
  • ora-31005 : Path name length string exceeds maximum length string
  • ora-02156 : invalid TEMPORARY tablespace identifier
  • ora-34177 : (MXCHGDCL19) number cannot be deleted because one or more partitioned variables instantiate it.
  • ora-10661 : Invalid option specified
  • ora-32730 : Command cannot be executed on remote instance
  • ora-19002 : Missing XMLSchema URL
  • ora-09778 : snynfyport: failure allocating the notify port.
  • ora-38105 : Delete not yet supported when Update row-migration is possible
  • ora-00307 : requested INSTANCE_NUMBER out of range, maximum is string
  • ora-01514 : error in log specification: no such log
  • ora-16073 : archiving must be enabled
  • ora-01578 : ORACLE data block corrupted (file # string, block # string)
  • ora-19361 : ONLINE option not allowed with this type of index
  • ora-25295 : Subscriber is not allowed to dequeue buffered messages
  • ora-13041 : failed to compare tile with element string.string.string
  • ora-29907 : found duplicate labels in primary invocations
  • 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.