High availability, backup, logging, resiliency, and recovery enhancements

Db2 11.5.9 includes enhancements that help ensure that your data remains available.

Attention: This mod pack release is currently available for the following Db2 products:
The following table displays a list of high availability, backup, logging, resiliency, and recovery enhancements in Db2 11.5.9:
Table 1. High availability, backup, logging, resiliency, and recovery enhancements in Db2 11.5.9
Enhancement Description
UPDATE HISTORY command

The UPDATE HISTORY command has been enhanced to allow status field updates of any database history file entry to X (DB2HISTORY_STATUS_DO_NOT_DELETE), indicating a do not delete status.

Database history file entries with status fields marked X (DB2HISTORY_STATUS_DO_NOT_DELETE) will not be pruned by:
  • automated database history file pruning,
  • calls to the PRUNE HISTORY command,
  • calls to the db2Prune API,
  • or by running the ADMIN_CMD procedure with PRUNE HISTORY.
The do not delete status can be used to protect key database history file entries from being pruned. In addition, if the database history file entry is related to a recovery object, such as a log file, backup copy image, or a load copy image, the recovery object will not be deleted.
Pacemaker software refresh With the release of Db2 11.5.9, Pacemaker is upgraded from version 2.1.2 to 2.1.6, and the CRM Shell (crmsh) is upgraded from version 4.4.0 to 4.5.0.