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

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

  • ora-24794 : no active DTP service found
  • ora-13402 : the rasterType is null or not supported
  • ora-16248 : RFS connections not permitted during Terminal Apply
  • ora-28557 : unknown string for database link to non-Oracle system
  • ora-40251 : no support vectors were found
  • ora-25180 : PCTTHRESHOLD only valid for certain table organizations
  • ora-28348 : index defined on the specified column cannot be encrypted
  • ora-29547 : Java system class not available: string
  • ora-12490 : DBHIGH cannot be lowered
  • ora-25268 : didnt dequeue in browse mode with get signature option
  • ora-23414 : materialized view log for "string"."string" does not record rowid values
  • ora-04077 : WHEN clause cannot be used with table level triggers
  • ora-19115 : too many context items specified
  • ora-31508 : invalid parameter value for synchronous change set
  • ora-36991 : (XSRELGID08) The level relation and level order valueset provide inconsistent level mappings.
  • ora-32051 : mapping service not available
  • ora-22345 : recompile type string.string before attempting this operation
  • ora-02446 : CREATE TABLE ... AS SELECT failed - check constraint violated
  • ora-22862 : specified object identifier doesn't match existing object identifier
  • ora-16661 : the standby database needs to be reinstated
  • ora-29864 : analyzing domain indexes marked LOADING/FAILED not supported
  • ora-12079 : materialized view options require COMPATIBLE parameter to be string or greater
  • ora-25121 : MINIMUM EXTENT value greater than maximum extent size
  • ora-34900 : (PPWKDAYS00) At least 7 day names must be given. Only number were provided.
  • ora-06953 : Not enough virtual memory
  • ora-30178 : duplicate flag used in a format specification
  • ora-02899 : smscre: Cannot create SGA with Extended Shared Memory feature
  • ora-30448 : internal data of the advisor repository is inconsistent
  • ora-32762 : Turn on Temp LOB Ref Count Tracing
  • ora-25015 : cannot perform DML on this nested table view column
  • 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.