|
Problem IC68413
|
Status: Closed |
"RECOVER DB" COMMAND IS NOT PICKING UP CORRECT DB2 BACKUP IMAGE FOR RECOVERY TILL POINT IN TIME. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
RECOVER DB" command is not picking up correct db2 backup image
for recovery till point in time and hence, fails with SQL1275N.
Consider that we have taken two backups as follows:
Backup 1:
----------------------------------------------------------------
Comment: DB2 BACKUP TEST OFFLINE
Start Time: 20090805005504
End Time: 20090805005505
Status: A
----------------------------------------------------------------
EID: 9 Location: /home/db2inst1
Backup 2:
----------------------------------------------------------------
Comment: DB2 BACKUP TEST OFFLINE
Start Time: 20090805053413
End Time: 20090805053449
Status: A
----------------------------------------------------------------
EID: 14 Location: /home/db2inst1
Then following RECOVER DB till PIT fails.
$ db2 recover db test to 2009-08-05-05.34.20 using local time
SQL1275N The stoptime passed to roll-forward must be greater
than or equal to "2009-08-05-05.34.46.000000 Local", because
database "TEST" on node(s) "0" contains information later than
the specified time.
Here, DB2 uses second backup image and later on, Rollforward
till Point in Time operation fails because PIT timestamp is
lesser than MRT timestamp. In such cases, DB2 should take PIT
timestamp into considerration and should choose first backup
image for Recover DB operation. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Prior to DB2 V97 FP3. *
****************************************************************
* PROBLEM DESCRIPTION: *
* "RECOVER DB" COMMAND IS NOT PICKING UP CORRECT DB2 BACKUP *
* IMAGE FOR RECOVERY TILL POINT IN TIME. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 V97 FP3. *
**************************************************************** |
| Local Fix: |
Restore first backup image and then do RollForward till PIT as
per your requirement.
Please make sure that MRT of first database backup image is
lesser than PIT you want. |
| 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 |
First Fixed in DB2 Version 9.7 Fix Pack 3 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 04.05.2010
24.09.2010
29.11.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
|
 |
| 9.7.0.3
|
|
