Managing HADR with CLI commands for Db2

You can use Db2 HADR CLI commands to show the HADR status, manually initiate a takeover, stop HADR, and enable the HADR Automatic Client Reroute feature

Showing the HADR status for Db2
You can monitor the state of your HADR configuration by running the --manage_hadr command with the -status option in the Db2 engine pod.
Manually initiating an HADR takeover in Db2
To initiate a takeover of the standby database, use the --manage_hadr command with the -takeover option in the Db2 engine pod. To switch to an auxiliary database, use the optional aux and force parameters with the -takeover option.
Restarting HADR after a failover in Db2
After a failover (forced takeover), HADR is stopped on the former primary database. This database might need to be manually reintegrated as a standby.
Stopping HADR for Db2
To stop the HADR process on the Db2 database and to stop the Governor automated failover mechanism, run the manage_hadr command with the -stop option.
Enabling HADR Automatic Client Reroute on Db2
You can enable the Db2 HADR Automatic Client Reroute (ACR) feature by running the manage_hadr command with the -enable_acr option.

Parent topic: Db2 high availability disaster recovery (HADR)