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 : 26-05-2017

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

  • ora-01118 : cannot add any more database files: limit of string exceeded
  • ora-38411 : invalid datatype for the column storing expressions
  • ora-23379 : connection qualifier "string" is too long
  • ora-30550 : index depends on a package/function spec/body which is not valid
  • ora-33086 : (XSAGINIT01) AGGMAP workspace object cannot be dimensioned by a conjoint dimension.
  • ora-30479 : Summary Advisor error string
  • ora-27031 : mirror resilvering functions not supported
  • ora-36188 : (XSAGGR16) AGGREGATE read a value less than 1 out of COUNTVAR variable workspace object. Either the values of the COUNTVAR variable are stored improperly, or there is problem in AGGREGATE. If no one has modified the values in this COUNTVAR, contact Oracle customer support.
  • ora-25507 : resource manager has not been continuously on
  • ora-14086 : a partitioned index may not be rebuilt as a whole
  • ora-31620 : file or device "string" cannot be specified for string operation
  • ora-01112 : media recovery not started
  • ora-29555 : Java source, class or resource is not allowed here
  • ora-02808 : Allocation of memory of open files array failed.
  • ora-12997 : cannot drop primary key column from an index-organized table
  • ora-30399 : a skip level must have at least one column that allows NULL values
  • ora-30514 : system trigger cannot modify tablespace being made read only
  • ora-26696 : no streams data dictionary for object with number string and version number string from source database string
  • ora-08269 : destroy_ora_addr: cannot destroy name
  • ora-01931 : cannot grant string to a role
  • ora-06004 : NETASY: dialogue file open failure
  • ora-29811 : missing STATISTICS keyword
  • ora-22835 : Buffer too small for CLOB to CHAR or BLOB to RAW conversion (actual: string, maximum: string)
  • ora-03292 : Table to be truncated is part of a cluster
  • ora-08452 : specification of E in picture mask is unsupported
  • ora-29831 : operator binding not found
  • ora-01038 : cannot write database file version string with ORACLE version string
  • ora-23463 : flavor incompatible with object "string"."string"
  • ora-26699 : STREAMS message consumer string already exists
  • ora-13008 : the specified date format has an invalid component
  • 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.