Upgrading Db2 servers in HADR environments without standby reinitialization

Upgrading Db2 servers in HADR multiple standby environments without standby reinitialization maintains the database role and relies on the normal log shipping and log replaying characteristics that are common to the HADR functionality. This method does not stop HADR for upgrades and avoids the need to reinitialize HADR after the upgrades. This benefit of this method is that it reduces the window where no standby database exists and eliminates the cost of sending a backup image to the standby site for reinitialization.

The minimum requirement for using this procedure is Db2 version 10.5 Fix Pack 7 or later.

This procedure ensures all log data generated by the primary database prior to the upgrade are shipped and replayed by all standbys. This is enforced by the use of db2ckupgrade that is run during db2iupgrade or any db2ckupgrade invocation that establishes an exclusive connection to the database to do proper database consistency checking.

Use the following procedures to execute this method based in single standby, multiple standby or pureScale environment:

• Upgrading Db2 servers in HADR single standby environments without standby reinitialization
• Upgrading Db2 servers in HADR multiple standby environments without standby reinitialization
• Upgrading Db2 servers in HADR pureScale environments without standby reinitialization