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

EXTENT MOVEMENT CAN CAUSE INCREMENTAL BACKUP CORRUPTION

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Extent movement does not "flag" the pages moved, causing 
incremental backup to not pick these pages up.  On the other 
hand, since the meta data that stores the location information 
of these pages have been flaged for incremental backup, only the 
meta data is backed up.  This means the backup image now contain 
up-to-date meta data with new information but not the actual 
pages at the new location, leading to corruption if such backup 
image is restored. 
 
Extent movement can be triggered by the ALTER TABLESPACE LOWER 
HIGH WATER MARK, or the ALTER TABLESPACE REDUCE command.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Extent movement corrupts incremental backup images.  If the  * 
* incremental backup images are restored, it will result in    * 
* database corruption                                          * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* If extent movement has been performed on a tablespace,       * 
* discard all incremental backup images that contain that      * 
* tablespace.  Take a full backup of the tablespace and the    * 
* meta data will be reset so incremental backup can be taken   * 
* again on that tablespace.                                    * 
****************************************************************
Local Fix:
Do not use incremental backup if extent movement has been 
issued, take a full tablespace backup instead.  Incremental 
backup is safe 
as long as there is no extent movement on the tablespace since 
the last full backup.
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
db2 v97 fp4
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
01.11.2010
28.04.2011
28.04.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 FixList