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

THE AUTOMATIC SETTING FOR INSTANCE_MEMORY WILL NO LONGER ENFORCE A LIMIT
UNLESS A LICENSE MEMORY LIMIT IS IN EFFECT

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
On Version 9.5, INSTANCE_MEMORY = AUTOMATIC enforces a limit on 
instance memory usage.  This limit is between 75-95% of RAM. 
The enforcement of this limit (under the AUTOMATIC setting) is 
being removed to avoid unnecessary out of memory errors - errors 
which may occur even when a system is not in danger of being 
overcommited - and associated tuning efforts. 
 
An instance memory limit is still enforced when INSTANCE_MEMORY 
is set to a specific value, or when a license memory limit 
exists. 
 
In addition, STMM will no longer take free Instance Memory into 
account when INSTANCE_MEMORY is set to AUTOMATIC and a license 
memory limit is not in effect.  STMM will continue to tune 
database memory based on available system memory (RAM).  The 
prior behaivour is that STMM would ensure both sufficient free 
Instance Memory and sufficient free system memory.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users are affected                                       * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Fix Pack 1 to avoid enforced AUTOMATIC Instance   * 
* Memory Limits.                                               * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Problem first fixed in DB2 Version 9.7 Fix Pack 1
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
30.06.2009
17.02.2010
29.06.2010
Problem solved at the following versions (IBM BugInfos)
9.7.FP1
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.1 FixList