DB2 FOR LUW / DB2FORLUW / A10 - DB2

A small amount of private memory is leaked when an optimization 
profile is first accessed.  SAP systems are vulnerable through 
the use of the DB2WORKLOAD=SAP registry setting. 
 
In most cases, the memory leak is minimal, as optimizer profile 
information is cached in the catalog cache.  The leak only 
occurs when the profile is loaded into the cache, i.e. on the 
first access after database activation, and on subsequent 
accesses only if the profile has been evicted from the cache 
(due to limited space/configuration). 
 
On SAP systems, the leak is only likely to be significant when 
the package cache is constrained, causing frequent statement 
recompilations. 
 
The memory leak is outside of DB2's memory manager, so it cannot 
be seen by DB2 diagnostic tools.  It can only be monitored as 
part of overall private memory usage by the db2sysc/db2syscs.exe 
process.  The best way to identify the problem is: 
- confirm vulnerability 
- monitor the catalog cache and package cache hit ratio 
- assess the catalog cache/package cache configuration 
- confirm that private memory usage for the db2sysc process is 
growing consistently over time

**************************************************************** 
* USERS AFFECTED:                                              * 
* Systems using optimizer profiles or with the registry        * 
* setting DB2WORKLOAD=SAP                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 3                       * 
****************************************************************

Increase the catalog cache setting (catalogcache_sz) and/or the 
package cache setting (pckcachesz)

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
 

Problem first fixed in DB2 Version 10.1 Fix Pack 3

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

04.02.2013
04.12.2013
04.12.2013