DB2 - Problem description
Problem IC67352 | Status: Closed |
MEMORY LEAK IN DB2 WHEN CALLING UNFENCED CLI ROUTINES | |
product: | |
DB2 FOR LUW / DB2FORLUW / 980 - DB2 | |
Problem description: | |
A small amount of memory is leaked in the DB2 server process on each call to a trusted/unfenced CLI routine. This leak can build over time and may cause memory overcommitment on a system, potentially resulting in performance degradation and eventually memory exhaustion. . For example, the problem was found in this case when running a large number of xml decomposition which invokes this trusted/unfenced CLI routine causing the memory to increase on the system and eventually memory exhaustion. | |
Problem Summary: | |
A small amount of memory is leaked in the DB2 server process on each call to a trusted/unfenced CLI routine. This leak can build over time and may cause memory overcommitment on a system, potentially resulting in performance degradation and eventually memory exhaustion. . For example, the problem was found in this case when running a large number of xml decomposition which invokes this trusted/unfenced CLI routine causing the memory to increase on the system and eventually memory exhaustion. | |
Local Fix: | |
None really. Until all connections terminate, this memory will not be released. | |
available fix packs: | |
DB2 Version 9.8 Fix Pack 3 for Linux, UNIX, and Windows | |
Solution | |
apar ic67352 fixed >= v98 fpk3 | |
Workaround | |
None really. Until all connections terminate, this memory will not be released. | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 21.03.2010 20.12.2010 20.12.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.8.FPk3 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.8.0.3 |