Restarting Db2 HADR on the designated auxiliary standby database
Upgrade to IBM Software Hub Version 5.1 before IBM Cloud Pak for Data Version 4.8 reaches end of support. For more information, see Upgrading from IBM Cloud Pak for Data Version 4.8 to IBM Software Hub Version 5.1.
An auxiliary standby database might have been the primary database because of maintenance or unavailability of the primary and principal standby databases. When the primary and/or principal standby databases became available, and a takeover was executed back to one of those two databases, HADR is automatically stopped on the auxiliary database.
About this task
Because Governor, the automated failover mechanism, is not running on auxiliary databases, HADR must be explicitly restarted by using the manage_hadr tool with the -start_as standby option.
The -status option with the manage_hadr tool displays the following message to indicate that HADR is not started:
oc exec -it c-${aux1_id}-db2u-0 -n ${aux1_project} -- manage_hadr -status
Output:
#######################################################################
### Db2 Advanced Edition high availability and ###
### disaster recovery (HADR) management ###
#######################################################################
Running HADR action -status on the database BLUDB ...
Unable to query HADR status.
################################################################################
* The requested HADR operation failed.
* Correct the errors and rerun the manage_hadr command.
################################################################################
Procedure
oc exec -it c-db2-aux-db2u-0 -- manage_hadr -start_as standby