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

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-07204 : sltln: name translation failed due to lack of output buffer space.
  • ora-29892 : indextypes with array DML do not support the given data type
  • ora-33338 : (DSSEXIST05) You cannot specify the EXPTEMP analytic workspace.
  • ora-23325 : parameter type is not string
  • ora-00610 : Internal error code
  • ora-38306 : this object is not recoverable standalone
  • ora-38445 : TOP clause not allowed with no statistics
  • ora-12026 : invalid filter column detected
  • ora-38856 : cannot mark instance string (redo thread string) as enabled
  • ora-02088 : distributed database option not installed
  • ora-00231 : snapshot control file has not been named
  • ora-22929 : invalid or missing directory name
  • ora-08100 : index is not valid - see trace file for diagnostics
  • ora-02238 : filename lists have different numbers of files
  • ora-27207 : syntax error in device PARMS - parentheses mismatch or missing
  • ora-32339 : cannot alter materialized view with the PMOP
  • ora-30386 : invalid SQL statement for DECLARE_REWRITE_EQUIVALENCE
  • ora-24142 : invalid ruleset name
  • ora-36684 : (XSDPART22) You cannot rename values of DIMENSION workspace object because it is the partition dimension of RANGE PARTITION TEMPLATE workspace object
  • ora-12034 : materialized view log on "string"."string" younger than last refresh
  • ora-00910 : specified length too long for its datatype
  • ora-36610 : (XSLMS00) Unable to locate a message file for OLAP message: value
  • ora-01271 : Unable to create new file name for file string
  • ora-36831 : (XSLMGEN01) View token cannot be NA
  • ora-14630 : subpartition resides in offlined tablespace
  • ora-38416 : A stored attribute may not be longer then 300 characters.
  • ora-03214 : File Size specified is smaller than minimum required
  • ora-29250 : Invalid index specifed in call to dbms_sql.bind_array
  • ora-01635 : rollback segment #string specified not available
  • ora-00104 : deadlock detected; all public servers blocked waiting for resources
  • 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.