DB2 - Problem description
Problem IC80783 | Status: Closed |
DATABASE MAY HANG DUE TO SMALL TIMING HOLE WHEN TERMINATING AGENT SIGNALS LOGGER TO FLUSH THE TRANSACTION BUFFER | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
There is a small timing hole that can cause a database hang. When a terminating agent may need to have the transaction log buffer flushed, it posts a message to the db2loggr agent. In rare cases, if the db2loggr is responding to other posts at the same time, the post from the terminating agent may get lost. The db2agent would have the following stack, where it is waiting for a response from the db2loggr thread. This agent would be holding the database latch during this time, which will cause other agents waiting for the latch to wait. sqloWaitEDUWaitPost sqlpgPostLoggrWithoutLatching sqlpterm sqeLocalDatabase::CleanDB sqeLocalDatabase::TermDbConnect sqeApplication::AppStopUsing sqlesrspWrp sqleUCagentConnectReset sqljsCleanup sqljsDrdaAsInnerDriver sqljsDrdaAsDriver sqeAgent6RunEDU sqlzRunEDU The db2loggr thread, not seeing a waiting action would then go to sleep waiting for more work: sqloWaitEDUWaitPost sqlpgasnPcj sqloEDUEntry | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All DB2 users * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 9.7 Fix Pack 7 or higher * **************************************************************** | |
Local Fix: | |
None, though the chance to hit the timing hole is small. | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows | |
Solution | |
Problem first fixed in DB2 Version 9.7 Fix Pack 7 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 11.01.2012 31.10.2012 31.10.2012 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP7 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.7 |