DB2 FOR LUW / DB2FORLUW / A50 - DB2

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 <partitionnum> -db <dbname> -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 << This is the leaking 
block 
 
An example scenario for the leak is: 
 
As DB2 instance user db2inst1: 
 
Step 1) 
 
db2 connect to sample; 
db2 "create table s like staff" 
db2 "insert into s select * from staff" 
db2 "grant select on table s to user dpf1" 
db2 terminate 
 
Step 2) 
 
export DB2NODE=2 
db2 terminate 
db2 connect to sample user dpf1 using xxxxxx 
db2 "select * from db2inst1.s" 
db2 terminate; 
 
 
The leaking allocation ( shown above ) will keep growing with 
every invocation of Step 2). 
 
This problem appears in DB2 v10.1, 10.5 and 11.1. It does not 
appear in DB2 v9.7.

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Db2 10.5 Fix Pack 9 or higher                     * 
****************************************************************

First fixed in Db2 10.5 Fix Pack 9

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

12.09.2016
29.09.2017
29.09.2017

9.0.