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

A MULTITHREADED CLIENT RUNNING WITH WLB ENABLED AND CONNECTED TO A
PURESCALE MEMEBER MAY TRAP.

product:
DB2 CONNECT / DB2CONNCT / A10 - DB2
Problem description:
A multithreaded client running with WLB enabled and connected to 
a pureScale cluster may trap if two threads are 
accessing/modifying the server list cache at the same 
time(cfgcache/srvlst.xml).  This is timing dependent - It can 
hit this as early as two minutes into a run and as late as 40 
minutes.  The likelihood of hitting this is increased when there 
are concurrent connection attempts in progress.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* CLI users connecting to pureScale member.                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.1.1                                * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
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
CLI users connecting purescale member with concurrent 
connections will not trap.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
14.06.2012
02.11.2012
02.11.2012
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.1 FixList
10.5.0.1 FixList