ORA-13800: concurrent DDL failure on SQL repository objects

Cause : A SQL repository object was the target of two concurrent DDL operations.

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

Check the current state of the object and retry the operation that failed.

update : 24-07-2017
ORA-13800

ORA-13800 - concurrent DDL failure on SQL repository objects
ORA-13800 - concurrent DDL failure on SQL repository objects

  • ora-16196 : database has been previously opened and closed
  • ora-15178 : directory 'string' is not empty; cannot drop this directory
  • ora-38476 : abstract type used for an Attribute set may not be modified.
  • ora-24082 : propagation may still be happening for the schedule for QUEUE string and DESTINATION string
  • ora-29872 : parameters clause cannot be combined with the specified options
  • ora-22308 : operation not allowed on evolved type
  • ora-25209 : invalid value string, EXPIRATION should be non-negative or NEVER
  • ora-28164 : REVOKE already specified
  • ora-19631 : archivelog record contains no file name
  • ora-01373 : insufficient memory for staging persistent LogMiner session
  • ora-12042 : cannot alter job_queue_processes in single process mode
  • ora-07497 : sdpri: cannot create trace file 'string'; errno = string.
  • ora-06305 : IPA: Illegal message type
  • ora-30339 : illegal dimension attribute name
  • ora-12489 : default label not within clearance range
  • ora-24323 : value not allowed
  • ora-36978 : (XSRELGID01) workspace object must be a self-relation.
  • ora-07670 : $IDTOASC failed translating a secrecy category
  • ora-24776 : cannot start a new transaction
  • ora-29661 : Unable to find the superclass of the defined in the EXTERNAL NAME
  • ora-23603 : STREAMS enqueue aborted due to low SGA
  • ora-16032 : parameter string destination string cannot be translated
  • ora-24417 : Session pool size has exceeded the maximum limit
  • ora-00041 : active time limit exceeded - session terminated
  • ora-24770 : cannot forget a prepared transaction
  • ora-16797 : database is not using a server parameter file
  • ora-01595 : error freeing extent (string) of rollback segment (string))
  • ora-02839 : Sync of blocks to disk failed.
  • ora-24300 : bad value for mode
  • ora-12544 : TNS:contexts have different wait/test functions
  • 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.