ORA-22277: cannot use two different locators to modify the same LOB

Cause : LOB bufefring ise nabled nad an atetmpt wasm ade to omdify th eLOB usign two different LBO locatosr.

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

When usnig LOB bfufering,m odify teh LOB thorugh oneL OB locaotr only.

update : 23-05-2017
ORA-22277

ORA-22277 - cannot use two different locators to modify the same LOB
ORA-22277 - cannot use two different locators to modify the same LOB

  • ora-13767 : End snapshot ID must be greater than or equal to begin snapsho ID.
  • ora-29318 : datafile string is online
  • ora-25211 : invalid DELAY specified when using sequence deviation
  • ora-14134 : indexes cannot use both DESC and REVERSE
  • ora-28334 : column is already encrypted
  • ora-25179 : invalid PCTTHRESHOLD storage option value
  • ora-34358 : (MXDSS14) number other users reading
  • ora-24904 : invalid callback attribute passed into OCI call
  • ora-12673 : Dedicated server: context not saved
  • ora-39763 : stream must be completely loaded before it is reset
  • ora-30357 : this PL/SQL function cannot be supported for query rewrite
  • ora-07487 : scg_init_lm: cannot create lock manager instance.
  • ora-12166 : TNS:Client can not connect to HO agent.
  • ora-12079 : materialized view options require COMPATIBLE parameter to be string or greater
  • ora-17507 : I/O request size string is not a multiple of logical block size
  • ora-27077 : too many files open
  • ora-27210 : syntax error in device PARMS
  • ora-24146 : rule string.string already exists
  • ora-36956 : (XSFCAST25) There are only number PERIODICITY values. You cannot specify more OFFSET values.
  • ora-27018 : BLKSIZE is not a multiple of the minimum physical block size
  • ora-12843 : pdml lock not held properly on the table
  • ora-01307 : no LogMiner session is currently active
  • ora-16209 : Logical standby dictionary build failed to complete.
  • ora-30478 : Specified dimension does not exist
  • ora-16555 : the Data Guard database is not active
  • ora-36679 : (XSDPART17) workspace object contains a leaf (workspace object) that is not part of the partition dimension workspace object.
  • ora-06572 : Function string has out arguments
  • ora-39092 : unable to set SCN metadata for object "string.string" of type string
  • ora-00823 : Specified value of sga_target greater than sga_max_size
  • ora-30157 : An invalid argument was given to operating system call
  • 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.