home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC67143 Status: Closed

ROLLFORWARD USING END OF BACKUP OPTION FOR TABLESPACE RECOVERY PROCESSES
ROLLFORWARD TO END OF LOGS.

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Using the END OF BACKUP option on a rollforward command for 
tablespace recovery results in rolling forward to the end of the 
logs. 
 
With this APAR fix, the END OF BACKUP option for tablespace 
recovery will roll forward to the highest Minimum Recovery Time 
(MRT) for the tablespace(s) being restored, over all database 
partitions. 
 
Note that the minimum recovery time for the tablespace(s) will 
be at least the timestamp of the end of the backup, but may be 
later if there are catalog updates that affect the 
tablespace(s).
Problem Summary:
ROLLFORWARD USING END OF BACKUP OPTION FOR TABLESPACE RECOVERY 
PROCESSES ROLLFORWARD TO END OF LOGS.
Local Fix:
As a workaround: 
 
1. Run 
 
db2 list tablespaces show detail 
 
on all nodes 
 
2. Get the highest MRT (minimum recovery time) of the 
tablespace(s) being recovered. 
 
3. Rollforward to PIT using the MRT from the step 2.
available fix packs:
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 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 DB2 v97FP3 
 
LOCAL FIX: 
As a workaround: 
 
1. Run 
 
db2 list tablespaces show detail 
 
on all nodes 
 
2. Get the highest MRT (minimum recovery time) of the 
tablespace(s) being recovered. 
 
3. Rollforward to PIT using the MRT from the step 2.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC68639 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
12.03.2010
29.09.2010
29.09.2010
Problem solved at the following versions (IBM BugInfos)
9.7.FP3
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.3 FixList
9.7.0.3 FixList