|
Problem IC66362
|
Status: Closed |
TABLE SPACE ROLL FORWARD MAY SKIP LOG RECORDS IF INTERRUPTED |
| product: |
DB2 FOR LUW / DB2FORLUW / 910 - 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: *
* Users of table space level roll forward. *
****************************************************************
* PROBLEM DESCRIPTION: *
* If a table space level roll forward is interrupted during *
* the undo phase, and then restarted, it might start at a log *
* sequence number that is too high, resulting in skipped log *
* records which can cause unpredictable errors. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to latest fix pack. *
**************************************************************** |
| Local Fix: |
Use database level recovery. |
| available fix packs: |
DB2 Version 9.1 Fix Pack 9 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 10 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12 for Linux, UNIX and Windows
|
| Solution |
Problem first fixed in DB2 UDB version 9.1 fix pack 9. |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC66820
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 16.02.2010
07.04.2010
07.04.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.1.FP9
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.1.0.9
|
 |
