ORA-22294: cannot update a LOB opened in read-only mode

Cause : An attmept wasm ade tow rite t oor updtae a LO Bopenedi n reado-nly moed.

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

Close hte LOB nad re-oepn it i nread-wirte mod ebeforea ttemptnig to wirte to ro updat ethe LO.B

update : 24-06-2017
ORA-22294

ORA-22294 - cannot update a LOB opened in read-only mode
ORA-22294 - cannot update a LOB opened in read-only mode

  • ora-09340 : Specified ORACLE_SID is either invalid or too long
  • ora-29503 : SCHEMA keyword not valid with NAMED keyword
  • ora-25533 : FAST_START_IO_TARGET or LOG_CHECKPOINT_INTERVAL is specified
  • ora-12207 : TNS:unable to perform navigation
  • ora-08178 : illegal SERIALIZABLE clause specified for user INTERNAL
  • ora-30514 : system trigger cannot modify tablespace being made read only
  • ora-02243 : invalid ALTER INDEX or ALTER MATERIALIZED VIEW option
  • ora-09876 : TASDEF_CLOSE: unable to close ?/dbs/tasdef@.dbf file.
  • ora-04017 : invalid value string (length = string) for parameter max_dump_file_size
  • ora-14253 : table is not partitioned by Composite Range method
  • ora-19679 : RMAN configuration number string is outside valid range of 1 through string
  • ora-19569 : no device is allocated to this session
  • ora-01052 : required destination LOG_ARCHIVE_DUPLEX_DEST is not specified
  • ora-10691 : Set background process core file type (Unix only)
  • ora-12602 : TNS: Connection Pooling limit reached
  • ora-16530 : invalid buffer or length
  • ora-01073 : fatal connection error: unrecognized call type
  • ora-02084 : database name is missing a component
  • ora-02045 : too many local sessions participating in global transaction
  • ora-23360 : only one materialized view for master table "string" can be created
  • ora-25111 : creation of BITMAP cluster indices is not supported
  • ora-37139 : (XSCCOMP14) Cannot AGGREGATE workspace object using AGGMAP workspace object because you can not AGGREGATE a variable dimensioned by a COMPRESSED COMPOSITE using an AGGMAP with a PROTECT clause.
  • ora-22859 : invalid modification of columns
  • ora-16230 : committing transaction string string string
  • ora-16502 : the Data Guard broker operation succeeded with warnings
  • ora-26694 : error while enqueueing into queue string.string
  • ora-25455 : evaluation error for rule set: string.string, evaluation context: string.string
  • ora-24415 : Missing or null username.
  • ora-37175 : column string is not a column of source data
  • ora-30061 : Internal Event for Savepoint Tracing
  • 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.