Upgrade Db2 High Availability Disaster Recovery (HADR) environments
You can upgrade the primary database of a Db2 high availability disaster recovery (HADR) deployment without reinitializing the standby database. Reinitialization of the standby is still an option, but is no longer the recommended option.
- Upgrading Db2 servers in HADR environments that require standby reinitialization. There is no minimum Db2 version requirement for this method.
- Upgrading Db2 servers in HADR environments without standby reinitialization. The minimum Db2 version requirement for this method is Db2 single partition users upgrading from Db2 11.1 or later, and for Db2 pureScale® users upgrading from Db2 11.1.1.1 or later.
- Upgrading a Db2 server in an HADR environment with down-level standby for Reads on Standby. When upgrading a Db2 11.5.8 or later High Availability Disaster Recovery (HADR) environment to Db2 12.1 or later, you can use this procedure to allow read-only applications to access the database by using the HADR reads on standby feature during the upgrade of the primary database. After the primary database is upgraded, the standby database can be upgraded to the new Db2 version, without the need to reinitialize HADR.
- Upgrading Db2 servers in a Pacemaker automated HADR environment. Use this method to upgrade a Pacemaker automated HADR environment from a previous Db2 version.
- Upgrading Db2 servers in a TSA automated HADR environment from a previous Db2 Version on AIX. Use this method to upgrade a TSA automated HADR environment from a previous Db2 version.
If you have multiple databases in the same instance, and under normal conditions the primary role for these databases are running on different hosts, you need to first move the primary role of all the databases in the instance to the same host, before executing HADR upgrade procedure. The HADR upgrade procedure requires that one system/instance be identified to contain all primary databases and the second system/instance be identified to contain all standby databases. Where necessary, issue graceful takeover to achieve this layout of primary and standby databases.