Db2
11.5.7 includes enhancements that help ensure that your data remains available.
Attention: This mod pack release is currently available for
the following
Db2 products:
Db2 on Cloud and
Db2 Warehouse on Cloud will be updated to version 11.5.7 early
in 2022.
The following table lists high availability enhancements that are available in
11.5.7:
Table 1. High availability
enhancements in 11.5.7
Enhancement |
Description |
Added support for PPCLE platform for Automated HADR failover with Pacemaker |
Automated HADR failover with Pacemaker is now
supported on RHEL 8.2 on PPCLE and SLES 15 SP3 on PPCLE. |
Pacemaker
software refresh |
- Pacemaker
has been upgraded from 2.0.4 to 2.0.5. This is to address CVE-2020-25654.
- crmsh has been upgraded from 4.2.0 to 4.3.1. This is to address CVE-2020-35459.
|
Improved HADR database hang detection on AIX platforms |
Improved primary HADR hang detection for Tivoli®
SA MP HADR
deployments. If connections to the primary database are unresponsive, the cluster manager will
initiate a failover to the standby. |
The following table lists backup and restore enhancements that are available in
11.5.7:
Table 2. Backup and restore
enhancements in 11.5.7
Enhancement |
Description |
ZLIB compression
for backup and log file compression |
ZLIB compression can now be used for backup and log file compression. On Power9 and z15 and
higher, the compression makes use of the on-chip hardware accelerators. |
The following table lists database logging enhancements that are available in
11.5.7:
Table 3. Database logging
enhancements in 11.5.7
Enhancement |
Description |
Log archive and
retrieve to remote storage. Added new log archive method type DB2REMOTE. |
Db2 log archiving and retrieving operations now support remote storage, such as IBM Cloud
Object Storage or Amazon Simple Storage Service (S3). The database configuration parameters logarchmeth1 and
logarchmeth2 now accept
a new log archive method type of DB2REMOTE. You must follow this value with a colon (:) and specify
a remote storage location by using a storage access alias. For more information, see Configuration parameters
for database logging. |