DB2 - Problembeschreibung
Problem IC62588 | Status: Geschlossen |
SLOW HADR STANDBY DEACTIVATION CAN CAUSE HADR PRIMARY TO PAUSE | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
In an HADR environment, the deactivation of standby involves flushing all dirty pages to disk. When the bufferpool is huge, it may take some time to flush all the dirty pages, and if HADR is in SYNC mode, the primary side will not be able to ship logs to the standby during this period. The primary will appear to hang until the standby is completely deactivated. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * In an HADR environment, the deactivation of standby involves * * * * flushing all dirty pages to disk. When the bufferpool is * * huge, * * it may take some time to flush all the dirty pages, and if * * HADR * * is in SYNC mode, the primary side will not be able to ship * * logs * * to the standby during this period. The primary will appear * * to * * hang until the standby is completely deactivated. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 9.7 FP1 * **************************************************************** | |
Local-Fix: | |
Tune softmax, chngpgs_thresh and/or use db2pdcfg -flushbp to reduce the number of dirty pages in the standby bufferpool before deactivating the database on the standby. | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows | |
Lösung | |
Problem was first fixed in Version 9.7 Fix Pack 1 | |
Workaround | |
Tune softmax, chngpgs_thresh and/or use db2pdcfg -flushbp to reduce the number of dirty pages in the standby bufferpool before deactivating the database on the standby. | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 19.08.2009 23.02.2010 23.02.2010 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7.FP1 | |
Problem behoben lt. FixList in der Version | |
9.7.0.1 |