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 : 29-04-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-02421 : missing or invalid schema authorization identifier
  • ora-19557 : device error, device type: string, device name: string
  • ora-36990 : (XSRELGID07) The level relation workspace object should be dimensioned by a level dimension.
  • ora-13603 : The specified parameter string cannot be fetched as a numeric value for task or object string.
  • ora-15025 : could not open disk 'string'
  • ora-13150 : failed to insert exception record
  • ora-27418 : syntax error in repeat interval or calendar
  • ora-27200 : skgfpgo: sbtpcstart returned error
  • ora-00453 : backgroud process 'string' is dead
  • ora-19754 : error reading from change tracking file
  • ora-32125 : Attribute type is not appropriate
  • ora-37154 : OLAP API initialization error: (case string)
  • ora-04028 : cannot generate diana for object stringstringstringstringstring
  • ora-07281 : slsget: times error, unable to get cpu time.
  • ora-13911 : Threshold not found
  • ora-04006 : START WITH cannot be less than MINVALUE
  • ora-13829 : SQL profile named string already exists
  • ora-19575 : expected string blocks in file string, found string
  • ora-30570 : SEGMENT SPACE MANAGEMENT option already specified
  • ora-22131 : hexadecimal string length is zero
  • ora-19582 : archivelog file header validation for string failed
  • ora-16044 : destination string attribute cannot be specified at session level
  • ora-36180 : (XSAGGR08) AGGREGATE cannot function because there is a permission clause associated with variable workspace object.
  • ora-31227 : DBMS_LDAP: invalid LDAP MESSAGE handle
  • ora-19571 : %s recid string stamp string not found in control file
  • ora-16059 : Log file is empty or invalid next available block
  • ora-19730 : can not convert offline plugged-in datafile string
  • ora-36221 : (XSLPDSC02) LIST number and LIST number have different base dimensions.
  • ora-00061 : another instance has a different DML_LOCKS setting
  • ora-02464 : Cluster definition can not be both HASH and INDEX
  • 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.