DB2 - Problem description
Problem IC77662 | Status: Closed |
TRUSTED STORED PROCEDURES WITHIN THE CONNECTION CONTEXT NOT FULLY RELEASED MEMORY DURING SUBSEQUENT DISCONNECT | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
When using trusted stored procedures, some of the memory is not freed even though the context of the query is completed. So you may find private memory usage increases on the db2sysc process. The current problem is, the memory is fully released only when the library is unloaded. This APAR will fix the problem. On busy systems, the application library may not be unloaded often, therefore cause a memory leak effectively. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * When using trusted stored procedures, some of the memory is * * not * * freed even though the context of the query is completed. * * * * So you may find private memory usage increases on the * * db2sysc * * process. * * * * The current problem is, the memory is fully released only * * when * * the library is unloaded. This APAR will fix the problem. * * * * * * * * * * * * On busy systems, the application library may not be unloaded * * * * often, therefore cause a memory leak effectively. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 version V9.7Fixpack 5 * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows | |
Solution | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 22.07.2011 07.12.2011 07.12.2011 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FIXPACK | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.5 |