(a) Standby-less system switchover (1:1) facility

The following table describes the commands to execute when starting HiRDB.

Table 26-44 Commands to execute when starting HiRDB (when using the standby-less system switchover (1:1) facility)

Objective	Command to execute	Remarks
Starting the normal BES unit	pdstart -q	If this command is executed when a normal BES unit has stopped when units are being alternated, the normal BES unit is placed in standby status.#1
Starting the alternate BES unit	pdstart -q	The alternate portion in the alternate BES unit is also started. The alternate portion is placed in waiting status if it was in normal status.#2
Starting the alternate portion	pdstart -q -c	Not necessary because HiRDB starts automatically. The command needs to be executed only when the alternate portion is stopped or is to be reactivated.

Note

Startup cannot be performed at the server level.

#1

The system will only be switched back to the normal BES unit if the normal BES unit is in standby status (that is, it will not be switched back to normal status from alternating status). If the normal BES unit is in standby status, the system status is displayed as SBY in the execution results of the pdls -d ha command.

#2

System switching only occurs when the alternating portion is in standby status. If the alternate BES unit is in standby status, the system status is displayed as SBY in the execution results of the pdls -d ha command.

(b) Notes

Common notes

• When you execute the pdstart -q command, you must start all units within 20 minutes from 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 of 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 executing 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 standby-less system switchover (1:1) 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 starting either the normal BES unit or the alternate BES unit, start the other idle unit within 20 minutes. If the standby system unit starts before the running system unit starts, 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.

During normal operation, the normal BES unit becomes the running system and the alternate portion becomes the standby system. When units are being alternated, the alternate portion becomes the running system and the normal BES unit becomes the standby system.

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.
• When the running system unit has stopped (including when the unit terminates abnormally), MC/ServiceGuard might recognize that node as one that cannot be switched during a system switchover. In such a case, that node cannot be switched even if HiRDB is waiting. Use an MC/ServiceGuard command to place that node in system switchable status.

Notes on using Hitachi HA Toolkit Extension

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 procedure in the following table.

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

Condition

Procedure

Unit to which the standby-less system switchover (1:1) facility is applied

Message KFPS01854-E is output and the normal BES unit terminates abnormally (abort code: Psadhfe). The alternate portion waits for the normal BES unit to start. The following procedure explains how to resolve this problem. Procedure Activate the service process for Hitachi HA Toolkit Extension on the normal BES unit. Start the normal BES unit. If the wait time is exceeded and the alternate portion is released from standby status, verify that startup of the normal BES unit is finished,# and then place the alternate portion on standby status.

#

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 on 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.

(a) Standby-less system switchover (1:1) facility

The following table describes how to terminate HiRDB when the standby-less system switchover (1:1) facility is used.

Table 26-46 Terminating HiRDB when the standby-less system switchover (1:1) facility is used

Objective		Command to execute	Remarks (effect on other unit or alternate portion)
Terminating HiRDB		pdstop	No specific operation needs to be performed on the alternate BES. Operation does not change even when alternating units.
Terminating the normal BES unit		pdstop -u	The alternate portion is released from standby status.#1
Terminating the alternate BES unit	Normal operation	pdstop -u	The alternate portion in the alternate BES unit is released from standby status.#1
	Alternating		The alternate portion in the alternate BES unit also stops. Also, when the normal BES unit is in standby status,#2 the standby status of the alternate BES unit is released.
Terminating the alternate portion while alternating units		pdstop -u	Specifies the unit identifier of the normal BES unit as the unit identifier.
Releasing standby status of the alternate portion		hatesbystp#3	None.
Releasing standby status of the normal BES unit		hatesbystp#4

Note

Termination at the server level is not possible.

#1

The system is switched to the alternate BES unit only if the alternate portion is in standby status. If the alternate portion is in standby status, the system status is displayed as SBY in the execution results of the pdls -d ha command.

#2

The system will be switched back to the normal BES unit only if the normal BES unit is in standby status (that is, it will not be switched back to normal status from alternating status). If the normal BES unit is in standby status, the system status is displayed as SBY in the execution results of the pdls -d ha command.

#3

Use HA Monitor's monsbystp command or Hitachi HA Toolkit Extension's hatesbystp command to release the alternate portion from standby status. Specify in the hatesbystp command the alias of the normal BES unit that corresponds to the alternate portion to be released from standby status.

#4

Use HA Monitor's monsbystp command or Hitachi HA Toolkit Extension's hatesbystp command to release the normal BES unit from standby status. Specify in the hatesbystp command the unit identifier of the normal BES unit to be released from standby status.

The following figures show examples of terminating alternate and normal BES units.

Example 1: Terminating a normal BES unit (normal operation, one-way alternating configuration)

Explanation

• Use the pdstop -u command to stop the normal BES unit (UNT1). When you stop the normal BES unit (UNT1), the alternate portion of BES1 of the alternate BES unit (UNT2) also stops automatically. To stop only the alternate portion of BES1 without stopping the normal BES unit (UNT1), execute hatesbystp UNT1.

To start the normal BES unit (UNT1) that has stopped:

1. Use the pdstart -q command to start the normal BES unit (UNT1).
2. Use the pdstart -q -c command to place the alternate portion of BES1 in standby status.

Example 2: Terminating an alternate BES unit (normal operation, one-way alternating configuration)

Explanation

• Use the pdstop -u command to stop the alternate BES unit (UNT2).

To start the alternate BES unit (UNT2) that has stopped:

1. Use the pdstart -q command to start the alternate BES unit (UNT2). The alternate portion of BES1 is also placed in standby status.

Example 3: Terminating a unit (normal operation, mutual alternating configuration)

Explanation

• Use the pdstop -u command to stop the normal BES unit (UNT1). When you stop the normal BES unit (UNT1), the alternate portion of BES2 and the alternate portion of BES1 of the alternate BES unit (UNT2) also stop automatically. To stop only the alternate portion of BES1 without stopping the normal BES unit (UNT1), execute hatesbystp UNT1.

To start a unit (UNT1) that has stopped:

1. Use the pdstart -q command to start the unit (UNT1). The alternate portion of BES2 is also placed in standby status.
2. Use the pdstart -q -c command to place the alternate portion of BES1 in standby status.

Example 4: Terminating an alternate BES unit (alternating, one-way alternating configuration)

Explanation

• Use the pdstop -u command to stop the alternate BES unit (UNT2).

To return to normal status:

1. Reactivate the package for BES1. This step is necessary only if you are using Hitachi HA Toolkit Extension.
2. Use the pdstart -q command to start the alternate BES unit (UNT2).
3. Use the pdstart -q command to start the normal BES unit (UNT1).

Example 5: Terminating an alternate BES unit (alternating, mutual alternating configuration)

#: The alternate portion of BES2 is inactive.

Explanation

• Use the pdstop -u command to stop the alternate BES unit (UNT2). When you stop the alternate BES unit (UNT2), the alternate portion of BES1 stops automatically. Furthermore, if the normal BES unit (UNT1) is in standby status, the standby status is automatically released.

To return to normal status:

1. Reactivate the package for BES1. This step is necessary only if you are using Hitachi HA Toolkit Extension.
2. Use the pdstart -q command to start the unit (UNT2).
3. Use the pdstart -q command to start the unit (UNT1).

Example 6: Terminating the alternate portion (alternating, one-way alternating configuration)

Explanation

• Use the hatesbystp command to stop the unit (UNT1).
• Use the pdstop -u command to stop the unit (UNT2).

To return to normal status:

1. Reactivate the package for BES1. This step is necessary only if you are using Hitachi HA Toolkit Extension.
2. Use the pdstart -q command to start the unit (UNT1).

Example 7: Releasing the alternate portion from standby status (normal processing, mutual alternating configuration)

Explanation

• Use the hatesbystp command to release the alternate portion of BES2 from standby status.

To place the alternate portion of BES2, which is stopped, in waiting status:

1. Use the pdstart -q -c command to place the alternate portion of BES2 in standby status.

Example 8: Stopping a unit in standby status (alternating, mutual alternating configuration)

#: The alternate portion of BES2 is inactive.

Explanation

• Use the hatesbystp command to stop the unit (UNT1).

To place a stopped unit (UNT1) in waiting status:

1. Use the pdstart -q command to place the unit (UNT1) in standby status.

(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-47 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 (host name of the normal BES) is displayed after a system switchover) Unit operating status (the unit identifier of the normal BES is displayed after a system switchover) 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-48 Checking the system status when a system switchover facility is used

Command	Output information
pdls -d ha	Host name and status of the normal BES unit (running/standby/stopped) Host name and status of the alternate BES unit (running/standby/stopped)
monshow (only when HA Monitor is used)	Host name and status of the local system#1 Host name and status of the other system#2
hateshow (only when Hitachi HA Toolkit Extension is used)	Status of the local system#3

#1: Statuses are displayed for the following categories:

Executing, on standby, starting as a running server, starting as a standby server, stopping as a running server, stopping as a standby server, waiting for restart as a running server, waiting for restart as a standby server, waiting for server system switchover, waiting for linked server system switchover

#2: Statuses are displayed for the following categories:

Executing, on standby, starting as a running server, starting as a standby server, stopping as a running server, stopping as a standby server, waiting for restart as a running server

#3: Statuses are displayed for the following categories:

Running server startup completed, standby server startup completed, running server starting, standby server starting, running server stopping, standby server stopping, running server waiting for restart wait, server not started

(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.

• When 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.
  
• When 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-less system switchover (1:1) facility is used, the statistics log files are the two files pdstj1 and pdstj2. These files are created as a set for the primary HiRDB system. Because the alternate BES unit's statistics log files are shared at the switching destination, no files are created for the secondary system. The HiRDB administrator must prepare files for the normal BES unit and for the alternate BES unit.

(a) Creating unload statistics log files

When a system switchover occurs, the statistics log files to be used by the switching-destination host are the files being used by the accepting unit at the switching destination. Because statistics log output destination files are distributed to each host, 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 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-less system switchover (1:1)).

Figure 26-97 Examples of unload statistics log files created when a system switchover facility is used (standby-less system switchover (1:1))

Hint

Because statistics log files have identical names on all server machines, do not use the same names when you create the unload statistics log files. 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.

When a system switchover occurs, statistics log files are handled by the switching-destination host.

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

This subsection explains the process for collecting statistical information on units in alternating status. The collection status of statistical information on the alternate BES unit determines whether collection of statistical information is necessary on a normal BES unit in alternating status. The same types of statistical information are collected on the normal BES unit and on the alternate BES unit. The following figure shows the process of collecting statistical information on units in alternating status.

Figure 26-98 Process of collecting statistical information on units in alternating status

Explanation

The following explains the process of collecting statistical information for BES1 and BES2 when they are in alternating status:

• BES1: Collects the same buf and dfw as the alternate BES unit (BES3).
• BES2: Collects the same sys as the alternate BES unit (BES4).

The process for BES3 and BES4 is the same.

In addition to the statistical information for BES3 and BES4, the statistical information for BES1 and BES2 is output to the statistics log file in the alternate BES unit (UNT2).

Remarks

The collection status of statistical information for a normal BES unit and an alternate BES unit in alternating status and the types of statistical information collected are the same. Figure 26-98 Process of collecting statistical information on units in alternating status is used as an example in the following explanations:

• When the pdstend command stops collecting statistical information for BES3, the statistical information for BES1 can no longer be collected. Similarly, when the pdstend command stops collecting statistical information for BES1, the statistical information for BES3 can no longer be collected.
• When the pdstbegin or pdstend command changes the types of statistical information collected for BES3, the types of statistical information for BES1 are also changed. Similarly, when the pdstbegin or pdstend command changes the types of statistical information collected for BES3, the types of collected information acquired for BES3 are also changed.

When a system is being switched back

When a system is being switched back (returning from alternating status to normal status), the following operands specify whether statistical information of the normal BES unit is to be collected and the types of statistical information to collect:

• pd_statistics
• pdstbegin

Therefore, you must execute the pdstbegin command again when you want to change whether to acquire statistical information, or when you want to change the types of information to be collected.

(c) Executing the statistics analysis utility

The statistics analysis utility is executed using the unload statistics log files created at the normal BES unit and the alternate BES unit as the input information. To manually copy the files that existed prior to a system switchover you must use, for example, an OS command. The statistics information on the server that was switched is processed as information on a server belonging to the alternate BES unit.

If a system switchover occurs because of 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.