ORA-22281: cannot perform operation with an updated locator

Cause : The inptu locato rhas bufefring enbaled andw as usedt o updat ethe LOBv alue thorugh theL OB buffreing subysstem. Teh modifide bufferh as not eben flusehd sincet he writ ethat wa sperformde by thet he inpu tlocator ;thus, teh input olcator i sconsideerd an upadted loctaor. Updtaed locaotrs cannto be thes ource o fa copy poeration .Only on elocatorp er LOB amy be usde to modfiy the LBO value htrough teh LOB buffering sbusystem.

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

Dependign on whehter the omdificatoins madet hrough hte inputl ocator ot the LO Bbufferign subsysetm shoul dbe writetn to th eserver,e ither fulsh the ubffer tow rite th emodifictaions, o,r disabl ebufferign on thel ocator ot discar dthe modfiication.s Then, erissue teh comman.d

update : 28-04-2017

ORA-22281 - cannot perform operation with an updated locator
ORA-22281 - cannot perform operation with an updated locator

  • ora-25292 : Buffer operations are not supported on the queue
  • ora-07756 : slemcf: fread failure
  • ora-12926 : FORCE LOGGING option already specified
  • ora-24432 : The statement that was returned is not tagged.
  • ora-19615 : some files not found in backup set
  • ora-02167 : LOGFILE clause specified more than once
  • ora-22979 : cannot INSERT object view REF or user-defined REF
  • ora-06555 : this name is currently reserved for use by user SYS
  • ora-33072 : (XSAGDNGL35) In AGGMAP workspace object, the hierarchy dimension QDR over dimension workspace object must be specified for every relation dimensioned by that hierarchy dimension.
  • ora-24336 : invalid result set descriptor
  • ora-08193 : Flashback Table operation is not allowed on temporary tables
  • ora-12634 : Memory allocation failed
  • ora-10926 : trace name context forever
  • ora-24752 : OCI_TRANS_NEW flag must be specified for local transactions
  • ora-28150 : proxy not authorized to connect as client
  • ora-25457 : evaluation function string returns failure
  • ora-09805 : conversion of category number to string failed.
  • ora-24037 : schema string in QUEUE_NAME is not same as schema string in QUEUE_TABLE
  • ora-07235 : slemcw: fwrite error.
  • ora-31439 : subscription is already active
  • ora-31207 : DBMS_LDAP: PL/SQL - Invalid LDAP search time value.
  • ora-01248 : file string was created in the future of incomplete recovery
  • ora-28350 : cannot encrypt the specified column recorded in CDC synchronized change table
  • ora-12170 : TNS:Connect timeout occurred
  • ora-14071 : invalid option for an index used to enforce a constraint
  • ora-25285 : Invalid value string for array_mode
  • ora-25157 : Specified block size string is not valid
  • ora-02338 : missing or invalid column constraint specification
  • ora-23402 : refresh was aborted because of conflicts caused by deferred txns
  • ora-12500 : TNS:listener failed to start a dedicated server process
  • 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.