DB2 - Problem description
Problem IC70305 | Status: Closed |
WHEN ALTERING BUFFERPOOL TO FIXED SIZE FROM AUTOMATIC IS DEFERRED, STMM WILL CONTINUE TO TUNE IT. | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
A user-initiated alter of an automatic bufferpool will be deferred until the next database activation if there is not enough memory to satisfy this request or "deferred" option is specified explicitly. Such a deferred request will be forgotten if STMM decides to alter the same bufferpool before the next database activation. The problem is that STMM continues to tune this bufferpool, and changes made by STMM will override any previously deferred (hence saved) alter requests. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error description field for more information. * **************************************************************** * RECOMMENDATION: * * Upgrade to Version 9.7 FixPack 4. * **************************************************************** | |
Local Fix: | |
1) Try to issue an alter request that will likely be not deferred, for example altering to the same size will not get deferred, but the bufferpool will no longer be tuned by STMM. 2) If the request does gets deferred while the bufferpool is still automatic, deactivate and reactivate the database before STMM gets a chance to tune the bufferpool. | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows | |
Solution | |
Problem was first fixed in DB2 UDB Version 9.7 FixPack 4. | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC70520 IC70521 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 30.07.2010 12.05.2011 12.05.2011 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP4 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.4 |