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-07-2017
ORA-31443

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

  • ora-13124 : unable to determine column id for column string
  • ora-16570 : operation requires restart of database "string"
  • ora-19503 : cannot obtain information on device, name="string", type="string", parms="string"
  • ora-33066 : (XSAGDNGL32) In AGGMAP workspace object, the hierarchy dimension QDR workspace object must be a hierarchy dimension of the relation.
  • ora-02092 : out of transaction table slots for distributed transaction
  • ora-26102 : relative file # in file header is string rather than string for file string
  • ora-13833 : SQL profile named string doesn't exist
  • ora-24395 : cannot reinitialize non-existent pool
  • ora-37104 : (XSVPART04) A partitioned variable must be dimensioned by a single partition template only.
  • ora-26004 : Tables loaded through the direct path may not be clustered
  • ora-02438 : Column check constraint cannot reference other columns
  • ora-16625 : cannot reach the database
  • ora-01523 : cannot rename data file to 'string' - file already part of database
  • ora-13262 : geometry column string does not exist in table string
  • ora-39772 : column array reset disallowed after OCI_CONTINUE or OCI_NEED_DATA
  • ora-07620 : smscre: illegal database block size
  • ora-28024 : must revoke grants of external roles to this role/user
  • ora-30977 : invalid Value Index option for XML Index
  • ora-09759 : osnsbt: bad message received.
  • ora-30382 : DROP MATERIALIZED VIEW string.string operation is not complete
  • ora-01469 : PRIOR can only be followed by a column name
  • ora-16205 : DDL skipped due to skip setting
  • ora-01409 : NOSORT option may not be used; rows are not in ascending order
  • ora-01610 : recovery using the BACKUP CONTROLFILE option must be done
  • ora-27128 : unable to determine pagesize
  • ora-01346 : LogMiner processed redo beyond specified reset log scn
  • ora-31617 : unable to open dump file "string" for write
  • ora-32141 : get method does not match the type of the parameter
  • ora-37026 : (XSMLTRESYNC01) Object workspace object cannot be resynced without dimension workspace object.
  • ora-29556 : object type has changed
  • 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.