DB2 FOR LUW / DB2FORLUW / 970 - DB2

DPF systems with lower numbers of frequently accessed database 
objects may experience growing memory usage over time due to 
this APAR. 
The growth in memory usage occurs in the application heap for 
the "db2lused" system application tracking the last access time 
for database objects. 
This functionality was introduced in DB2 version 9.7 and does 
not apply to earlier releases. 
The leak is more likely to be seen on test/development systems 
with periods of inactivity, or, for example, dedicated 
coordinator partitions that do not access database objects 
directly. 
The memory leak occurs in the case where there is no information 
to send back from a given partition to the db2lused system 
application for a given interval. 
 
While the main symptom is growing system memory usage over time, 
systems with fixed limits on application heap (APPLHEAPSZ), 
application memory (APPL_MEMORY), or instance memory 
(INSTANCE_MEMORY) may experience out of memory errors due to the 
leak. 
 
The memory leak can be observed by monitoring the application 
heap for the db2lused system application through global 
application snapshots or SQL: 
select b.appl_name, b.dbpartitionnum, a.pool_cur_size, 
a.pool_watermark 
   from sysibmadm.snapagent_memory_pool a, 
sysibmadm.applications b 
   where b.appl_name = 'db2lused' and 
              a.agent_id = b.agent_id and 
              a.dbpartitionnum = b.dbpartitionnum and 
              a.pool_id = 'APPLICATION' 
 
If individual application heap usage continues to grow above 
50MB and not released, it is likely due to this APAR. 
Each leaked allocation is 163840 bytes, and at most 4 per hour 
per partition. 
 
On a given partition, 
db2pd -db <db> -memb appctl 
will show a growing allocated memory blocks similar to the 
following (match on the last 2 columns) : 
0x0700000030177FC8 0x0700000030177FE0 1          apph 
1399  163840       1 815   3872119310

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* You may experience "SQL0101N  The statement is too long      * 
* ortoo complex" or other errors due to memory leak            * 
* inapplication heap for system application db2lused.          * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Recommended to upgrade to DB2 LUW v9.7 FP3.                  * 
****************************************************************

The db2lused system application can be disabled dynamically as 
follows: 
DB2_SYSTEM_MONITOR_SETTINGS=LAST_USE_INTERVAL:0 
This will prevent the collection of the last used time statistic 
for database objects.

DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
 

Problem First Fixed in DB2 Version 9.7 fix pack 3

not known / see Local fix

forerunner  : APAR is sysrouted TO one or more of the following: IC69789 
follow-up : 

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

23.06.2010
27.09.2010
27.09.2010

9.7.FP3