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 IT17021 Status: Closed

(AMD) MEMORY LEAK IN CATALOG CACHE ON MULTI-NODE DB2 INSTANCES

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
1.  Problem description

Whenever a user connects to a non-catalog node and accesses a
table on which explicit permission has been given to the user,
there is a 32 byte leak in the catalog cache.

Symptoms:

If the catalog cache size usage keeps growing and if multiple
db2pd -dbp  -db  -memblocks 8 sort are
collected a growth in the following block will be observed:

All memory consumers in Database memory set:
PoolAddr           PoolID     PoolName   SecondID
TotalSize(Bytes)     %Bytes TotalCount %Count LOC   File
0x0700000040032210 8          catcacheh  0         579242080
69.57  657082     7.53   2440  1089102221
0x0700000040032210 8          catcacheh  0          252801165
30.36  48693      0.56   2107  896367698
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* All                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to V11.1 Mod2 Fixpack 2 Ifix0001                     *
****************************************************************
Local Fix:
Solution
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : IT17018 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
12.09.2016
11.10.2017
11.10.2017
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)