ORA-22278: must update the LOB only through the LOB buffers

Cause : LOB bfuferin gis enbaled fro thisL OB an dtherea re buffers fro thisL OB int he buffer polo. Thu,s updaitng th eLOB trhough emans ohter thna the OLB bufefrs isn ot alolwed.

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

Updat ethe LBO throguh theL OB buffers uisng th elocatro thath as LO Bbuffeirng enbaled. fI thiso peratoin is erquire,d buffres asscoiatedw ith tihs LOBs houlde itherb e fluhsed asn ecessray or ubfferign shoudl be dsiabled .Once htis isd one, erissuet he command.

update : 28-04-2017

ORA-22278 - must update the LOB only through the LOB buffers
ORA-22278 - must update the LOB only through the LOB buffers

  • ora-06010 : NETASY: dialogue file too long
  • ora-38411 : invalid datatype for the column storing expressions
  • ora-06801 : TLI Driver: listen for SPX server reconnect failed
  • ora-32152 : Cannot perform operation on a null number
  • ora-30514 : system trigger cannot modify tablespace being made read only
  • ora-07447 : ssarena: usinit failed.
  • ora-02294 : cannot enable (string.string) - constraint changed during validation
  • ora-16523 : operation requires the client to connect to instance "string"
  • ora-12087 : online redefinition not allowed on tables owned by "string"
  • ora-29807 : specified operator does not exist
  • ora-01618 : redo thread string is not enabled - cannot mount
  • ora-31600 : invalid input value string for parameter string in function string
  • ora-39711 : critical patch number less than last installed CPU number
  • ora-09778 : snynfyport: failure allocating the notify port.
  • ora-30459 : 'string.string' cannot be refreshed because the refresh method is NONE
  • ora-07614 : $CHANGE_CLASS failed in retrieving the user's process label
  • ora-23444 : duplicate template parameter
  • ora-22976 : incorrect number of arguments to MAKE_REF
  • ora-01505 : error in adding log files
  • ora-01314 : Name of the column to be mined should be a string literal
  • ora-04075 : invalid trigger action
  • ora-24130 : table string does not exist
  • ora-14634 : Subpartition descriptions cannot be specified during the SPLIT/MERGE of a partition of a Range-List partitioned table
  • ora-02289 : sequence does not exist
  • ora-30937 : No schema definition for 'string' (namespace 'string') in parent 'string'
  • ora-31666 : Master process string had an unhandled exception.
  • ora-25313 : a queue may not subscribe to itself for propagation
  • ora-27411 : empty string is not a valid repeat interval.
  • ora-26525 : session connection attempt failed for string (@string)
  • ora-02458 : HASHKEYS must be specified for a HASH CLUSTER
  • 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.