home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC84518 Status: Closed

MEMORY LEAK IN CATALOG CACHE WHEN AUTOMATIC STATISTICS IS ENABLED.

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
This memory leak only occurs with specific memory allocations 
made by automatic statistics collection (which is enabled via 
AUTO_RUNSTATS db cfg parameter). 
 
To detect this memory leak, check for a steady catcache growth 
from "db2pd -d <db> -memblocks sort 8" data from allocations by 
file 1191117521 from line# 320-323. For example, 
 
All memory consumers in Database memory set: 
PoolID     PoolName   TotalSize(Bytes)     %Bytes TotalCount 
%Count LOC   File 
8          catcacheh  689981592            84.94  58066 5.58 
320   1191117521 
 
Several days later, it grows up: 
PoolID     PoolName   TotalSize(Bytes)     %Bytes TotalCount 
%Count LOC   File 
8          catcacheh  759833640            91.59  63980 7.50 
320   1191117521 
 
This problem was first introduced in DB2 Version 9.7 Fixpack 1.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to fixpack 1 or use the local fix.                    * 
****************************************************************
Local Fix:
Disable AUTO_RUNSTATS, which is an online configurable db cfg 
parameter.  When disabled, you need to consider performing 
statistics collection manually as needed, until automatic 
statistics collection can be re-enabled.
available fix packs:
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
This problem is first fixed in db2 version 10.1 fixpack 1.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
14.06.2012
01.11.2012
01.11.2012
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.1 FixList
10.5.0.1 FixList