home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT09568 Status: Closed

QUERY MAY RECEIVE A SQL0901N WITH REASON "FOUND ZERO CLOB.RESET"

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
Problem definition: 
Query in BLU environment may fail with a SQL0901N with Reason 
"Found zero CLOB.reset". The failure will be in 
sqlng_build_IU_CLOB_obj function. 
 
Stack may look similar to the following: 
sqlnn_cmpl 
sqlng_main 
sqlng_main 
sqlng_build_thread 
sqlngProcessLolepop 
sqlng_process_return_op 
sqlng_process_remote_ops 
sqlng_process_riud_op 
sqlng_process_remote_ops 
sqlng_process_remote_ops 
sqlng_process_ship_op 
sqlngProcessLolepop 
sqlng_process_TQ_op 
sqlng_process_SMPTQ_op 
sqlng_build_thread 
sqlng_build_SMP_TQB_op 
sqlng_build_IU_CLOB_obj
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 10.5 Fix Pack 7                               * 
****************************************************************
Local Fix:
SET CURRENT DEGREE 1 to remove intra partition parallelism
Solution
First Fixed in DB2 10.5 Fix Pack 7
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
19.06.2015
09.05.2017
09.05.2017
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.7 FixList