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

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

  • ora-17510 : Attempt to do i/o beyond file size
  • ora-04934 : unable to obtain the current sequence number
  • ora-26566 : Couldn't open connect to string
  • ora-23535 : instantiating templates from multiple back ends is not allowed.
  • ora-14503 : only one partition name can be specified
  • ora-29533 : attempt to overwrite class or resource string while defining or compiling string.string
  • ora-02186 : tablespace resource privilege may not appear with other privileges
  • ora-06977 : X.25 Driver: X.25 Level 2 failure
  • ora-02733 : osnsnf: database string too long
  • ora-39068 : invalid master table data in row with PROCESS_ORDER=string
  • ora-15202 : cannot create additional ASM internal change segment
  • ora-15186 : ASMLIB error function = [string], error = [string], mesg = [string]
  • ora-06800 : TLI Driver: SQL*Net SPX client went away during reconnect
  • ora-09837 : addCallback: could not add allocate a callback link.
  • ora-25198 : only range, list, and hash partitioning are supported for index-organized table
  • ora-12699 : Native service internal error
  • ora-00023 : session references process private memory; cannot detach session
  • ora-25447 : encountered errors during evaluation of rule string.string
  • ora-19582 : archivelog file header validation for string failed
  • ora-07390 : sftopn: translate error, unable to translate file name.
  • ora-01725 : USERENV('COMMITSCN') not allowed here
  • ora-21603 : property id [string] is invalid
  • ora-24400 : error occured while creating connections in the pool
  • ora-32015 : unable to restore SPFILE
  • ora-12736 : Instant Client Light: unsupported server national character set string
  • ora-39076 : cannot delete job string for user string
  • ora-37999 : Serious OLAP error: string. Please contact Oracle Technical Support.
  • ora-24316 : illegal handle type
  • ora-27473 : argument string does not exist
  • ora-22898 : existing scope clause on "string" points to a table other than the one mentioned in the referential constraint
  • 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.