Depending on the operations listed in the table below, you might need to restart the alternate portion. If you do not restart the alternate portion in these cases, it will terminate abnormally when a system switchover occurs.

Table 26-50 Operations in which the alternate BES unit or alternate portion must be restarted

Classification	Operation		A running system server restarted after independently terminating normally?	Is it necessary to restart the alternate BES unit (alternate portion)?
SQL execution	Execution of a definition SQL statement		No	N
			Yes	Y
	Definition of the first abstract data type after HiRDB system construction (CREATE TYPE statement execution)		No	Y
			Yes	Y
Operation command or utility execution	Database structure modification utility (pdmod) execution	Registration of HiRDB file system area generation	No	N
			Yes	N
		Deletion of HiRDB file system area generation	No	N
			Yes	N
		Auditor registration	No	N
			Yes	N
		Re-initialization of RDAREA without the with reconstruction operand specified	No	Y
			Yes	Y
		RDAREA attribute modification	No	Y
			Yes	Y
		Audit trail table creation	No	N
			Yes	Y
		Other operations	No	Y
			Yes	Y
	Execution of the pddbchg command		No	N
			Yes	Y
	Execution of online reorganization (execution of the pdorbegin or pdorend command)		No	N
			Yes	Y
	First execution of the pdplgrgst command after HiRDB system construction (CREATE TYPE statement execution)		No	Y
			Yes	Y
System common definition modification	Modification of one of the following definitions: Global buffer definition (pdbuffer) Maximum RDAREA count (pd_max_rdarea_no) Maximum number of HiRDB files comprising an RDAREA (pd_max_file_no) Maximum inner replica group count (pd_inner_replica_control) Minimum guaranteed value for table reservation count (pd_assurance_table_no) Minimum guaranteed value for index reservation (pd_assurance_index_no)		No	N
			Yes	Y

Legend:

Y: The alternate portion must be restarted.

N: The alternate portion need not be restarted.

If the alternate portion terminates abnormally, use the pdstart -q -c command to restart it.

When performing an operation listed above, terminate the normal BES unit, and then restart it. If you do not restart the normal BES unit, it will terminate abnormally when a system switchover (or a system switchback) occurs. If a normal BES unit terminates abnormally, use the pdstart -q command or pdstart -u command to start it.

To minimize the time required to perform a system switchover, the standby-less system switchover (1:1) facility opens only the RDAREAs needed for full recovery when a system switchover occurs. It does not open other RDAREAs. The RDAREA opening trigger attributes in the normal BES unit are as follows:

• When a system switchover occurs, the system can be reactivated only after all processes in the alternate portion have terminated. Therefore, the RDAREA opening trigger attribute of the alternate portion is SCHEDULE.
• After recovering from an error and switching the system back to the normal BES unit, the RDAREA opening trigger attribute of the INITIAL or DEFER attribute on the normal BES unit is the DEFER attribute. RDAREAs with the SCHEDULE attribute remain unchanged.

For details about RDAREA opening trigger attributes, see 15.6 Modifying an RDAREA opening trigger attribute (RDAREA modification).

• 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).
• No operation command can be executed by the HiRDB on the standby system while HiRDB is running.

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 are done, you can use the pdstart command to start HiRDB only.

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.

If you are 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 might occur and the standby system unit might 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 might abort (Phi1012).

• If the front-end server unit specified in the PDFESHOST operand is switching over, UAPs cannot connect to HiRDB (CONNECT).
• There is an interval between the time the HiRDB service starts and the time that HiRDB is ready to begin receiving transactions. If there is a connection attempt during this period, a connection error will result. Use the pdls command to check the HiRDB status, and then reconnect.
• When a system switchover occurs, the client connections terminate and the database returns to its status before the transactions began. If necessary, re-execute the processing.

You must be careful about executing the pdsetup -d command when HiRDB is forcibly or abnormally terminated. Do not enter Y at the command's prompt. If you do enter Y, it might become impossible to start HiRDB subsequently.

Note the following points about using HA Monitor:

• 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 system^#3 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.

#2

Status in which *SBY* is displayed when 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 might be output repeatedly on the primary system until startup of the running system is complete. These messages cease to be output once startup of the running system is complete.

• KFPS05608-I
• KAMN305-E
• KAMN222-I

The KAMN305-E and KAMN222-I messages are output by HA Monitor.

If the time used by the OS differs significantly between the primary system machine and the standby system machine (the time delay on the standby system machine is greater than the time required to perform a system switchover), note the following: HiRDB will be affected in the same way as when an incorrect operation is performed for moving 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.