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 IC94474 Status: Closed

EXCESSIVE MEMORY ALLOCATION FOR DBMS MEMORY SET ON SOLARIS / SPARC
ARCHITECTURE

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
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.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 LUW on Solaris                                           * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5 Fix Pack 3                       * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Solution
Problem first fixed in DB2 Version 10.5 Fix Pack 3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
30.07.2013
28.02.2014
28.02.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.3 FixList
10.5.0.3 FixList