DB2 - Problem description
Problem IT10197 | Status: Closed |
SMALL MEMORY LEAK IN DB2 CLIENT/DRIVER IF THE ALTERNATE SERVER LIST IS ENABLED IN A DB2DSDRIVER.CFG FILE | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problem description: | |
Small amount of memory leaks in the db2 client/driver application on each tcpip connection to DB with a db2dsdriver.cfg file. For example, if db2dsdriver.cfg includes the following elements about alternate server feature, the small memory leaks in db2 Client/Driver. 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> Those leaked memory allocations can be confirmed by the system memory debug feature like MALLOCDEBUG on AIX. In the case of AIX with "export MALLOCDEBUG=log:extended,stack_depth:12", the following stacks will be listed on the leaked memory locations. malloc_common_debugging _Fancy_malloc __nw getIterator getEffectiveAlternateSrvList sqleUCinitAppData sqleUCappConnect sqlakConnect sqlacall DbConnect main | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * DB2 CLIENT/DRIVER user * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to db2 Version 10.5 FixPack 7 or higher * **************************************************************** | |
Local Fix: | |
Solution | |
Problem was first fixed in Version 10.5 FixPack 7 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 20.07.2015 20.01.2016 20.01.2016 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.5.0.7 |