ORA-22922: nonexistent LOB value" error when selecting a clob value in an Index-Organized Table with a date column in the primary key

« Go Back


Question/Problem Description
An "ORA-22922: nonexistent LOB value" error is received when selecting a clob value in an Index-Organized Table with a date column in the primary key.
Steps to Reproduce
Clarifying Information
Steps to Reproduce:
  • Create the following table:
    create table class1H001 (bbr_object_name varchar2(230) NOT NULL, bbr_value_date date NOT NULL,faststringtype3 clob NULL, constraint class1P001 primary key(bbr_value_date, bbr_object_name))organization index PCTTHRESHOLD 10 overflow
  • Populate table:
    insert into class1H001 values ('object1', to_date('2008-07-28 10:30:00','YYYY-MM-DD HH24:MI:SS'), 'fast')
  • Run the next statement:
    select* from class1H001
Error Message[DataDirect][ODBC Oracle Wire Protocol driver][Oracle]ORA-22922: nonexistent LOB value
Defect/Enhancement NumberDD00040941
Reproduced the issue with build 
Defect DD00040941 has been fixed in build 

Click here for instructions on how to download and install the patch.
Last Modified Date9/13/2015 6:39 PM

The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.

Was this article helpful?


Your feedback is appreciated.

Please tell us how we can make this article more useful.

Characters Remaining: 255