DB2 - Problembeschreibung
Problem IC66970 | Status: Geschlossen |
DB2 PAGE CLEANER HANGS MAY LEAD TO DATABASE HANGING | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
Page cleaners spinning on V97FP1 The stack of the page cleaners will show that they keep on looping within the sqlbClnrGatherForFlushUpToLSN function Stack: <StackTrace> -------Frame------ ------Function + Offset------ 0x090000001A7F3214 sqloSpinLockReleaseConflict + 0xB8 0x090000001A7F3360 sqloSpinLockReleaseConflict@glue74 + 0x78 0x090000001A969740 sqlbClnrGatherForFlushUpToLSN__FP12SQLB_CLNR_CB + 0x1D0 0x090000001A557024 sqlbClnrGatherPages__FP12SQLB_CLNR_CB + 0x0 0x090000001A5C2B60 sqlbClnrEntryPoint__FP12sqbPgClnrEdu + 0x714 0x090000001A7BEED4 RunEDU__12sqbPgClnrEduFv + 0x34 0x090000001A7BF184 EDUDriver__9sqzEDUObjFv + 0xDC 0x090000001A7B3AE0 sqloEDUEntry + 0x264 </StackTrace> A trace of the page cleaners will show that the cleaners keep on entering and exiting this function with rc = TRIGGER_SERVICED. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * An internal trigger was not turned off properly for the page * * cleaners, causing them to spin on finding work, when there * * isn't any. * * * * * * The stack of the page cleaners will show that they keep on * * * * looping within the sqlbClnrGatherForFlushUpToLSN function * * * * * * * * Stack: * * * * <StackTrace> * * * * -------Frame------ ------Function + Offset------ * * * * 0x090000001A7F3214 sqloSpinLockReleaseConflict + 0xB8 * * * * 0x090000001A7F3360 sqloSpinLockReleaseConflict@glue74 + 0x78 * * * * 0x090000001A969740 * * * * sqlbClnrGatherForFlushUpToLSN__FP12SQLB_CLNR_CB + 0x1D0 * * * * 0x090000001A557024 sqlbClnrGatherPages__FP12SQLB_CLNR_CB + * * 0x0 * * 0x090000001A5C2B60 sqlbClnrEntryPoint__FP12sqbPgClnrEdu + * * 0x714 * * 0x090000001A7BEED4 RunEDU__12sqbPgClnrEduFv + 0x34 * * * * 0x090000001A7BF184 EDUDriver__9sqzEDUObjFv + 0xDC * * * * 0x090000001A7B3AE0 sqloEDUEntry + 0x264 * * * * </StackTrace> * * * * * * * * A trace of the page cleaners will show that the cleaners * * keep on * * entering and exiting this function with rc = * * TRIGGER_SERVICED. * **************************************************************** * RECOMMENDATION: * * It is a rare problem to hit, but the customer's only option * * is to recycle the instance. * **************************************************************** | |
Local-Fix: | |
Recycle the instance | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows | |
Lösung | |
the problem is fixed in v97 fp 2 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC66974 Nachfolger : | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 08.03.2010 13.05.2010 13.05.2010 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7.FP2 | |
Problem behoben lt. FixList in der Version | |
9.7.0.2 |