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

DEADLOCK CAN BE HAPPEN BETWEEN THE IBM INFORMIX CSDK ODBC DRIVER AND THE
IBM DB2 DATASERVER DRIVER WHEN USED IN THE SAME APP

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
Deadlock can occur on Windows because both drivers make a system 
call to getenv() which locks a critical section. 
If the timing is perfect this can cause a deadlock. 
 
Possible workaround to minimize the impact is to modify the 
CriticalSectionTimeout: 
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session 
Manager\CriticalSectionTimeout
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Windows Only                                                 * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Problem was first fixed in Version 10.1 Fix Pack 3           * 
****************************************************************
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       :
03.04.2013
01.10.2013
01.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