DB2 - Problem description
Problem IC64767 | Status: Closed |
ALTER BUFFERPOOL REDUCE OR STMM MAY HANG IF SET WRITE SUSPEND HAD BEEN ISSUED | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
SET WRITE SUSPEND has the ability to interrupt page cleaners, but once the page cleaners had been interrupted, they did not perform the correct sequence of disengagement, and may cause ALTER BUFFERPOOL REDUCE or STMM to indefinitely wait on some page latches. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All users. * **************************************************************** * PROBLEM DESCRIPTION: * * For users of STMM or SET WRITE SUSPEND, db2stop force may * * hang * * For other users, they may experience a slow or inefficient * * page cleaning on a busy system. This could lead to log * * space being held up by dirty pages, or a higher than usual * * dirty steals occurring in the bufferpool, which could affect * * performance. * **************************************************************** * RECOMMENDATION: * * Upgrade to the aforementioned fixpaks. * **************************************************************** | |
Local Fix: | |
Recycle the instance | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows | |
Solution | |
The problem has been fixed in v91 fp 8, v95 fp5 and v97 fp1 As part of the change, the set write suspend command may take longer to pause the page cleaners than v91 fp7/v95 fp4 when the problematic APAR went in. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 23.11.2009 10.12.2009 10.12.2009 |
Problem solved at the following versions (IBM BugInfos) | |
9.1.FP7/v95, 9.1.FP8, 9.5.FP5, 9.7.FP1 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.1 |