DB2 - Problem description
Problem IC79533 | Status: Closed |
DB2 AGENT HANG IN SQLPGWAITFORLRECONDISK DUE TO MISSING POST. | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
In rare conditions, a db2agent may be stuck in following call stacks due to missing post during writing log records into disk. sqlpgWaitForLrecOnDisk + 0x330 sqlpWriteToLog + 0x7D8 sqlpWriteLR + 0x418 The above stacks should be observed in a stack file(use db2pd -stack all to generate stack files) for several rounds for a long time. If this db2agent had obtained some latches, then there is a chance to hang database due to latch wait cascaded. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All. * **************************************************************** * PROBLEM DESCRIPTION: * * In rare conditions, a db2agent may be stuck in following * * call stacks due to missing post during writing log records * * into disk. * * * * sqlpgWaitForLrecOnDisk + 0x330 * * sqlpWriteToLog + 0x7D8 * * sqlpWriteLR + 0x418 * * * * The above stacks should be observed in a stack file(use * * db2pd -stack all to generate stack files) for several rounds * * for a long time. * * * * BTW, if this db2agent had obtained some latches, then there * * is a chance to hang database due to latch wait cascaded. * **************************************************************** * RECOMMENDATION: * * Update to version 9.7 fixpack 3 or later fixpacks. * **************************************************************** | |
Local Fix: | |
No known work around. | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows | |
Solution | |
This problem is first fixed in version 9.7 fixpack 3. | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC82267 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 31.10.2011 03.11.2011 04.04.2012 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP3 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.3 | |
9.7.0.3 |