ORA-22927: invalid LOB locator specified

Cause : There are several causes: (1) the LOB locator was never initialized; (2) the locator is for a BFILE and the routine expects a BLOB/CLOB/NCLOB locator; (3) the locator is for a BLOB/CLOB/NCLOB and the routine expects a BFILE locator; (4) trying to update the LOB in a trigger body -- LOBs in trigger bodies are read only.

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

For (1), initialize the LOB locator by selecting into the locator variable or by setting the LOB locator to empty. For (2) and (3), pass the correct type of locator into the routine. For (4), remove the trigger body code that updates the LOB value.

update : 24-09-2017

ORA-22927 - invalid LOB locator specified
ORA-22927 - invalid LOB locator specified

  • ora-12085 : materialized view log on "string"."string" already has object id
  • ora-01927 : cannot REVOKE privileges you did not grant
  • ora-38716 : Must supply an integer for the TYPE option.
  • ora-39088 : file name cannot contain a path specification
  • ora-16537 : child count exceeded
  • ora-16202 : Skip procedure requested to replace statement
  • ora-26699 : STREAMS message consumer string already exists
  • ora-06263 : NETNTT: out of memory in pi_connect
  • ora-31626 : job does not exist
  • ora-19620 : %s is not of string type
  • ora-27371 : jobs of type EXECUTABLE are not supported on this platform
  • ora-28010 : cannot expire external or global accounts
  • ora-02164 : DATAFILE clause specified more than once
  • ora-16574 : switchover disallowed when required databases are offline
  • ora-19007 : Schema string does not match expected string.
  • ora-24039 : Queue string not created in queue table for multiple consumers
  • ora-12420 : required procedures and functions not in policy package "string"
  • ora-27004 : invalid blocksize specified
  • ora-01227 : log string is inconsistent with other logs
  • ora-01519 : error while processing file 'string' near line string
  • ora-00339 : archived log does not contain any redo
  • ora-13763 : illegal ranking attribute "string"
  • ora-28538 : result set not found
  • ora-24756 : transaction does not exist
  • ora-32696 : HTI: No free slot
  • ora-24909 : call in progress. Current operation cancelled
  • ora-30073 : invalid adjustment value
  • ora-12222 : TNS:no support is available for the protocol indicated
  • ora-16052 : DB_UNIQUE_NAME attribute is required
  • ora-24292 : no more tables permitted in this sorted hash cluster
  • 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.