25.13.7 Notes on operations
(1) Limitations on execution of operation commands
- To execute an operation command during HiRDB termination processing, the HiRDBs on both systems must be engaged in termination processing (however, this requirement does not apply to the pdstart command).
- While HiRDB is running, no operation commands can be executed by the HiRDB on the standby system.
(2) Limitations on execution of operation commands when using the standby-less system switchover (effects distributed) facility
When the situation described below occurs in an environment in which a global buffer for OTHER is defined, you must not attempt to terminate the unit alone by executing the pdstop -u command from the unit where the system manager is defined. First, either execute the pdstop command from the unit where the system manager is defined to terminate HiRDB or use the system reconfiguration command (pdchgconf command) to allocate a global buffer to the RDAREA to be added, and then terminate the unit. For details about global buffers for OTHER, see 25.5.8 Definition of global buffers (standby-less system switchover (effects distributed) facility only).
- In a unit to which the standby-less system switchover (effects distributed) facility is applicable, the globalbuffer operand was omitted from the create rdarea statement of the database structure modification utility (pdmod) and an RDAREA with a page size larger than the size of the global buffer for OTHER has been added.
(3) 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 terminate HiRDB only normally, then change the HiRDB system definition or reconfigure HiRDB. When you are done, you can use the pdstart command to start HiRDB only.
(4) When HiRDB files created on a shared disk cannot be accessed
If HiRDB is stopped by the cluster software, it may 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.
(5) Notes on executing the pdsetup command (applicable to the server mode only)
You must be careful about executing the pdsetup -d command while terminating HiRDB forcibly or abnormally. Do not enter Y at the command's prompt; if you do enter Y, it may become impossible to start HiRDB subsequently.
(6) Note on using Hitachi HA Toolkit Extension
When using Hitachi HA Toolkit Extension, the standby system unit will not wait for the running system unit to start. If a command is issued to the running system unit before the standby system unit has started, an error may occur and the standby system unit may abort (Phi1012). Therefore, wait for startup of the running system unit to finish before starting the standby system unit. If the standby system unit is started without waiting for startup of the running system to finish, the standby system unit may abort (Phi1012).
(7) Notes on using HA monitor
The following points about using HA monitor should be noted:
- During startup of a server,1 if all systems, including the primary system (system for which online is specified in the init operand of HA monitor's servers definition), wait for the running system server to start,2 start the primary system3 as the running system by executing HA monitor's monact command.
- If a server is being activated in a unit to which the standby-less system switchover (effects distributed) facility is applicable, do not terminate that unit forcibly. If it is terminated forcibly, the next time a server is started on the primary system, this server may wait for the running system server to start.2 In this case, start the primary system3 as the running system by executing HA monitor's monact command.
- 1 For a unit to which the standby-less system switchover (1:1) facility is applicable, replace server with unit when you read this sentence.
- 2 Status in which *SBY* is displayed when the HA monitor's monshow command is executed.
- 3 If the secondary system (system for which standby is specified in the init operand of HA monitor's servers definition) server is started by the monact command as the running system, the messages listed below may be output repeatedly on the primary system until startup of the running system is completed. These messages cease to be output once startup of the running system is completed.
- KFPS05608-I
- KAMN305-E
- KAMN222-I
- The KAMN305-E and KAMN222-I messages are output by HA monitor.