DB2 - Problem description
|Problem IC64250||Status: Closed|
ZERO LSN ERRONEOUSLY WRITTEN TO INDEX PAGE DURING CRASH RECOVERY
DB2 FOR LUW / DB2FORLUW / 970 - DB2
During crash recovery, while replaying index manager transactions, DB2 may incorrectly write zero log sequence number (LSN) to an index page on disk. This may occur under a very particular set of internal factors. This problem can result in the index corruption which can lead to a crash once the corrupted index page is referenced.
If for some reason (e.g. operation cancelled) DB2 does not write the log record whose log sequenNe number (LSN) would have been as the index page (LSN), it may end up writing a page with a zero LSN to disk.
|available fix packs:|
DB2 Version 9.1 Fix Pack 9 for Linux, UNIX and Windows
The problem has been corrected such that if LSN is zero, a valid LSN will be obtained and used instead as the page LSN.
not known / see Local fix
forerunner : APAR is sysrouted TO one or more of the following: IZ64705 follow-up :
Date - problem reported : Date - problem closed : Date - last modified :
30.10.2009 16.04.2010 16.04.2010
|Problem solved at the following versions (IBM BugInfos)|
|Problem solved according to the fixlist(s) of the following version(s)|