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 IT17502 Status: Closed

-30020 WITH MULTI ROW FETCH AND SPLIT BUFFER THAT CONTAINS LOB DATA

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
An application can receive an SQL30020N error (or CLI0113E, and 
possibly other CLI conversion failures) when performing a 
multi-row fetch that contains a LOB column (eg, XML) and results 
in a split buffer (ie, not all the rows can fit in one cursor 
block). 
 
Problem was reproduced, and identified to be a result of APAR# 
IC98943 which was "fixed" in DB2 v10.5 FP4.   This fix was not 
required for v10.5 and needs to be removed, which would then fix 
this issue as well.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Db2 10.5 Fix Pack 9 or higher                     * 
****************************************************************
Local Fix:
The FET_BUFF_SIZE db2cli.ini keyword can be used to avoid a 
split buffer scenario.  The parameter can change the size of a 
cursor block from the default of 64K to something much larger 
(eg, 256K).
Solution
First fixed in Db2 10.5 Fix Pack 9
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
14.10.2016
29.09.2017
29.09.2017
Problem solved at the following versions (IBM BugInfos)
9.0.
Problem solved according to the fixlist(s) of the following version(s)