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

ABEND POSSIBLE IN CLI_SQLDISCONNECT WITH > 512 DATABASE HANDLES
ALLOCATED IN MULTITHREAD ENVIRONMENT

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
When a multithreaded CLI application has over 512 database 
handles for one environment handle, then DB2 CLI code 
reallocates an internal structure. 
There is a very small timing window that when a SQLDisconnect ( 
which calls CLI_sqlDisconnect ) is invoked as this threshold is 
reached, stale memory can be referenced, leading to a crash of 
the application. 
 
CLI_sqlDisconnect will be the crashing function.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* The customers can see the issue, only in multi threaded      * 
* environment when they are creating connection handled        * 
* greater than 512.                                            * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to product version v.97.fp9                          * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
26.09.2013
26.10.2013
26.10.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.3 FixList
10.1.0.3 FixList