DB2 - Problem description
Problem IC66093 | Status: Closed |
MEMORY LEAK OF 36548 OR 514 BYTES WHEN EXECUTING LOAD COMMAND | |
product: | |
DB2 FOR LUW / DB2FORLUW / 980 - DB2 | |
Problem description: | |
When executing a load command, there is a memory leak of 514 bytes in the db2sysc process. If the load command is executed via the sysproc.admin_cmd() procedure, then there is an additional leak of 36034 bytes leaked in the db2fmp process that executed the sysproc.admin_cmd() procedure. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All users running load * **************************************************************** * PROBLEM DESCRIPTION: * * When executing a load command, there is a memory leak of * * 514 * * bytes in the db2sysc process. If the load command is * * executed * * via the sysproc.admin_cmd() procedure, then there is an * * * * additional leak of 36034 bytes leaked in the db2fmp process * * that * * executed the sysproc.admin_cmd() procedure. * **************************************************************** * RECOMMENDATION: * * Problem was first fixed in Version 9.8 Fix Pack 3 * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 9.8 Fix Pack 3 for Linux, UNIX, and Windows | |
Solution | |
When executing a load command, there is a memory leak of 514 bytes in the db2sysc process. If the load command is executed via the sysproc.admin_cmd() procedure, then there is an additional leak of 36034 bytes leaked in the db2fmp process thatexecuted the sysproc.admin_cmd() procedure. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 05.02.2010 27.12.2010 22.04.2011 |
Problem solved at the following versions (IBM BugInfos) | |
9.8.FP3 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.8.0.3 |