DB2 - Problem description
Problem IT25196 | Status: Closed |
OLDER DATAL ARCHIVE LOGS ARE NOT PRUNED BY "PRUNE HISTORY TIMESTAMP AND DELETE" COMMAND UNEXPECTEDLY | |
product: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problem description: | |
If NUM_DB_BACKUPS DB config parameter is configured, the backup entries within NUM_DB_BACKUPS value may be unexpectedly retained in the Recovery History File after "prune history TIMESTAMP and delete" command is issues even if the timestamp of the backup entries are older than one on the "prune history" command. Then the older archive log files may not be pruned which are within the range of the retained backup object entries. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 11.1 Mod 4 Fixpack 4 or higher * **************************************************************** | |
Local Fix: | |
"WITH FORCE OPTION" option usage on the "prune history" command is a option of the work around. | |
Solution | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 30.05.2018 27.11.2018 27.11.2018 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |