|
Problem IC66821
|
Status: Closed |
TABLE SPACE ROLL FORWARD MAY SKIP LOG RECORDS IF INTERRUPTED |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
If a table space level roll forward is interrupted during the
undo phase, it is possible that when it is restarted, it might
start in the wrong place. This could cause log records to be
missed, resulting in unpredictable errors . |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All users of tablespace rollforward. *
****************************************************************
* PROBLEM DESCRIPTION: *
* A restarted tablespace rollforward may restart in the *
* wrongspot, causing log records to be skipped. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to the most recent fix pack. *
**************************************************************** |
| Local Fix: |
Use database level recovery. |
| available fix packs: |
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.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 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 |
Problem is first fixed in DB2 UDB version 9.7 fix pack 2. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 02.03.2010
25.05.2010
25.05.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP2
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.2
|
 |
