16.4.2 Terminating HADB servers in the multi-node configuration

(a) Normally terminating HADB servers in the multi-node configuration

The following shows the procedure for normally terminating the HADB servers in the multi-node configuration.

Procedure:

1. Execute the adbstop command on the master node.

   When the adbstop command is executed on the master node, the HADB servers on all nodes terminate normally.

2. Execute HA Monitor's monend command on the master node.

   After confirming that the HADB servers on all nodes have terminated normally, execute HA Monitor's monend command on the master node.

(b) Forcibly terminating HADB servers in the multi-node configuration

The following shows the procedure for forcibly terminating the HADB servers in a multi-node configuration.

Procedure:

1. Execute the adbstop --force command on each slave node.

   Execute the adbstop --force command on all slave nodes.

   In addition, confirm that the adbstop --force command terminated on all slave nodes.

2. Execute the adbstop --force command on the master node.

   Confirm that the adbstop --force command terminated.

3. Execute HA Monitor's monend command on the master node.

(a) Normally terminating the HADB server on the master node only

The procedure for normally terminating the HADB server only on the master node differs depending on whether you are using host reset or SCSI reservation for shared disk.

• When using host reset

  If you execute the HA Monitor monswap command on the master node, only the HADB server on the master node ends normally. At this time, a master node switchover occurs, and the slave node with the highest priority becomes the master node.

  Furthermore, if you execute the monswap command, all running transactions on the master node are canceled, and all the connections running those transactions are terminated. All connections that have not yet run any transactions are also terminated. After the connection termination processing is complete, the master node's HADB server begins its termination processing.

  Important

  If you accidentally terminate the master node's HADB server by using the adbstop --node command, execute the monswap command on that node.

• When using SCSI reservation for shared disk

  Procedure:

  1. Execute the adbstop --cancel --node command on the master node.

  2. Execute the HA Monitor command monswap on the master node.

  This procedure normally terminates the HADB server only on the master node. At this time, a master node switchover occurs, and the slave node with the highest priority becomes the master node.

(b) Forcibly terminating the HADB server on the master node only

If you execute the adbstop --force command on the master node, only the master node's HADB server is forcibly terminated. At this time, a master node switchover occurs, and the slave node with the highest priority becomes the master node.

Note

Recovery processing (rollback) performed on update processing that had been running on the master node you forcibly terminated, is executed on the slave node that becomes the new master node.

(c) Normally terminating the HADB server on a slave node only

Execute the adbstop --node command on a slave node to normally terminate the HADB server of the slave node on which the command is executed.

(d) Forcibly terminating the HADB server on a slave node only

Execute the adbstop --force command on a slave node to forcibly terminate the HADB server of the slave node on which the command is executed.