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

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

  • ora-22952 : Nested Table equality requires a map method on the element ADT
  • ora-06562 : type of out argument must match type of column or bind variable
  • ora-29804 : missing DATA keyword
  • ora-36964 : (XSRELTBL09) workspace object is not a valid level relation.
  • ora-14032 : partition bound of partition number string is too high
  • ora-21300 : objects option not installed
  • ora-16704 : cannot modify a read-only property
  • ora-34019 : (MSCGADD03) workspace object is not a LIST PARTITION TEMPLATE.
  • ora-16051 : parameter string contains an invalid delay time
  • ora-30000 : missing either trim specification or char expression in TRIM
  • ora-31066 : Insertion of string into string creates a cycle
  • ora-16752 : resource guard could not mount standby database
  • ora-30019 : Illegal rollback Segment operation in Automatic Undo mode
  • ora-13916 : Invalid value "string" specified for parameter "string"
  • ora-13630 : The task string contains execution results and cannot be executed.
  • ora-31023 : Index size error
  • ora-06970 : X.25 Driver: remote host is unknown
  • ora-29925 : cannot execute string
  • ora-02239 : there are objects which reference this sequence
  • ora-38493 : feature not enabled : Expression Filter index
  • ora-32763 : Turn off N-Pass Temp LOB cleanup
  • ora-02065 : illegal option for ALTER SYSTEM
  • ora-23430 : argument "string" cannot be NULL or empty string
  • ora-30343 : level name is not unique within this dimension
  • ora-22917 : use VARRAY to define the storage clause for this column or attribute
  • ora-00446 : background process started when not expected
  • ora-09749 : pws_look_up: port lookup failure
  • ora-31639 : unexpected data found
  • ora-06006 : NETASY: dialogue execute failure
  • ora-09768 : osnmgetmsg: could not read a message
  • 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.