DB2 FOR LUW / DB2FORLUW / A50 - DB2

Auto deletion of backup objects is enabled via the 
AUTO_DEL_REC_OBJ db cfg parameter. 
 
When changing from archival logging to circular logging ( and 
back as needed ), it is possible log this auto deletion will 
stop working. 
This is triggered by the fact that  the log file sequence in the 
history files gets reset, so the log file numbers will start 
back at 0. 
 
This can cause the prune history logic to become confused and 
set the timestamp from where to prune backup images back at the 
beginning of the history file, thereby failing to prune images 
that should be removed.

**************************************************************** 
* USERS AFFECTED:                                              * 
* all                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade the database server to V9.7 Fix Pack 9               * 
****************************************************************

As a workaround, the entries to be pruned can manually be 
updated using the "UPDATE HISTORY" command and changing 
the obsolete history entries from 'A' (active) to 'D' (delete).

DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
 DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
 

This problem has first been fixed in v9.7 Fix Pack 9

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

10.07.2014
10.07.2014
10.07.2014

9.7.FP9