home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC90006 Status: Geschlossen

SMALL PRIVATE MEMORY LEAK ON THE DB2 SERVER EVERY TIME AN OPTIMIZATION
PROFILE IS LOADED

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
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
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* systems using optimizer profiles or with DB2_WORKLOAD=SAP    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 9                        * 
****************************************************************
Local-Fix:
Increase the catalog cache setting (catalogcache_sz) and/or the 
package cache setting (pckcachesz)
verfügbare FixPacks:
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

Lösung
Problem first fixed in DB2 Version 9.7 Fix Pack 9
Workaround
See Local Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC90008 IC90009 IC95438 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
04.02.2013
18.12.2013
18.12.2013
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP9
Problem behoben lt. FixList in der Version
9.7.0.9 FixList
9.7.0.9 FixList