Upgrading Db2 servers in an automated HADR environment

Upgrade to Db2 version 11.1 in an automated HADR environment from a previous Db2 Version.

Before you begin

Ensure that you have root access on Linux® and UNIX operating systems or Local Administrator authority on Windows.
Ensure that you have SYSADM authority.
Perform pre-upgrade tasks for Db2 servers

This topic explains the upgrade procedure for automated HADR environments.

Upgrading the HADR primary and standby database through re-initialization of the HADR pair

Stop HADR by running db2 stop hadr command on the database dbname.
Delete the resources for the current instance by using the db2haicu -delete command. Deleting the cluster resources is an irreversible step. Before you do this, ensure that a snapshot of the resource model for the instance is captured by using the lssam command. The resource model needs to be re-created after the upgrade is complete.
Deactivate the databases on both the primary and standby servers.
Stop the Db2 instance by using db2stop command.
Install Db2 version 11.1 in a new directory path.
Upgrade the Db2 instance by using the db2iupgrade command.
Start the Db2 instance by using the db2start command.
If you are completing an upgrade on a primary server, upgrade the database by using the db2 upgrade dbname command.

After the HADR pair is initialized once again, the cluster domain resources must be re-created. For more information about re-creating cluster domain resources, see: Automating HADR on Db2 LUW Failover Solution Using Tivoli System Automation for Multiplatforms.