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

SQL_ATTR_FET_BUF_SIZE VALUE SHOULD BE ALLOWED AS ( N TIMES 32K )AND NOT ( N
TIMES 32K ) MINUS 1

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Currently if SQL_ATTR_FET_BUF_SIZE value is set as ( N times 32K 
), warning is generated and value is rounded of to next 32K 
boundary. This is incorrect and no round-off should happens for 
(N times 32K) values.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to db2_v97fp7 or later.                              * 
****************************************************************
Local Fix:
NA
available fix packs:
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Fixed in db2_v97fp6. 
SQL_ATTR_FET_BUF_SIZE VALUE WILL BE ALLOWED AS ( N TIMES 32K ).
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC85233 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
06.07.2012
24.10.2012
24.10.2012
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.7 FixList