DB2 FOR LUW / DB2FORLUW / A10 - DB2

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.

**************************************************************** 
* USERS AFFECTED:                                              * 
* Large Windows systems                                        * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 1                       * 
****************************************************************

db2set DB2_ALLOCATION_SIZE=256M 
( requires stopping/starting the instance )

DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
 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
 

First fixed in DB2 Version 10.1 Fix Pack 1

See Local Fix

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

13.06.2012
02.11.2012
02.11.2012