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

SMALL MEMORY LEAK IN DB2 CLIENT/DRIVER IF CLIENT AFFNITY IS ENABLED

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
On the affinity feature, even for the very first connection, 
DB2 client/driver uses affnity list including a member list in 
which members are defined in alternate server list. 
 
  For example, if db2dsdriver.cfg includes the following 
elements about affinity feature, the small memory leaks in db2 
Client/Driver.  And this memory leak occurs even if 
clientaffinitydefined element is not included or even on the 
cached affinity member list from the earlier connection. 
 
  A sample of db2dsdriver.cfg 
 
       <acr> 
          .... 
          <alternateserverlist> 
             <server name="member1" hostname="localhost" 
port="31126"/> 
             <server name="member2" hostname="localhost" 
port="31126"/> 
          </alternateserverlist> 
          <affinitylist> 
             <list name="list1" serverorder="member1,member2"/> 
             <list name="list2" serverorder="member2,member1"/> 
          </affinitylist> 
          <clientaffinitydefined> 
            <client name="client1" hostname="localhost" 
listname="list1"/> 
          </clientaffinitydefined> 
       </acr>
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* affinity feature user                                        * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V10.5 FP9 or higher                           * 
****************************************************************
Local Fix:
Solution
First fixed in DB2 V10.5 FP9
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
01.06.2016
27.09.2017
27.09.2017
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)