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 : 21-08-2017

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

  • ora-16014 : log string sequence# string not archived, no available destinations
  • ora-22282 : non-contiguous append to a buffering enabled LOB not allowed
  • ora-01201 : file string header failed to write correctly
  • ora-02359 : internal error setting attribute string
  • ora-22818 : subquery expressions not allowed here
  • ora-24759 : invalid transaction start flags
  • ora-19957 : database should have no datafiles in unknown state
  • ora-25296 : Queue Table string has a buffered queue string
  • ora-33070 : (XSAGDNGL34) In AGGMAP workspace object, all QDRs of dimension workspace object must map to the same dimension position.
  • ora-07849 : sllfsk: $GET failure
  • ora-12590 : TNS:no I/O buffer
  • ora-02173 : invalid option for DROP TABLESPACE
  • ora-19380 : invalid plan filter
  • ora-07452 : specified resource manager plan does not exist in the data dictionary
  • ora-14188 : sub-partitioning columns must form a subset of key columns of a UNIQUE index
  • ora-10643 : Database should be mounted in restricted mode and Exclusive mode
  • ora-06261 : NETNTT: nrange() failed
  • ora-01060 : array binds or executes not allowed
  • ora-09841 : soacon: Name translation failure.
  • ora-24075 : cannot specify agent with NULL address and non-NULL protocol
  • ora-00083 : warning: possibly corrupt SGA mapped
  • ora-07232 : slemcc: fclose error.
  • ora-31091 : empty string specified as a SQL name
  • ora-30042 : Cannot offline the undo tablespace
  • ora-00231 : snapshot control file has not been named
  • ora-12014 : table 'string' does not contain a primary key constraint
  • ora-31103 : Resource locked in shared mode. Cannot add exclusive lock
  • ora-29801 : missing RETURN keyword
  • ora-36612 : (XSLMS01) invalid OLAP message number: value
  • ora-19771 : cannot rename change tracking file while database is open
  • 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.