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

AN ONLINE BACKUP MAY DELETE ARCHIVED LOG FILES THAT ARE REQUIREDBY THE
OLDEST REQUIRED BACKUP IMAGE.

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
An online backup may delete archived log files that are required 
by the oldest required backup image. 
 
If your database has the following: 
	db2 update db cfg using NUM_DB_BACKUPS <Value> 
	db2 update db cfg using REC_HIS_RETENTN <Value> 
	db2 update db cfg using AUTO_DEL_REC_OBJ ON 
 
Then an online backup initiates auto-prune when the following 
conditions are met: 
	- If the number of backups reaches the NUM_DB_BACKUPS value. 
	- If the oldest online backup which needs retaining has not 
reached REC_HIS_RETENTN. 
	- If the Transaction log file required by this backup is over 
REC_HIS_RETENTN, auto-prune will mistakenly delete it. 
 
eg. 
	db2 update db cfg using NUM_DB_BACKUPS 2 
	db2 update db cfg using REC_HIS_RETENTN 2 
	db2 update db cfg using AUTO_DEL_REC_OBJ ON 
 
When backup-initiated auto-prune happened, it was 
20170606021400. At this point of time, the following is the 
oldest backup that needs retaining. It was an online backup and 
not 2 days old yet. 
 
Op Obj Timestamp+Sequence Type Dev Earliest Log Current Log 
Backup ID 
-- --- ------------------ ---- --- ------------ ------------ 
-------------- 
  B  D  20170606021354001   N    D  S0000025.LOG S0000025.LOG 
---------------------------------------------------------------- 
------------ 
  Contains 5 tablespace(s): 
 
00001 SYSCATSPACE 
00002 USERSPACE1 
00003 IBMDB2SAMPLEREL 
00004 IBMDB2SAMPLEXML 
00005 SYSTOOLSPACE 
---------------------------------------------------------------- 
------------ 
    Comment: DB2 BACKUP SAMPLE ONLINE 
Start Time: 20170606021354 
   End Time: 20170606021356 
     Status: A 
---------------------------------------------------------------- 
------------ 
  EID: 47 Location: /backups 
 
The first log required by this oldest online backup that needs 
retaining is S0000025.LOG and it is over 2 days old. 
 
Op Obj Timestamp+Sequence Type Dev Earliest Log Current Log 
Backup ID 
-- --- ------------------ ---- --- ------------ ------------ 
-------------- 
  X  D  20170604021347      1    D S0000025.LOG C0000000 
---------------------------------------------------------------- 
------------ 
 
---------------------------------------------------------------- 
------------ 
    Comment: 
Start Time: 20170604021347 
   End Time: 20170606021357 
     Status: A 
---------------------------------------------------------------- 
------------ 
  EID: 44 Location: 
/logs/db2inst1/SAMPLE/NODE0000/LOGSTREAM0000/C0000000/S0000025.L 
OG 
 
As a result, auto-prune mistakenly deleted S0000025.LOG.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All Platforms                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Db2 LUW v11.1 Mod 3 Fixpack 3                     * 
****************************************************************
Local Fix:
Can look to increase NUM_DB_BACKUPS and/or REC_HIS_RETENTN.
available fix packs:
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows

Solution
First Fixed in Db2 LUW v11.1 Mod 3 Fixpack 3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
15.06.2017
16.03.2018
16.03.2018
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)