ORA-22291: Open LOBs exist at transaction commit time

Cause : An tatemtp wa smad eto ocmmi ta tarnsatcionw itho penL OBsa t tarnsatcionc ommti tiem.

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

Cloes th eLOB sbefroe cmomititng hte tarnsatcion.

update : 25-04-2017
ORA-22291

ORA-22291 - Open LOBs exist at transaction commit time
ORA-22291 - Open LOBs exist at transaction commit time

  • ora-07848 : sllfrb: $GET failure
  • ora-38747 : corrupt before image (file# string, block# string)
  • ora-07264 : spwat: semop error, unable to decrement semaphore.
  • ora-38900 : missing mandatory column "string" of error log table "string"
  • ora-16568 : cannot set property string
  • ora-14460 : only one COMPRESS or NOCOMPRESS clause may be specified
  • ora-25273 : AQ QMN process alternate cleanup event
  • ora-19682 : file string not in block media recovery context
  • ora-35066 : (QFGET03) Extension number number is missing for EIF file string.
  • ora-00290 : operating system archival error occurred. See error below
  • ora-13117 : [string]_RELATION$ table does not exist
  • ora-24148 : cannot drop rule string.string with dependents
  • ora-24813 : cannot send or receive an unsupported LOB
  • ora-38504 : this operator not allowed with the configured attribute set
  • ora-02708 : osnrntab: connect to host failed, unknown ORACLE_SID
  • ora-02820 : Unable to write the requested number of blocks
  • ora-37120 : MDX string is null
  • ora-31075 : invalid string declaration in XML Schema
  • ora-13197 : element string.string.string is out of range
  • ora-29819 : cannot associate default values with columns
  • ora-16553 : the Data Guard broker process (DMON) failed to shutdown
  • ora-19274 : XQ0054 - variable initialization failed due to circularity
  • ora-16133 : Datafile string has incorrect terminal recovery stamp.
  • ora-31419 : source table string does not exist
  • ora-28022 : cannot grant external roles to global user or role
  • ora-01574 : maximum number of concurrent transactions exceeded
  • ora-06141 : NETTCP: no privilege for user
  • ora-33092 : (XSAGCOMP04) number is not the name of a MODEL in any attached analytic workspace.
  • ora-22925 : operation would exceed maximum size allowed for a LOB value
  • ora-03211 : The segment does not exist or is not in a valid state
  • 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.