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

DB2 PRUNE HISTORY YYYYMMDDHHMMSS AND DELETE IS DELETING NECESSARY LOG with
online backups.

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
db2 "prune history yyyymmddhhmmss and delete" is deleting 
necessary LOG. 
 
db2 list history backup all for db sample | grep  " B " 
  B  D  20140618144208001   F    N  S0000000.LOG S0000000.LOG 
  B  D  20140618145059001   N    D  S0000000.LOG S0000000.LOG 
  B  D  20140618145214001   N    D  S0000001.LOG S0000001.LOG 
 
db2 list history archive log all for db sample | grep  " X " 
  X  D  20140618145101      1    D  S0000000.LOG C0000000 
  X  D  20140618145101      1    D  S0000001.LOG C0000000 
  X  D  20140618145217      P    D  S0000002.LOG C0000000 
 
 
specify 20140618145216(Between last backup date 20140618145214 
and last archived date 20140618145217) in prune history and 
delete 
db2 prune history 20140618110156 and delete 
 
$ db2 connect to sample 
 
   Database Connection Information 
 
 Database server        = DB2/AIX64 10.1.2 
 SQL authorization ID   = DB2INST1 
 Local database alias   = SAMPLE 
 
$ db2 prune history 20140618145216 and delete 
DB20000I  The PRUNE command completed successfully. 
$ db2 list history backup all for db sample | grep  " B " 
  B  D  20140618145214001   N    D  S0000001.LOG S0000001.LOG 
$ db2 list history archive log all for db sample | grep  " X " 
  X  D  20140618145217      1    D  S0000002.LOG C0000000 
 
db2 deleted S0000001.LOG. 
So, DB2 can not restore backup due to lack of LOG file.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 UDB version 10.5 fix pack 5.                  * 
****************************************************************
Local Fix:
Use LOGFILE PRIOR TO instead of history yyyymmddhhmmss and 
delete.
Solution
Problem was first fixed in DB2 UDB Version 10.1 fix pack 5.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
14.07.2014
14.07.2015
14.07.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.5 FixList