Performing rolling updates in an automated Db2 high availability disaster recovery (HADR) environment
When you use the integrated High Availability (HA) feature to automate HADR, extra steps are required to update operating system or Db2® database system software, upgrade hardware, or change database configuration parameters. Use this procedure to perform a rolling upgrade in an automated HADR environment.
Before you begin
- Two Db2 instances.
- Two Db2 servers.
- The instances are originally running at Version 11.1.1.1 or a later version. If the instances are running on version 11.1 GA, refer to this IBM® technote.
- The instances are configured with IBM Tivoli® System Automation for Multiplatforms (SA MP) controlling HADR failover.
The HADR pair must be in PEER state prior to starting the rolling update.
Restrictions
Use this procedure to perform a rolling update on your Db2 database system and update the Db2 database product software to a new fix pack level in an automated HADR environment. For example, applying a fix pack to a Db2 database product software.
- The Db2 instances must be currently running at Version 11.1.1.1 or a later version. If the instances are running on version 11.1 GA, refer to this IBM technote.
A rolling update cannot be used to upgrade a Db2 database system from an earlier version to a later version. For example, you cannot use this procedure to upgrade from Db2 version 10.5 to Db2 version 11.1. To upgrade a Db2 server in an automated HADR environment, see Upgrading Db2 servers in an automated HADR environment .
You cannot use this procedure to update the Db2 HADR configuration parameters. Updates to the HADR configuration parameters must be made separately. Because HADR requires the parameters on the primary and standby to be the same, both the primary and standby databases might need to be deactivated and updated at the same time.