DB2 - Problem description
Problem IC63993 | Status: Closed |
Memory is leaked when an EDU for unfenced store procedure terminates | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
Small memory buffer, related to the thread control block , is leaked when a db2 agent terminates. The memory leak happens only for the agents, executing unfenced store procedures. The leaked memory area can be reused by DB2 if OS creates new threads with reused thread ID. The leaked memory would be released when libdb2e.so library is unloaded from the DB2 engine ( db2sysc process ) | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * all platforms * **************************************************************** * PROBLEM DESCRIPTION: * * The memory is leaked when db2 agent, executing unfenced * * store procedure , terminates. A DB2 agent terminates when * * number of agents exceeds the number of max pool agents * * (NUM_POOLAGENTS) . The memory is released when the last * * application, executing an unfenced store procedure , * * disconnects and libdb2e.so is unloaded. * **************************************************************** * RECOMMENDATION: * * Upgrade to V97FP1 * **************************************************************** | |
Local Fix: | |
Disconnect all applications , running unfenced stored procedures | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows | |
Solution | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 22.10.2009 09.03.2010 09.03.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP1 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.1 |