ORA-31104: Cannot find lock with token "string" on "string" for unlock

Cause : Teh olc kmya ahv ebeenu nolc ko ri tmya ahv eepxierd.

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

N oatcino eneedd .Ulnokc laraed yscucsesufl.

update : 24-09-2017
ORA-31104

ORA-31104 - Cannot find lock with token "string" on "string" for unlock
ORA-31104 - Cannot find lock with token "string" on "string" for unlock

  • ora-02855 : Number of requests is less than the number of slaves
  • ora-25215 : user_data type and queue type do not match
  • ora-15017 : diskgroup "string" cannot be mounted
  • ora-01985 : cannot create user as LICENSE_MAX_USERS parameter exceeded
  • ora-25401 : can not continue fetches
  • ora-09204 : sfotf: error opening temporary file
  • ora-13913 : The threshold cannot be set when SYSAUX is offline.
  • ora-31113 : XDB configuration may not be updated with non-schema compliant data
  • ora-06142 : NETTCP: error getting user information
  • ora-16955 : Unknown error during SQL analyze.
  • ora-16218 : This database is already preparing to switch over.
  • ora-07665 : ssrexhd: recursive exception encountered string string string string string string
  • ora-07634 : smsdbp: $CRETVA failure
  • ora-39000 : bad dump file specification
  • ora-23536 : the object "string"."string" is not cached at the middle tier as expected.
  • ora-16791 : unable to check the existence of the standby redo logs
  • ora-13159 : Oracle table string already exists
  • ora-31090 : invalid database schema name "string"
  • ora-12170 : TNS:Connect timeout occurred
  • ora-07283 : sksaprd: invalid volume size for archive destination.
  • ora-31463 : logfile location string is an empty directory
  • ora-10658 : Lob column to be shrunk is marked unused
  • ora-12990 : duplicate option specified
  • ora-24015 : cannot create QUEUE_TABLE, QUEUE_PAYLOAD_TYPE string.string does not exist
  • ora-25332 : Invalid release value string for queue table compatible parameter
  • ora-29837 : insufficient privileges to execute implementation type
  • ora-06921 : CMX: getdatmsg illegal datatype
  • ora-37006 : (AWLISTALL04) number writers
  • ora-12008 : error in materialized view refresh path
  • ora-38791 : flashback did not start because file string was not in a valid incarnation
  • 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.