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

DEACTIVATION WITH LARGE BUFFERPOOL MEMORY TAKES EXCESSIVELY LONG ON LARGE
WINDOWS SYSTEM

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Deactivating a database with large bufferpool memory on Windows 
takes excessively long.  For example, it takes 10+ minutes to 
deactivate a database with 100GB of bufferpool memory. 
 
A workaround is to increase the units of memory allocation used 
for bufferpools from the default 128K to the maximum of 256MB: 
 
  db2set DB2_ALLOCATION_SIZE=256M 
 
This requires stopping/starting the instance to take effect. 
 
This setting is an appropriate workaround for the size of 
systems vulnerable to this problem.  While DB2_ALLOCATION_SIZE 
is a deprecated registry variable, it is still effective in DB2 
Version 9.7.  Note that bufferpools will only use the amount of 
memory that is required, i.e. the full 256MB will not be used 
when only a portion of that amount is needed. 
 
The same symptom could be seen for any activity (eg. last 
connection out) which is driving database deactivation.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Large DB2/Windows systems                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 6                        * 
****************************************************************
Local Fix:
db2set DB2_ALLOCATION_SIZE=256M 
( requires stopping/starting the instance )
available fix packs:
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 8 for Linux, UNIX, and Windows
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

Solution
Problem first fixed in DB2 Version 9.7 Fix Pack 6
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC84260 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
20.10.2011
21.06.2012
21.06.2012
Problem solved at the following versions (IBM BugInfos)
9.7.FP6
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.6 FixList
This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.