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

"RECOVER DB" COMMAND IS NOT PICKING UP CORRECT DB2 BACKUP IMAGE FOR
RECOVERY TILL POINT IN TIME.

product:
DB2 FOR LUW / DB2FORLUW / A50 - 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 consideration
and should choose first backup image for Recover DB operation.


NOTE:  this problem was originally fixed via APAR IZ58872 in
Version 9.5fp6a, APAR IC68413 in Version 9.7, and APAR IC68414
in Version 9.8, however the problem was not fixed in versions
after Version 9.8.  The intent of this new APAR is to
permanently fix this issue in the current release inclusive of
this new APAR and all future releases.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 10.5 Fix Pack 10 or higher                    *
****************************************************************
Local Fix:
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.
Or
Upgrade to the fixpack inclusive of this APAR fix.
Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
21.05.2018
19.07.2018
19.07.2018
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)