ORA-24775: cannot prepare or commit transaction with non-zero lock value

Cause : nAa ttmetpw sam da eotd teca hht ertnaastcoi niwhta n noz-re oolkcv laeu.

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

eDathct eht arsncaitnow ti holkcv laeus tet oezora dnt eh nrt yotp erapero rocmmtit eht arsncaitno.

update : 27-04-2017

ORA-24775 - cannot prepare or commit transaction with non-zero lock value
ORA-24775 - cannot prepare or commit transaction with non-zero lock value

  • ora-31494 : could not activate a LogMiner session
  • ora-08112 : a composite partition may not be coalesced as a whole
  • ora-00290 : operating system archival error occurred. See error below
  • ora-01535 : rollback segment 'string' already exists
  • ora-01182 : cannot create database file string - file is in use or recovery
  • ora-16124 : transaction string string string is waiting on another transaction
  • ora-02798 : Invalid number of requests
  • ora-24021 : queue table definition not imported for string.string
  • ora-14251 : Specified subpartition does not exist
  • ora-13618 : The specified value is not a valid value for procedure argument string.
  • ora-28278 : No domain policy registered for password based GLOBAL users.
  • ora-13828 : generated SQL profile name string already exists
  • ora-26680 : object type not supported
  • ora-31430 : subscriber view exists
  • ora-29250 : Invalid index specifed in call to dbms_sql.bind_array
  • ora-29902 : error in executing ODCIIndexStart() routine
  • ora-00450 : background process 'string' did not start
  • ora-16200 : Skip procedure requested to skip statement
  • ora-36810 : (XSTBLFUNC05) Analytic workspace object number does not exist.
  • ora-16612 : string value too long for attribute "string"
  • ora-13017 : unrecognized line partition shape
  • ora-36650 : (XSDUNION10) Concat dimension workspace object cannot be changed to UNIQUE. Leaves workspace object and workspace object share the value number.
  • ora-38422 : invalid datatype for the attribute: string
  • ora-14519 : Conflicting tablespace blocksizes for string string: Tablespace string block size string [string] conflicts with previously specified/implied tablespace string block size string [string]
  • ora-01103 : database name 'string' in control file is not 'string'
  • ora-16571 : Data Guard configuration file creation failure
  • ora-09836 : addCallback: could not add a port to the callback set.
  • ora-19112 : error raised during evaluation: string
  • ora-37079 : (XSMCSESS07) Aggmap workspace object cannot be used for AGGREGATE.
  • ora-31220 : DBMS_LDAP: PL/SQL - Invalid LDAP SSL wallet location.
  • 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.