|
Problem IT05365
|
Status: Closed |
HISTORY PRUNNING NOT BEHAVING AS DOCUMENTED |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
When NUM_DB_BACKUPS and REC_HIS_RETENTN are set, it should
remove the expired backup just when both parameters are reached,
however, backup entries are being removed from the history file
even when NUM_DB_BACKUPS was not reached.
With this fix, backup entries will be removed from the history
file only when NUM_DB_BACKUPS is reached. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 10.5 Fix Pack 5 *
**************************************************************** |
| Local Fix: |
|
| Solution |
First Fixed in DB2 10.5 Fix Pack 5 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 04.11.2014
09.05.2017
09.05.2017 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.7
|
 |
