DB2 - Problem description
Problem IC73422 | Status: Closed |
CRASH RECOVERY MAY USE OLD VERSION OF LOG PAGE FOR RECOVERY | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
Crash recovery may use an older version of a log page to complete crash recovery, such that committed log records are not replayed. There may not be any error indicated on the crash recovery, but there could be missing data, or uncommitted data left in the database. This error can only occur while writing a partial log page to a new log file and a subsequent re-write of the same log page, to the last page of the current log file, is abnormally terminated (i.e. power outage). | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * Crash recovery may use an older version of a log page to * * complete crash recovery, * * as such, committed log records my not be replayed. The * * crash recovery may complete * * successfully, but the database may contain uncommitted data * * or missing data. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 V9.7 Fix Pack 4. * **************************************************************** | |
Local Fix: | |
Restore and roll forward to point in time before end of logs. | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows | |
Solution | |
Problem was first fixed in DB2 V9.7 Fix Pack 4. | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC73679 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 21.12.2010 28.04.2011 28.04.2011 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP4 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.4 |