(a) HiRDB single server configuration

The following procedure explains how to start a server in a HiRDB single server configuration when you are using the system switchover facility.

Procedure

1. Use the pdstart command to start HiRDB on the running system.
2. Use the pdstart command to start HiRDB on the standby system. HiRDB enters standby status on the standby system.

(b) HiRDB parallel server configuration

Use the pdstart command to start HiRDB on the running system and the standby system.

Inheriting IP addresses

• Starting HiRDB on the running system
  If you start HiRDB on the running system without having allocated the IP address in advance, directly log onto the server machine of each unit and execute the pdstart -q command.
  If you allocate an IP address for each server machine and execute the pdstart command, you can start all units on the running system
  
• Starting HiRDB on the standby system
  Directly log onto a server machine that has standby system units and execute the pdstart -q command.
  

Not inheriting IP addresses

• Starting HiRDB on the running system
  Directly log onto a server machine that has running system units and execute the pdstart -q command. Another method is to execute the pdstart command to start all units on the running system.
  
• Starting HiRDB on the standby system
  Directly log onto a server machine that has standby system units and execute the pdstart -q command.
  

(c) Notes

Common notes

• When you execute the pdstart -q command, you must start all units within 20 minutes of the time the first unit starts. If all units cannot be started within 20 minutes, HiRDB startup processing terminates. Note that this value of 20 minutes for the startup time limit can be modified with the pd_reduced_check_time operand. The value 20 (minutes) is the default for this operand.
• The -i option, -r option, and dbdestroy option cannot be specified when the pdstart command is executed in the HiRDB on a standby system.
• Activate the shared resources before executing the pdstart -r or pdstart -R command. When the server mode system switchover facility based on HA Monitor is used, you can activate the shared resources simultaneously with HiRDB startup by executing the pdstart -r -t or pdstart -R -t command. The shared resources to be activated here are the shared disk, IP addresses, and other resources defined in the server definition file of HA Monitor.
• Terminate both the running system HiRDB and standby system HiRDB before you execute the pdstart -r or pdstart -R command. If HiRDB is started using the pdstart -r or pdstart -R command, HiRDB will not become a system switchover target. After a process such as database recovery processing terminates, terminate HiRDB, and then start it on the running system and standby system.

Notes on using the rapid system switchover facility

These notes apply only when you are using Hitachi HA Toolkit Extension. They do not apply if you are not using Hitachi HA Toolkit Extension.

After startup processing for the running system unit finishes, start the standby system unit that uses the rapid system switchover facility. If the standby system unit is started before the running system unit has started, the standby system unit waits for startup of the running system unit to finish. If the running system unit does not start within the waiting time limit, the standby system unit outputs abort code Phi1012 and terminates abnormally.

Notes on using MC/ServiceGuard

When you start HiRDB, the MC/ServiceGuard package must have started normally on the running system. Therefore, before starting HiRDB, confirm that the package has started. Use an MC/ServiceGuard command to confirm that the package has started or to start a package.

Notes on using Hitachi HA Toolkit Extension

After you start the service process for Hitachi HA Toolkit Extension, you must start the running system HiRDB. If HiRDB is started without activating the service process for Hitachi HA Toolkit Extension, both systems will start as standby systems. If this happens, perform the applicable procedure in the following table.

Table 26-34 Procedures to perform when HiRDB is started without activating the service process for Hitachi HA Toolkit Extension

Condition	Procedure
Unit to which user server hot standby is applied	Message KFPS01872-I, which indicates that both systems started as standby systems, is output. This message is output to both systems. The following procedure explains how to resolve this problem. Procedure Terminate both systems with Hitachi HA Toolkit Extension's standby system termination command. Activate the cluster software on the running system. Start the running system unit. Verify that startup of the running system unit is finished,# and then start the standby system unit.
Unit to which the rapid system switchover facility is applied	Message KFPS01854-E is output and the primary system unit terminates abnormally (abort code: Psadhfe). The secondary system unit waits for the primary system unit to start as the running system unit. The following explains how to resolve this problem. Starting the primary system as the running system Activate the cluster software on the primary system. Start the primary system unit as the running system unit. If the wait time is exceeded and the secondary system (standby system) terminates abnormally, verify that startup of the running system unit is finished,# and then start the standby system unit. Starting the secondary system as the running system Use the pdstop -z (pdstop -f for a HiRDB single server configuration) command to forcibly terminate the secondary system unit. Activate the service process for Hitachi HA Toolkit Extension on the secondary system. Start the secondary system unit as the running system unit. Verify that startup of the running system unit is finished,# and then start the standby system unit.

#

You can use the following methods to confirm that unit startup processing is complete:

• STATUS in the execution results of the pdls command displays ACTIVE.
• The KFPS05210-I or KFPS05110-I message is output.

Notes about using HA Monitor

Before you start the running system unit, use HA Monitor's monshow command to make sure that the standby system unit has stopped. The monshow command does not display any inactive system. If the command displays the status of the standby system, the standby system unit has not stopped.

An attempt to start the running system unit immediately after its termination might result in output of the KFPS01878-I and KFPS00715-E messages, because the standby system unit is still engaged in termination processing. If an attempt to start the running system unit has failed, perform the following procedure to start the unit:

1. Use HA Monitor's monshow command to make sure that the standby system unit has stopped.
2. Execute the pdrpause command to restart the process server process.
3. Use the pdstart command to start the running system unit.

The following table lists the methods for terminating HiRDB when the standby system switchover facility is used.

Table 26-35 Terminating HiRDB when the standby system switchover facility is used

Condition		Termination method
The cluster software product used is HA Monitor	Terminating both the running system and the standby system	Use the pdstop command to terminate the running system HiRDB. The standby system HiRDB will terminate together with the running system. This situation also applies during planned termination or forced termination. To terminate at the unit level, use the pdstop -u command to terminate the running system unit. The standby system unit will terminate together with the running system unit. This situation also applies when the pdstop -z command is executed.
	Terminating only the standby system	Use HA Monitor's monsbystp command to terminate only the standby system.
A cluster software product other than HA Monitor is used	Terminating both the running system and the standby system#	Use the pdstop command to terminate the running system HiRDB, and then use the hatesbystp command in Hitachi HA Toolkit Extension to terminate HiRDB. Executing the pdstop command does not terminate the standby system HiRDB. This situation also applies to planned termination or forced termination. To terminate at the unit level, use the pdstop -u command to terminate the running system unit, and then use the hatesbystp command in Hitachi HA Toolkit Extension to terminate the standby system unit. Executing the pdstop -u command does not terminate the standby system unit. This situation also applies when the pdstop -z command is executed.
	Terminating only the standby system	Use the hatesbystp command in Hitachi HA Toolkit Extension to terminate the standby system HiRDB.

#

• When you terminate the running system HiRDB (or unit), terminate the standby system HiRDB also.
• Terminate the standby system HiRDB before you restart the running system HiRDB (or unit).

(a) Unit and server operating statuses

The following table describes how to check the operating status of units and servers when a system switchover facility is used.

Table 26-36 Checking the operating status of units and servers when a system switchover facility is used

Command	Output information
pdls -d svr	Host name (the primary system host name is displayed after a system switchover) Unit operating status Server operating status

(b) Checking the system status

The following table describes how to check the system status when a system switchover facility is used.

Table 26-37 Checking the system status when a system switchover facility is used

Command	Output information
pdls -d ha	Host name and system status of the primary system (running, standby, or stopped) Host name and system status of the standby system (running, standby, or stopped) This command can check the host name and status of the standby system only when IP addresses are not inherited.#1
monshow#2 (only when HA Monitor is used)	Host name and status of the local system Host name and status of the other system
hateshow (only when Hitachi HA Toolkit Extension is used)	Status of the local system

#1

When IP addresses are inherited, use a command in the cluster software to check the system status. For details about the information displayed, see the documentation for the applicable cluster software product.

#2

For details about the statuses that can be displayed using the monshow command, see the HA Monitor manuals.

(c) Checking whether a command or utility can be executed

Execute the pdls -d svr command on the system manager unit of the primary system.

• If the termination status of the pdls -d svr command executed on the primary system is 0:
  Because the primary system is the running system, execute the command or utility on the primary system.
  
• If the termination status of the pdls -d svr command executed on the primary system is 8, or when the pdls -d svr command cannot be executed (for example, a remote shell cannot be executed and logon is not possible):
  The secondary system might be the running system. Execute the pdls -d svr command on the system manager unit of the secondary system to check whether the secondary system is the running system.
  
• When the termination status of the pdls -d svr command executed on the primary system or the secondary system is 4:
  Some units might be stopped, or HiRDB is being started or terminated. If units are stopped, start them. If units are stopped because of an error, check the message that was output to the syslogfile, correct the error, and then start the stopped units.
  If HiRDB is being started or terminated, execute the pdls -d svr command repeatedly at intervals of approximately 5 seconds until the termination status is no longer 4. Execute the pdls -d svr command repeatedly using the time specified in the pd_system_complete_wait_time operand as a guideline.
  

When the standby system switchover facility is used, the statistics log files are the two files pdstj1 and pdstj2. These files are created automatically for both the primary system and the secondary system, so the HiRDB administrator must prepare a total of four files. Statistics log files cannot be shared between the primary system and the secondary system.

(a) Creating unload statistics log files

Because statistics log files are distributed to each server machine when a system switchover occurs, you must create unload statistics log files on a specific server machine. We recommend that you create unload statistics log files at the following times:

• When HiRDB starts
• When statistics log files are swapped
• When a system switchover occurs

The following figure shows examples of unload statistics log files created when a system switchover facility is used (standby system switchover (server mode)).

Figure 26-93 Examples of unload statistics log files created when a system switchover facility is used (standby system switchover (server mode))

Hint

Make the names of the statistics log files the same on all server machines. Do not create unload statistics log files with the same names. Even if you are using the shell script provided by HiRDB (pdstjacm), modify the shell script so that each unload statistics log file has a different name.

(b) Process for collecting statistical information after a system switchover

The following operands specify whether statistical information is to be collected by the HiRDB on the switchover destination system after a system switchover occurs:

• pd_statistics
• pdstbegin

If Y is specified in the pd_statistics operand, or if the pdstbegin operand is specified, statistical information is collected immediately after a system switchover occurs.

If a system switchover occurs when the pdstbegin command is being used to start collecting statistical information, HiRDB on the switchover destination system cannot collect statistical information. To collect statistical information in this situation, you must use HiRDB on the switchover destination system to execute the pdstbegin command.

Also, HiRDB on the switchover destination system determines whether the pdstj1 or the pdstj2 statistics log file is used. The procedure for determining which statistics log file is used is the same as when the system switchover facility is not used.

(c) Executing the statistics analysis utility

The statistics analysis utility is executed using the created unload statistics log files as the input information. If a system switchover occurs due to an error, the statistics log information immediately prior to the system switchover is not acquired correctly in the file. For this reason, the execution results of the statistics analysis utility might not be accurate if they are used for tuning or other such activities.