home clear 64x64
en blue 200x116 de orange 200x116 info letter User
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 IC92927 Status: Closed

UNNECESSARY INCREASE IN DBMS SET SIZE IN VERSION 10 FOR WORKLOAD DISPATCHER

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
The DBMS memory set size is significantly higher in DB2 version 
10.  Some of this is required for functional and problem 
determination enhancements.  A large amount is due to an 
unnecessarily high estimate for the workload dispatcher.  This 
amount will be reduced to what is strictly necessary (the DBMS 
set will grow automatically if required).  For example, on a 
machine with 8 cpus/12GB RAM, the DBMS set is sized at 
approximately 250MB (and increase from 50MB on version 9.7), and 
this will be reduced to approximately 150MB.  On larger 
machines, the difference may be higher. 
 
Note the excess memory is only backed by real memory on Solaris, 
and can be ignored on other platforms.  While the initial sizing 
counts towards instance memory usage, the excess unused memory 
will be automatically reduced if needed for other purposes 
(database memory requirements, STMM tuning, etc.)
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* all systems are affected                                     * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* The symptoms caused by this problem are immaterial and can   * 
* be ignored.  An exception is DB2 systems running on Solaris  * 
* with a large number of small instances - in this case it is  * 
* recommended to upgrade to DB2 Version 10.1 Fix pack 3        * 
****************************************************************
Local Fix:
available fix packs:
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

Solution
Problem first fixed in DB2 Version 10.1 Fix pack 3
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC94475 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
07.06.2013
04.12.2013
04.12.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.3 FixList
10.1.0.3 FixList