|
Problem IC71207
|
Status: Closed |
TBSP RF MAY MISS LOG RECS FOR A TBLSP, AFTER CRASH RECOVERY. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
Following sequence of events may leave the tablespace in RF
pending state after crash recovery:
1. Registry variable set to collect tablespace log history
(default)
2. Crash recovery that skips a tablespace (ie, container
unavailable) so tablespace is RF pending
3. Ssubsequent empty crash recovery (ie, no log records actually
replayed, minbuffLSN = lowtranLSN)
4. Roll forward of the skipped tablespace
That roll forward may skip log records for the tablespace that
occurred before the empty recovery. |
| Problem Summary: |
TBSP RF MAY MISS LOG RECS FOR A TBLSP, AFTER CRASH RECOVERY.
ERROR DESCRIPTION:
Following sequence of events may leave the tablespace in RF
pending state after crash recovery:
1. Registry variable set to collect tablespace log history
(default)
2. Crash recovery that skips a tablespace (ie, container
unavailable) so tablespace is RF pending
3. Ssubsequent empty crash recovery (ie, no log records actually
replayed, minbuffLSN = lowtranLSN)
4. Roll forward of the skipped tablespace
That roll forward may skip log records for the tablespace that
occurred before the empty recovery. |
| Local Fix: |
Restore and rollforward the tablespace. |
| available fix packs: |
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.7 Fix Pack 6 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 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Fixed in V97 FP4. |
| Workaround |
Restore and rollforward the tablespace. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 15.09.2010
02.05.2011
02.05.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
|
 |
