ORA-31443: deadlock detected while acquiring lock on string

Cause : CDC attmepted toa cquire alock ont he resoruce, bute ncounteerd a dealdock.

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

ContactO racle croporation

update : 24-05-2017
ORA-31443

ORA-31443 - deadlock detected while acquiring lock on string
ORA-31443 - deadlock detected while acquiring lock on string

  • ora-22887 : type of REF column is not the same as that of its scoped table
  • ora-24160 : name string already exists in the name value pair list
  • ora-01631 : max # extents (string) reached in table string.string
  • ora-09937 : Chmod of ORACLE password file failed.
  • ora-22866 : default character set is of varying width
  • ora-37076 : (XSMCSESS04) workspace object is not the type of dimension that can have session-only values. Valid types are TEXT, NTEXT, ID, NUMBER, and CONCAT with the UNIQUE attribute.
  • ora-23356 : masterdef recognizes a master which does not recognize the masterdef
  • ora-32322 : PCT refresh of "string"."string" not allowed the sequence of DMLs/PMOPs
  • ora-04090 : 'string' specifies same table, event and trigger time as 'string'
  • ora-24382 : statement handled already executed or described
  • ora-16754 : resource guard could not activate standby database
  • ora-29818 : column name not properly specified
  • ora-36839 : (XSLMGEN09) Cube string.string!string measure string is missing a COLUMNNAME property value
  • ora-14194 : only one subpartition may be rebuilt
  • ora-01682 : read-only DB cannot allocate temporary space in tablespace string
  • ora-15117 : command only operates on one diskgroup
  • ora-34342 : (MXDSS01) IMPORTANT: Analytic workspace string is read-only. Therefore, you will not be able to use the UPDATE command to save changes to it.
  • ora-29381 : plan/consumer_group string referred to by another plan and cannot be deleted
  • ora-31531 : could not find column string in CDC subscriber view string.string
  • ora-29264 : unknown or unsupported URL scheme
  • ora-31487 : cannot support begin dates or end dates in this configuration
  • ora-16743 : the status of redo transport service for standby database "string" is unknown
  • ora-13869 : Instance-wide SQL tracing on instance string is already enabled
  • ora-28606 : block too fragmented to build bitmap index (string,string)
  • ora-27419 : unable to determine valid execution date from repeat interval
  • ora-06259 : NETNTT: cannot read from remote process
  • ora-26041 : DATETIME/INTERVAL datatype conversion error
  • ora-02157 : no options specified for ALTER USER
  • ora-02447 : cannot defer a constraint that is not deferrable
  • ora-15109 : conflicting protection attributes specified
  • 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.