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 : 25-06-2017
ORA-22278

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

  • ora-38850 : an enabled thread missing from control file
  • ora-10269 : Don't do coalesces of free space in SMON
  • ora-14312 : Value string already exists in partition string
  • ora-30738 : object "string" does not exist in schema "string"
  • ora-19209 : invalid or unsupported formatting argument
  • ora-12569 : TNS:packet checksum failure
  • ora-26725 : cannot downgrade apply handlers
  • ora-12642 : No session key
  • ora-14022 : creation of LOCAL partitioned cluster indices is not supported
  • ora-10382 : parallel query server interrupt (reset)
  • ora-22803 : object type contains zero attributes
  • ora-01016 : This function can be called only after a fetch
  • ora-15122 : ASM file name 'string' contains an invalid file number
  • ora-13147 : failed to generate MBR
  • ora-32121 : Source FILE is null
  • ora-02722 : osnpui: cannot send break message to orapop
  • ora-09932 : Close of ORACLE password file failed.
  • ora-16138 : end of log stream not received from primary
  • ora-30338 : illegal dimension hierachy name
  • ora-37151 : MDX parser initialization error
  • ora-04045 : errors during recompilation/revalidation of string.string
  • ora-26508 : null materialized view connection
  • ora-38703 : Type string in header is not a flashback database log file.
  • ora-16638 : could not get the instance status
  • ora-28368 : cannot auto-create wallet
  • ora-06804 : TLI Driver: could not bind an IPX address at initialization
  • ora-16216 : Log stream sequence error
  • ora-03001 : unimplemented feature
  • ora-01181 : file string created before last known RESETLOGS, cannot recreate
  • ora-07432 : unable to perform nested sleep
  • 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.