|
Problem IC66970
|
Status: Closed |
DB2 PAGE CLEANER HANGS MAY LEAD TO DATABASE HANGING |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
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 Summary: |
****************************************************************
* 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 |
| available fix packs: |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
the problem is fixed in v97 fp 2 |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC66974
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 08.03.2010
13.05.2010
13.05.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP2
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.2
|
 |
