Nonstop Database, HiRDB Version 9 System Operation Guide

[Contents][Index][Back][Next]

26.6.2 Planned system switchover

This subsection explains how to perform a planned system switchover.

The two methods described below are available for planned system switchovers. Select the one that best suits the environment you are using.

Organization of this subsection
(1) Using method 1 to execute a planned system switchover
(2) Using method 2 to execute a planned system switchover

(1) Using method 1 to execute a planned system switchover

The planned system switchover procedure is as follows.

Procedure
  1. Use the pdls -d ha command or the corresponding cluster software command to confirm the following:
    [Figure] The unit subject to the planned system switchover is active.
    [Figure] The planned system switchover target unit is in standby status.
  2. Execute the pdtrnqing command at the source unit and start transaction queuing.
    During this step, confirm that the pdtrnqing command terminated normally with a return code of 0. If the return code is 0, transaction queuing has started normally. If the return code is 8 or 12, transaction queuing has not started. In this case, eliminate the cause of the problem, and then re-execute the pdtrnqing command.
  3. Use a cluster software command (the monswap command for HA Monitor) to execute the planned system switchover.
  4. Use the pdls -d ha command or the corresponding cluster software command to confirm that the switchover target unit is active.
When the planned system switchover is complete, transaction queuing is automatically canceled, and the transactions that have been queued are executed. This method can only be used for planned system switchovers when the automatic reconnect facility is applied. Therefore, check whether this facility is applied. For details about the automatic reconnect facility, see the HiRDB Version 9 UAP Development Guide.
When this method is used for a planned system switchover, UAP transactions are queued and placed in waiting status after the pdtrnqing command is executed and until the planned system switchover is complete. This increases the response time. Therefore, check whether the following settings are appropriate:
[Figure] Client maximum wait time specified in the PDCWAITTIME operand of the client environment definition
[Figure] HiRDB client maximum wait time during server connection, specified in the PDCONNECTWAITTIME operand of the client environment definition
When the time specified by these operands has passed, UAP execution results in an error.

(2) Using method 2 to execute a planned system switchover

The planned system switchover procedure is as follows.

Procedure
  1. Use the pdstop command to terminate the running system HiRDB (or unit).
  2. Use a cluster software command (the monswap command for HA Monitor) to perform a planned system switchover. For details about planned system switchovers, see the documentation for the applicable cluster software product.
  • If the cluster software product being used is HA Monitor, and you specify HiRDB termination in the shell that you start with the termcommand operand in the server definition file, you can perform a planned system switchover by simply executing the monswap command. For examples of shell creation, see 26.2.5(2)(c) termcommand operand.
  • To perform a system switchover manually when the cluster software product being used is ClusterPerfect, stop the running system, and then start the standby system. When the system switchover occurs, the color of ClusterPerfect's ClusterPerfect system information window changes.