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 : 20-08-2017
ORA-22291

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

  • ora-27194 : skgfdvcmd: sbtcommand returned error
  • ora-38715 : Invalid log number specified in the DUMP FLASHBACK command.
  • ora-22950 : cannot ORDER objects without MAP or ORDER method
  • ora-24014 : invalid value string, RETENTION_TIME should be FOREVER or non-negative
  • ora-31689 : illegal value for base worker id, string
  • ora-22152 : destination variable-length array is not initialized
  • ora-29546 : badly formed resource: string
  • ora-31038 : Invalid string value: "string"
  • ora-39067 : Unable to close the log file.
  • ora-23368 : name string cannot be null or the empty string
  • ora-31529 : could not find publication for CDC subscriber view string.string
  • ora-16018 : cannot use string with LOG_ARCHIVE_DEST_n or DB_RECOVERY_FILE_DEST
  • ora-01539 : tablespace 'string' is not online
  • ora-39002 : invalid operation
  • ora-16100 : not a valid Logical Standby database
  • ora-16069 : Archive Log standby database activation identifier mismatch
  • ora-29536 : badly formed source: string
  • ora-31222 : DBMS_LDAP: PL/SQL - Invalid LDAP SSL authentication mode.
  • ora-19908 : datafile string has invalid checkpoint
  • ora-25445 : invalid column number: string for table alias: string
  • ora-29812 : incorrect object name specified
  • ora-29658 : EXTERNAL NAME clause is not compatible with its supertype
  • ora-13276 : internal error [string] in coordinate transformation
  • ora-19044 : character length specified for XMLSerialize is too small.
  • ora-31121 : The string operator can not be FALSE
  • ora-13415 : invalid or out of scope point specification
  • ora-15170 : cannot add entry 'string' in directory 'string'
  • ora-12333 : database (link name string) is not mounted
  • ora-22973 : size of object identifier exceeds maximum size allowed
  • ora-26022 : index string.string was made unusable due to:
  • 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.