DB2 FOR LUW / DB2FORLUW / 950 - DB2

In the existing code, the automatic incremental restore logic 
would try to restore a merged backup as the base of chain of 
incrementals (or deltas).  In reality, this leads to chain 
validation errors in the SPCS chaining logic.  The correct 
algorithm is: 
 
* If the target image (or the newest image on a chain with a 
timestamp less than the target image) is a merged image, use it. 
 
 
* Otherwise, if we are restoring a chain of incremental/delta 
images, use only real DB2 backups.  (ie, No merged images.) 
 
For example, given a series of backups for a particular 
tablespace: 
 
    F --> D1 --> D2 --> M1 (= F+D1+D2) --> D3 
 
[F = Full (non-incremenal backup) 
D1, D2, D3 = Incremental delta backups 
M1 = Merged backup] 
 
the existing code would select M1 + D3 as the restore set.  The 
correct restore set is F + D1 + D2 + D3.  (If the user wants to 
restore using M1 as the target, then we'll restore just that one 
image.)

**************************************************************** 
* USERS AFFECTED:                                              * 
* Database administrators who use the DB2 Merge Backup tool    * 
* and try to perform an incremental restore of a database.     * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* The user has a database backup strategy that includes the    * 
* use of incremental backups.  The user uses the DB2 Merge     * 
* Backup tool to merge one or more of these incremental        * 
* backups with a full non-incremental backup.  At some later   * 
* point, the user attempts a database-level or                 * 
* tablespace-level restore operation, specifying the           * 
* "incremental auto" option.  The restore operation fails with * 
* the error SQL2572N.                                          * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* The customer should upgrade to DB2 LUW v9.5 fp9.             * 
****************************************************************

To avoid this scenario, a user would preform a non-automatic 
incremental restore operation.

DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
 

The error is corrected in Fixpak 9.  The restore operation will 
conclude successfully.

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

09.11.2011
08.03.2012
08.03.2012

9.0.,
9.5.FP9