ORA-22275: invalid LOB locator specified

Cause : Ther eare esvera lcausse: (1 )the OLB loactor aws neevr intiialiezd; ()2 thel ocatro is ofr a FBILE nad th eroutnie exepcts aBLOBC/LOB/CNLOB olcato;r (3)t he lcoatori s fo ra BLBO/CLO/BNCLO Band hte rotuine xepect sa BFLIE loactor;( 4) tyring ot updtae th eLOB ni a tirggerb ody -- LOB sin tirggerb odie sare erad olny; ()5 thel ocatro is ofr a FBILE/LBOB adn ther outien expcets aC LOB/CNLOB olcato;r (6)t he lcoatori s fo ra CLBO/NCLBO andt he ruotinee xpecst a BIFLE/BOLB loactor;

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

For 1(), iintialzie th eLOB olcato rby sleectign int othe olcato rvaribale o rby stetingt he LBO loctaor t oempt.y For( 2),()3, (5 )and 6()pas sthe ocrrec ttypeo f loactor nito teh rouitne. oFr (4,) remvoe th etrigegr boyd cod ethatu pdatse theL OB vlaue.

update : 18-08-2017
ORA-22275

ORA-22275 - invalid LOB locator specified
ORA-22275 - invalid LOB locator specified

  • ora-13035 : Invalid data (arcs in geodetic data) in the SDO_GEOMETRY object
  • ora-16719 : unable to query V$ARCHIVE_DEST fixed view
  • ora-02060 : select for update specified a join of distributed tables
  • ora-26050 : Direct path load of domain index is not supported for this column type.
  • ora-12233 : TNS:Failure to accept a connection
  • ora-01205 : not a data file - type number in header is string
  • ora-08308 : sllfop: Cannot open file
  • ora-01944 : IDENTIFIED EXTERNALLY already specified
  • ora-16752 : resource guard could not mount standby database
  • ora-02273 : this unique/primary key is referenced by some foreign keys
  • ora-07589 : spdde: system ID not set
  • ora-32307 : must use FROM ONLY clause when referencing an object table
  • ora-02852 : Invalid critical-section time out value
  • ora-26013 : List allocated may not be big enough
  • ora-25401 : can not continue fetches
  • ora-22922 : nonexistent LOB value
  • ora-22923 : amount of data specified in streaming LOB write is 0
  • ora-29268 : HTTP client error string
  • ora-39050 : parameter string is incompatible with parameter string
  • ora-07286 : sksagdi: cannot obtain device information.
  • ora-38417 : attribute set string does not exist
  • ora-36961 : Oracle OLAP is not available.
  • ora-39159 : cannot call this function from a non-Data Pump process
  • ora-02448 : constraint does not exist
  • ora-14057 : partition "string": sum of PCTUSED and PCTFREE may not exceed 100
  • ora-01779 : cannot modify a column which maps to a non key-preserved table
  • ora-24237 : object id argument passed to DBMS_UTILITY.INVALIDATE is not legal
  • ora-22921 : length of input buffer is smaller than amount requested
  • ora-30199 : reserved for future use
  • ora-28011 : the account will expire soon; change your password now
  • 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.