DB2 FOR LUW / DB2FORLUW / A10 - DB2

In DB2 Version 10.1, when using the Solaris operating system on 
the Sparc architecture, the base amount of memory used per DB2 
instance may be excessive.  The DBMS memory set, allocated after 
issuing db2start, is larger than necessary.  Users migrating 
from previous releases may notice a significant increase in 
system memory consumption, or possibly a failure - SQL1220 - to 
start the instance if using a small fixed INSTANCE_MEMORY 
setting. 
 
The problem is caused by the memory sizing calculations used to 
support the new Workload Dispatcher feature, which requires 
knowledge of the CPU configuration.  On Solaris Sparc, DB2 is 
incorrectly calculating the threading degree, leading to a 
significant memory over-allocation. 
 
Instead of a the DBMS memory set being in a low range (typically 
80-200MB though this may vary), the size may be in the order of 
several GB, as in the following example: 
 
db2pd -memsets 
 
Memory Sets: 
Name         Address            Id          Size(Kb) 
DBMS         0x0000000200000000 939524312   4754112 
... 
 
See the related APAR IC92927, which also contributes to 
over-allocation of the DBMS memory set, but is not specific to 
the Solaris / Sparc platform.

**************************************************************** 
* USERS AFFECTED:                                              * 
* Systems running on the Solaris platform                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 3                       * 
****************************************************************

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

Vorgänger  : APAR is sysrouted TO one or more of the following: IC94474 
Nachfolger : 

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

22.07.2013
09.12.2013
09.12.2013