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

INCREMENTAL AUTOMATIC RESTORE ON DB2 VERSION 9.5 FP9 MAY FAIL WITH SQL2571N
REASON CODE 3

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
An Incremental Automatic Restore on DB2 Version 9.5 FP9 may fail 
with SQL2571N Reason Code 3. 
 
Here is an example on that: 
 
$ db2_all "<<+0< db2 restore db SAM incremental automatic from 
/test/backup taken at 20110726092149 INTO SAM REPLACE HISTORY 
FILE Replace Existing without prompting" 
 
SQL2571N An automatic restore is unable to proceed. Reason code: 
"3". 
x336solaris1: db2 restore db SAM ... completed rc=4 
 
Entries on db2diag.log will show something like the following: 
 
DATA #1 : String, 126 bytes 
During verification, missing required backup image was noticed 
for tablespace SYSCATSPACE. Tablespace was in search state I.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.5 Fix Pack 10.                      * 
****************************************************************
Local Fix:
Solution
First fixed in DB2 Version 9.5 Fix Pack 10.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
26.04.2012
18.10.2013
18.10.2013
Problem solved at the following versions (IBM BugInfos)
9.5.FP10
Problem solved according to the fixlist(s) of the following version(s)
9.5.0.10 FixList