DB2 - Problem description
Problem IC99827 | Status: Closed |
HISTORY PRUNNING NOT BEHAVING AS DOCUMENTED | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - 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 Problem Description above. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 9.7 Fix Pack 10. * **************************************************************** | |
Local Fix: | |
Solution | |
First Fixed in Version 9.7 Fix Pack 10. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 04.03.2014 07.11.2014 07.11.2014 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP10 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.10 |