ORA-22922: nonexistent LOB value

Cause : The LOB value associated with the input locator does not exist. The information in the locator does not refer to an existing LOB.

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

Repopulate the locator by issuing a select statement and retry the operation.

update : 25-06-2017
ORA-22922

ORA-22922 - nonexistent LOB value
ORA-22922 - nonexistent LOB value

  • ora-19503 : cannot obtain information on device, name="string", type="string", parms="string"
  • ora-38786 : Flash recovery area is not enabled.
  • ora-40105 : input data incompatible with model signature
  • ora-29847 : cannot create a local domain index on a partitioned index-organized table
  • ora-03244 : No free space found to place the control information
  • ora-27064 : cannot perform async I/O to file
  • ora-13201 : invalid parameters supplied in CREATE INDEX statement
  • ora-26049 : Unscoped REF column has non-existent table name.
  • ora-07860 : osnsoi: error setting up interrupt handler
  • ora-02066 : missing or invalid DISPATCHERS text
  • ora-27195 : proxy copy not supported
  • ora-24145 : evaluation context string.string already exists
  • ora-33072 : (XSAGDNGL35) In AGGMAP workspace object, the hierarchy dimension QDR over dimension workspace object must be specified for every relation dimensioned by that hierarchy dimension.
  • ora-10658 : Lob column to be shrunk is marked unused
  • ora-14012 : resulting partition name conflicts with that of an existing partition
  • ora-22893 : constraint can be specified only for REF columns
  • ora-07746 : slemrd: invalid error message file handle
  • ora-00206 : error in writing (block string, # blocks string) of control file
  • ora-36883 : (XSSRF02) The first parameter of an AW single row function cannot be NULL.
  • ora-32609 : missing REFERENCE keyword in MODEL clause
  • ora-14106 : LOGGING/NOLOGGING may not be specified for a clustered table
  • ora-25234 : NEXT_TRANSACTION navigation option invalid for queue table string.string
  • ora-06006 : NETASY: dialogue execute failure
  • ora-01858 : a non-numeric character was found where a numeric was expected
  • ora-38494 : column in the table alias and an attribute have matching names
  • ora-28102 : policy does not exist
  • ora-14120 : incompletely specified partition bound for a DATE column
  • ora-30444 : rewrite terminated by the sql analyzer
  • ora-16402 : ONDEMAND archival requires FAL_CLIENT and FAL_SERVER support
  • ora-02144 : no option specified for ALTER 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.