Nonstop Database, HiRDB Version 9 System Operation Guide

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

26.6.6 Notes on using the standby system switchover facility (monitor mode)

Organization of this subsection
(1) Limitations on execution of operation commands
(2) Note on changing a HiRDB system definition or the HiRDB configuration
(3) When HiRDB files created on a shared disk cannot be accessed
(4) Note on when the time used by the OS differs significantly between the primary system and the standby system

(1) Limitations on execution of operation commands

Note that the following limitations apply to executing an operation command in conjuction with the standby system switchover facility (monitor mode):

(2) Note on changing a HiRDB system definition or the HiRDB configuration

If you change a HiRDB system definition or the HiRDB configuration, do not use a cluster software command to terminate HiRDB. Instead, use the pdstop command to normally terminate HiRDB only, and then change the HiRDB system definition or reconfigure HiRDB. When you have finished, you can use the pdstart command to start HiRDB only.

(3) When HiRDB files created on a shared disk cannot be accessed

If HiRDB is stopped by the cluster software, it might not be possible to manipulate HiRDB files on the shared disk from either system. In this case, you must use an OS command to activate the shared disk.

(4) Note on when the time used by the OS differs significantly between the primary system and the standby system

If the time used by the OS differs significantly between the primary system machine and the standby system machine (that is, if the time delay on the standby system machine is greater than the time required to perform a system switchover), note that HiRDB will be affected in the same way as when an incorrect operation is performed in an attempt to move the time back.

For details about how to change the time used by the OS, see 9.12 Changing the time used by the OS.