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 : 25-05-2017
ORA-22927

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

  • ora-01592 : error converting Version 7 rollback segment (string) to Oracle 8 format
  • ora-09275 : CONNECT INTERNAL is not a valid DBA connection
  • ora-24006 : cannot create QUEUE, string already exists
  • ora-16088 : archive log has not been completely archived
  • ora-08181 : specified number is not a valid system change number
  • ora-12022 : materialized view log on "string"."string" already has rowid
  • ora-10916 : TABLESPACE GROUP already specified
  • ora-25259 : cannot specify protocol for agent
  • ora-22283 : filename contains characters that refer to parent directory
  • ora-00379 : no free buffers available in buffer pool string for block size stringK
  • ora-13022 : polygon crosses itself
  • ora-26002 : Table string has index defined upon it.
  • ora-01145 : offline immediate disallowed unless media recovery enabled
  • ora-13857 : Invalid module name
  • ora-01332 : internal Logminer Dictionary error
  • ora-07497 : sdpri: cannot create trace file 'string'; errno = string.
  • ora-23417 : unknown materialized view type: string
  • ora-00402 : database changes by release string cannot be used by release string
  • ora-39139 : Data Pump does not support XMLSchema objects. string will be skipped.
  • ora-09815 : File name buffer overflow
  • ora-09921 : Unable to get information label from connection
  • ora-38504 : this operator not allowed with the configured attribute set
  • ora-13605 : The specified task or object string does not exist for the current user.
  • ora-02775 : Invalid request done signal
  • ora-00483 : During shutdown a process abnormally terminated
  • ora-12690 : Server Authentication failed, login cancelled
  • ora-37016 : (XSACQUIRE01) You must specify objects to acquire for the ACQUIRE command.
  • ora-24120 : invalid string parameter passed to DBMS_REPAIR.string procedure
  • ora-02404 : specified plan table not found
  • ora-13415 : invalid or out of scope point specification
  • 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.