|
Problem IT03081
|
Status: Closed |
AUTO DELETION OF BACKUP OBJECTS NO LONGER WORKING AFTER SWITCHING BETWEEN ARCHIVAL AND CIRCULAR LOGGING |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
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. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* all *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade the database server to V9.7 Fix Pack 9 *
**************************************************************** |
| Local Fix: |
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). |
| available fix packs: |
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
|
| Solution |
This problem has first been fixed in v9.7 Fix Pack 9 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 10.07.2014
10.07.2014
10.07.2014 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP9
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.4
|
 |
