ORA-36740: A CHILDLOCK was detected in your valueset

Cause : N/A.

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


update : 24-05-2017

ORA-36740 - A CHILDLOCK was detected in your valueset
ORA-36740 - A CHILDLOCK was detected in your valueset

  • ora-04002 : INCREMENT must be a non-zero integer
  • ora-19812 : cannot use string without DB_RECOVERY_FILE_DEST
  • ora-12724 : regular expression corrupt
  • ora-08233 : smsdes: cannot unmap SGA
  • ora-38434 : could not evaluate expression "string"
  • ora-31212 : DBMS_LDAP: PL/SQL - Invalid LDAP mod_array.
  • ora-27013 : skgfqdel: cannot delete an open file
  • ora-13370 : failure in applying 3D LRS functions
  • ora-15126 : component within ASM file name 'string' exceeds maximum length
  • ora-16065 : remote archival disabled at standby destination
  • ora-19617 : file string contains different resetlogs data
  • ora-23422 : Oracle Server could not generate an unused job number
  • ora-10854 : Sets poll count used for AQ listen code under RAC
  • ora-07455 : estimated execution time (string secs), exceeds limit (string secs)
  • ora-16257 : Switchover initiated stop apply successfully completed
  • ora-24775 : cannot prepare or commit transaction with non-zero lock value
  • ora-00712 : cannot rename system tablespace
  • ora-16151 : Managed Standby Recovery not available
  • ora-09771 : osnmwrtbrkmsg: bad return code from msg_send.
  • ora-22612 : TDS does not describe a collection TDS
  • ora-07561 : szprv: $IDTOASC failure
  • ora-16557 : the database is already in use
  • ora-30680 : debugger connection handshake failed
  • ora-37132 : (XSCCOMP07) Incremental aggregation over the dense DIMENSION workspace object is not supported when aggregating a VARIABLE dimensioned by a COMPRESSED COMPOSITE.
  • ora-28267 : Invalid NameSpace Value
  • ora-12448 : policy string not applied to schema string
  • ora-14106 : LOGGING/NOLOGGING may not be specified for a clustered table
  • ora-13135 : failed to alter spatial table
  • ora-13907 : Threshold value is invalid.
  • ora-38907 : DML error logging is not supported for FILE column "string"
  • 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.