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 IC65345 Status: Closed

ROLLFORWARD FAILS WHILE REPLAYING INDEX RECORDS DUE TO LACK OF OBJECT
TABLE SPACE

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Rollforward fails while replaying index records due to lack of 
object table space 
 
The following forward recovery scenario may result in a system 
outage during rollforward: 
 
1. Create backup1 
2. Create first index I1 on a table 
3. Create backup2 
4. Restore backup1 and rollforward 
5. Drop index I1 
6. Restore backup2 and rollforward 
 
User will observe instance crash and one of the following 
messages might be logged in db2diag.log: 
 
sqldRedoUpsert: "Free space doesn't not match during redo" 
 
or 
 
loadOrValSubDMSDesc, "Failed fetching record from object table!"
Problem Summary:
The problem is that a change of index life LSN was not logged 
even though the life LSN did change when the index was mark bad. 
When the last "rollforward db <dbname> to end of logs" is 
executed, rollforward does NOT replay the drop index log record 
because the index life LSN in this log record is lesser than the 
current index life LSN from the object table entry. The record 
was not deleted from the object table; therefore, the space was 
not freed up. Then an error is enountered while redoing an 
insert there is not enough space in the object table page.
Local Fix:
n/a
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
This APAR fix is targeted for Fix Pack 9.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IZ67734 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
06.01.2010
07.01.2010
07.01.2010
Problem solved at the following versions (IBM BugInfos)
9.0.
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.2 FixList