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-07-2017
ORA-22927

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

  • ora-01163 : SIZE clause indicates string (blocks), but should match header string
  • ora-04098 : trigger 'string.string' is invalid and failed re-validation
  • ora-19592 : wrong string conversation type
  • ora-01559 : MAXEXTENTS for rollback segment must be greater than 1
  • ora-23439 : refresh group template already exists
  • ora-06406 : NETCMN: error sending break message
  • ora-25135 : cannot use the SINGLE TABLE option
  • ora-23416 : table "string"."string" does not contain a primary key constraint
  • ora-19509 : failed to delete sequential file, handle="string", parms="string"
  • ora-27411 : empty string is not a valid repeat interval.
  • ora-19581 : no files have been named
  • ora-01906 : BACKUP keyword expected
  • ora-28527 : Heterogeneous Services datatype mapping error
  • ora-09360 : Windows 3.1 Two-Task driver unable to allocate context area
  • ora-30131 : number of keys being set exceeds allocation
  • ora-30938 : No prefix defined for namespace 'string' (particle string)
  • ora-00234 : error in identifying or opening snapshot or copy control file
  • ora-06514 : PL/SQL: The remote call cannot be handled by the server
  • ora-09365 : Windows 3.1 Two-Task driver unable to destroy hidden window
  • ora-08342 : sropen: failed to open a redo server connection
  • ora-38719 : Invalid DUMP FLASHBACK object.
  • ora-12838 : cannot read/modify an object after modifying it in parallel
  • ora-16219 : This database is not preparing to switch over.
  • ora-36910 : (XSAGDNGL47) In AGGMAP workspace object, DYNAMIC MODEL workspace object can only edit the top level of its matching relation hierarchy.
  • ora-09843 : soacon: Archmon unable to create named pipe.
  • ora-19571 : %s recid string stamp string not found in control file
  • ora-07276 : no dba group in /etc/group.
  • ora-28535 : invalid Heterogeneous Services context
  • ora-01128 : cannot start online backup - file string is offline
  • ora-13434 : GeoRaster metadata cellRepresentation error
  • 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.