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 : 28-07-2017
ORA-39111

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-06538 : statement violates string RESTRICT_REFERENCES pragma
  • ora-24780 : cannot recover a transaction while in an existing transaction
  • ora-19551 : device is busy, device type: string, device name: string
  • ora-06703 : TLI Driver: send break message failed
  • ora-01542 : tablespace 'string' is offline, cannot allocate space in it
  • ora-06700 : TLI Driver: incorrect message type from host
  • ora-13797 : invalid SQL Id specified, string
  • ora-02368 : file string is not valid for this load operation
  • ora-19254 : XQ0034 - too many declarations for function string
  • ora-30573 : AUTO segment space management not valid for this type of tablespace
  • ora-28674 : cannot reference transient index-organized table
  • ora-32594 : invalid object category for COMMENT command
  • ora-19665 : size string in file header does not match actual file size of string
  • ora-30680 : debugger connection handshake failed
  • ora-12231 : TNS:No connection possible to destination
  • ora-37139 : (XSCCOMP14) Cannot AGGREGATE workspace object using AGGMAP workspace object because you can not AGGREGATE a variable dimensioned by a COMPRESSED COMPOSITE using an AGGMAP with a PROTECT clause.
  • ora-14013 : duplicate partition name
  • ora-00233 : copy control file is corrupt or unreadable
  • ora-08342 : sropen: failed to open a redo server connection
  • ora-14457 : disallowed Nested Table column in a Temporary table
  • ora-33280 : (DBERR10) Analytic workspace string cannot be attached in MULTI mode until the changes made and updated in RW or EXCLUSIVE mode are committed or rolled back.
  • ora-09769 : osnmbr: cannot send break message
  • ora-39117 : Type needed to create table is not included in this operation. Failing sql is: string
  • ora-13348 : polygon boundary is not closed
  • ora-24158 : invalid table alias
  • ora-07210 : slcpu: getrusage error, unable to get cpu time.
  • ora-02839 : Sync of blocks to disk failed.
  • ora-02711 : osnpvalid: write to validation channel failed
  • ora-31625 : Schema string is needed to import this object, but is unaccessible
  • ora-19654 : must use backup control file to switch file incarnations
  • 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.