|
Problem IC64250
|
Status: Closed |
ZERO LSN ERRONEOUSLY WRITTEN TO INDEX PAGE DURING CRASH RECOVERY |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
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. |
| Problem Summary: |
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. |
| Local Fix: |
n/a |
| available fix packs: |
DB2 Version 9.1 Fix Pack 9 for Linux, UNIX and Windows
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.1 Fix Pack 10 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.1 Fix Pack 11 for Linux, UNIX and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.1 Fix Pack 12 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 has been corrected such that if LSN is zero, a
valid LSN will be obtained and used instead as the page LSN. |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IZ64705
follow-up : |
| Timestamps |
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) |
| 9.1.0.9
|
 |
| 9.7.0.2
|
|
