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

32-bit IBM DB2 ODBC Driver not enabled for connection pooling, on 64-bit
Windows install

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
On Windows 64-bit installations of DB2 servers, IBM Data Server 
Clients, and IBM Data Server Driver installations, the 32-bit 
IBM DB2 ODBC Driver has connection pooling disabled by default, 
while the 64-bit driver (and the 32-bit driver, on Windows 
32-bit installations) have connection pooling enabled by 
default. 
 
When the DB2 (and IBM Data Server Client or Driver) install 
registers the ODBC/CLI driver with Microsoft ODBC, it creates a 
registry entry for "CPtimeout"(connection pool timeout) in the 
ODBCINST.INI stanza with default value of 60 seconds. This 
enables connection pooling by default for that driver. 
 
This works fine for the Windows 32-bit installer. It also works 
fine for the 64-bit driver when using the 64-bit installer. 
However, this registry entry is not created for the 32-bit 
driver. Hence connection pooling is disabled by default for 
32-bit applications utilizing the IBM DB2 ODBC Driver. 
 
Registry entry for 64-bit driver (64 bit install): 
HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\IBM DB2 ODBC 
DRIVER - DB2COPY1\CPTimeout 
 
The same entry for the 32-bit driver (64-bit install) is missing 
the entry for CPTimeout in registry: 
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBCINST.INI\IBM 
DB2 ODBC DRIVER - DB2COPY1 
 
If connection pooling is not enabled, this will decrease 
performance, due to additional connects and disconnects.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* 32-bit DB2 ODBC driver on Windows 64-bit environments        * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v9.7 Fixpack 9                                * 
****************************************************************
Local Fix:
To enable connection pooling for the 32-bit ODBC driver, launch 
the Windows 32-bit ODBC Data Source Administrator. on Windows 
64-bit platforms: 
 
c:\windows\syswow64\odbcad32.exe 
 
In the 'Connection Pooling' tab, locate and double click the 
driver name corresponding to the current DB2 / IBM Data Server 
Driver copy, e.g. for the default copy of the IBM Data Server 
Driver package: 
 
IBM DB2 ODBC DRIVER - IBMDBCL1 
 
This will bring up the 'Set Connection Pooling Attributes' 
dialog. Select 'Pool connections to this driver' and  a timeout 
value of 64 seconds, and then select 'OK'.
available fix packs:
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
First fixed in DB2 v9.7 Fixpack 9
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC95525 IC95658 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
01.03.2013
17.12.2013
17.12.2013
Problem solved at the following versions (IBM BugInfos)
9.7.FP9
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.9 FixList
9.7.0.9 FixList
This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.