3.3.16 Operands related to the system switchover facility

49) pd_ha_acttype = monitor | server
Specifies whether to run the system switchover facility in the monitor mode or server mode. For details on the monitor and server modes, see the HiRDB Version 8 System Operation Guide.
monitor: The system switchover facility runs in the monitor mode.
server: The system switchover facility runs in the server mode.
If any of the following facilities is used, the server mode is used as the default.
  • User server hot standby
  • Rapid system switchover facility
  • Standby-less system switchover (1:1) facility
  • Standby-less system switchover (effects distributed) facility
Conditions
To specify this operand, you must specify use for the pd_ha operand, and N for the pd_ha_ipaddr_inherit operand. If you specify server, all of the following conditions must be satisfied:
  • Hitachi HA Toolkit Extension is installed.
  • It is specified that IP addresses are not inherited. (pd_ha_ipaddr_inherit = N is specified.)
If you specify server without installing these products, HiRDB cannot start.
50) pd_ha_unit = nouse
Specify this operand if the system switchover facility is not to be applied to the unit. Specify this operand when the facility is to be applied to only some of the units. Specifying this operand invalidates the specifications of all of the operands explained in this section.
Relationship to other operands
If the -k stls option is specified in the front-end server's pdstart operand, a recovery-unnecessary front-end server unit is assumed. The system switchover facility is not applicable to a recovery-unnecessary front-end server unit. For a system that employs the system switchover facility, make sure that you specify this operand in the unit control information definition for the recovery-unnecessary front-end server unit.
51) pd_ha_switch_timeout = Y | N
This operand can be specified when the server mode is used. Specification of this operand is invalid in the monitor mode.
This operand specifies whether to switch the system without waiting for internal termination processing of HiRDB when internal termination processing of HiRDB (or a unit for a HiRDB/Parallel Server) during system switchover has exceeded the server failure monitoring time. The server failure monitoring time referred to here is the time specified for the patrol operand of the Hitachi HA Toolkit Extension.
For details about the patrol operand of Hitachi HA Toolkit Extension, see the manual Hitachi HA Toolkit.
Y:
Switches the system without waiting for internal termination processing of HiRDB when internal termination processing of HiRDB during system switchover has exceeded the server failure monitoring time. In this case, system switchover is carried out by assuming that HiRDB has slowed down.
If you are using the standby-less system switchover (1:1) facility or the standby-less system switchover (effects distributed) facility, the specification for this operand is invalid during planned system switchover.
N:
Does not switch the system until internal termination processing of HiRDB during system switchover is terminated.
Advantage
If internal termination processing of HiRDB during system switchover takes a long time, because, for example, of a disk error, system switchover may be delayed as a result. If you specify Y (default value) for this operand, you can switch the system without waiting for internal termination processing of HiRDB, even when it is taking a long time.
Notes
  • If you specify Y for this operand when the patrol operand value is small, planned system switchover may turn into system switchover based on slow-down. This is because internal termination processing of HiRDB during planned system switchover exceeds the time specified by the patrol operand.
  • You need to be careful if restart is specified for the switchtype operand of the Hitachi HA Toolkit Extension. If pd_ha_switch_timeout=Y (default value) is specified, and if internal termination processing of HiRDB exceeds the server failure monitoring time, HiRDB is not started in the system in which the failure occurred. In this case, the system is immediately switched.
    For details about the switchtype operand of the Hitachi HA Toolkit Extension, see the manual Hitachi HA Toolkit.
52) pd_ha_server_process_standby = Y | N
Specifies whether to use user server hot standby. For details on user server hot standby, see the HiRDB Version 8 System Operation Guide.
Y: Uses user server hot standby.
N: Does not use user server hot standby.
Omit this operand if you use the standby-less system switchover (1:1) facility or standby-less system switchover (effects distributed) facility.
Condition
HiRDB must be in the server mode if you are to specify Y (default value) for this operand. If the monitor mode is in effect, N is always assumed.
Relationship to other operands
The rapid system switchover facility includes user server hot standby. Therefore, if standbyunit is specified (to use the rapid system switchover facility) for the pd_ha_agent operand, Y is assumed for the pd_ha_server_process_standby operand even if you specify N for it.
53) pd_ha_agent = standbyunit | server | activeunits
Specify this operand when you use the following facilities:
  • Rapid system switchover facility
  • Standby-less system switchover (1:1) facility
  • Standby-less system switchover (effects distributed) facility
For details about these facilities, see the HiRDB Version 8 System Operation Guide.
standbyunit: Specify this option when you use the rapid system switchover facility.
server: Specify this option when you use the standby-less system switchover (1:1) facility.
activeunits: Specify this option when you use the standby-less system switchover (effects distributed) facility.
Note that you cannot specify both the standby-less system switchover (1:1) facility and the standby-less system switchover (effects distributed) facility within the same system.
Condition
If you specify this operand, the server mode must be used. If the monitor mode is used, the error message KFPS01896-E is output.
Notes
  • A unit that is the target of the rapid system switchover facility cannot inherit IP addresses. Therefore, for a HiRDB/Single Server, specify N for the pd_ha_ipaddr_inherit operand in the system common definition or unit control information definition. If a configuration to inherit IP addresses is used for a HiRDB/Parallel Server, specify N for the pd_ha_ipaddr_inherit operand in the unit control information definition of the unit that is the target of the rapid system switchover facility.
  • When you use the rapid system switchover facility, standby-less system switchover (1:1) facility, or standby-less system switchover (effects distributed) facility, global buffers cannot be dynamically changed. For details about how to dynamically change global buffers, see the HiRDB Version 8 System Operation Guide.
Relationship to other operands
  • The rapid system switchover facility includes user server hot standby. Therefore, if you specify standbyunit for this operand, Y is assumed for the pd_ha_server_process_standby operand.
  • The standby-less system switchover (1:1) facility and the standby-less system switchover (effects distributed) facility use the server process of the unit at the switching destination following a system switchover. Consequently, if you specify server or activeunits for this operand, the specification of the pd_ha_server_process_standby operand becomes invalid.
  • When you use the rapid system switchover facility, standby-less system switchover (1:1) facility, or standby-less system switchover (effects distributed) facility, Y is assumed for the pd_rdarea_open_attribute_use operand (RDAREA opening trigger specification).
  • When you use the standby-less system switchover (effects distributed) facility, not all units within an HA group need to be active, and therefore the specification of the pd_start_skip_unit operand becomes invalid. However, all back-end servers within the HA group must be running at some units. Otherwise, HiRDB cannot start.
  • When you specify this operand, check the values specified for the following operands. If the specification values are wrong, the error message KFPS01896-E is output.
    Operand namepd_ha_agent operand value
    standbyunitserveractiveunits
    pd_hauseuseuse
    pd_ha_acttypeserverserverserver
    pd_ha_ipaddr_inherit (unit control information definition)N[Figure][Figure]
    pd_ha_agent[Figure]activeunits must not be specified for other units.server must not be specified for other units.
    -c option of the pdstart operand[Figure]Y[Figure]
    -g option of the pdstart operand[Figure][Figure]Y
    pdhagroup[Figure][Figure]Y
Legend:
Y: Operand must be specified.
[Figure]: Not applicable
54) pd_ha_max_act_guest_servers = maximum-number-of-acceptable-guest-BES
[Figure]<unsigned integer>((0-33))
Specify this operand when you use the standby-less system switchover (effects distributed) facility. This operand specifies the maximum number of guest back-end servers that operate as running systems inside the unit. When the number of guest back-end servers that are operating as running systems inside the unit reaches the value specified for this operand, the accepting state for guest back-end servers is cancelled.
The value of this operand determines the guest area to be allocated by the accepting unit. Adjust the resource requirement for back-end servers by changing the value of this operand.
If the value of this operand is too small, processing for some of the back-end servers may not take place when a system switchover occurs. When the number of back-end servers in an error state inside the HA group exceeds the total number of acceptable guest back-end servers inside the HA group, processing for the excess back-end servers is not accepted by any unit, and consequently, processing for these back-end servers does not occur.
Condition
When you specify this operand, you must also specify the following operands. If they are not specified, a system definition error occurs (message KFPS01896-E is output).
  • pdhagroup
  • pd_ha_agent = activeunits
Specification guidelines
If this operand is omitted, HiRDB calculates a value for this operand. The upper limit of the value that can be specified is the smaller of the following two values:
  • 34 - number-of-host-back-end-servers-inside-unit
  • number-of-servers-inside-HA-group - number-of-host-BESs-inside-unit
Even if you specify a value greater than the upper limit, it is corrected to the upper limit (message KFPS05613-W is output).
Note that the maximum number of acceptable guest back-end servers calculated by HiRDB when this operand is omitted assumes that all of the following conditions are satisfied:
  • All units inside the HA group have the same number of back-end servers.
  • A 2-point error has occurred.
Therefore, if all units inside the HA group do not have the same number of back-end servers, or if a 3-point error occurs, the default value of this operand may not allow the processing of some of the back-end servers.
Remarks
The following formula can be used to calculate the default value for this operand:
  • When the number of units inside the HA group is 2: a
  • When the number of units inside the HA group is 3 or larger: [Figure] (a[Figure] 2) [Figure] (b - 2) [Figure]
a: number-of-back-end-servers-inside-host
b: number-of-units-inside-HA-group
When you specify this operand, use the calculation formula (recommended value) shown below to determine the value to be specified for this operand. This calculation formula assumes that when a multi-point error occurs sequentially starting with the unit containing the largest number of units, except the local unit, the remaining units accept the host back-end servers from the failed unit evenly.
[Figure]
a: number-of-host-back-end servers-in-the-unit-ranked-i-th-in-number-of-host-back-end servers-excluding-local-unit
b: number-of-units-inside-HA-group
c: number-of-multi-point-errors-assumed (< b)
55) pd_ha_max_server_process = maximum-number-of-user-server-processes-inside-accepting-unit
[Figure]<unsigned integer>((1-10000)) <<total-value-of-the-pd_max_bes_process-operands-of-host-back-end-servers-inside-unit>>
Specify this operand when you use the standby-less system switchover (effects distributed) facility. Specify the maximum number of user server processes to be started inside a unit. In the accepting unit, the number of server processes is restricted by the value of the pd_max_bes_process operand (the maximum number of processes that can be started) for each host BES and guest BES. In addition, specifying this operand can restrict the total number of server processes inside the unit.
Condition
If you specify this operand, you must also specify the following operands. If they are not specified, the specification of the pd_ha_max_server_process operand becomes invalid.
  • pdhagroup
  • pd_ha_agent = activeunits
Specification guidelines
Omit this operand if you do not wish to increase the number of processes inside the unit following a system switchover. However, the upper limit of the number of service requests that can be concurrently processed may become restricted. If there is a sufficient amount of resources, specify the combined total value of the maximum number of processes that can be started (value of the pd_max_bes_process operand) in the host back-end servers inside the unit and the guest back-end servers that can be accepted. Then, the upper limit of the number of service requests that can be concurrently processed stays the same after a system switchover.
Specifying this operand can prevent an excessive load from being applied to the accepting unit. Determine the value to be specified for this operand by taking into account both the load increase on the unit and the number of service requests that can be concurrently processed following a system switchover.
Note
If the value specified for this operand is smaller than the combined total value of the pd_max_bes_process operand of the host back-end servers inside the unit, that specified value is invalid. In this case, the combined total value of the pd_max_bes_process operand of the host back-end servers inside the unit is assumed (message KFPS05614-W is output).
56) pd_ha_process_count = number-of-processes-resident-inside-unit-after-acceptance-of-guest-BES
[Figure]<unsigned integer>((0-10000))
Specify this operand when you use the standby-less system switchover (effects distributed) facility. Specify the combined total of the number of host back-end servers inside the unit and the number of resident processes for the guest back-end servers after these guest back-end servers have been accepted.
You can use the specification for this operand to adjust the number of resident processes in each server after guest back-end servers are accepted.
Condition
If you specify this operand, you must also specify the following operands. If they are not specified, the specification of the pd_ha_max_server_process operand becomes invalid.
  • pdhagroup
  • pd_ha_agent = activeunits
  • pd_process_count operand in the server common definition or back-end server definition
Specification guidelines
  • If you omit this operand, HiRDB calculates a value for this operand.
  • If some back-end servers cannot start a process, and service requests cannot be processed because a resident process not currently in service is occupying the process, decrease the value of this operand. However, transaction throughput may deteriorate following a system switchover. To improve the transaction throughput following a system switchover, increase the value of this operand. However, if the value of this operand is too large, some of the back-end servers may not be able to process service requests.
Note
If the value specified for this operand is smaller than the combined total value of the pd_process_count operand of the host back-end servers inside the unit, that specified value is invalid. In this case, the combined total value of the pd_process_count operand of the host back-end servers inside the unit is assumed (message KFPS05615-W is output).
Remarks
The number of processes resident in each back-end server after guest back-end servers are accepted is the smaller of the following two values:
  • Value obtained by proportionately distributing the value of this operand based on the value of the pd_process_count operand
  • Value of the pd_process_count operand of each back-end server

    [Figure]

The default value of this operand is the value obtained by multiplying the maximum number of user server processes that can be started after guest back-end servers are accepted by the ratio between the number of resident processes and the maximum number of user server processes that can be started before guest back-end servers are accepted. The calculation formula follows.
[Figure]
57) pd_ha_resource_act_wait_time = maximum-wait-time-for-resource-activation
[Figure]<unsigned integer>((2-3600)) (seconds)
When you use the standby-less system switchover (effects distributed) facility, this operand specifies the maximum wait time for the running server's resources to be activated at the time of unit startup. Unit startup processing is placed on hold up to the specified amount of wait time. If the resources are activated within the specified amount of time, unit startup processing resumes.
Advantages
When unit startup processing is completed, jobs can be started only if the running server's startup processing is completed in the unit. By specifying an appropriate value in this operand, you can start your jobs immediately after the unit's startup processing is completed because the unit startup processing will have waited on wait status for resource activation.
Specification guidelines
Normally, there is no need to specify this operand. You should specify this operand when all the following conditions are applicable:
  • The standby-less system switchover (effects distributed) facility is being used.
  • The KFPS05623-I message was displayed.
  • The target unit for the message contains the running server.
Use the following guideline to determine the value to be specified in this operand:
10 + time required for resource activation processing (seconds)
Remarks
If the unit does not contain the running server, the running server's startup is placed on hold for the amount of time specified in this operand. However, if all the servers in the unit start as standby servers, unit startup processing is restarted without waiting for the amount of time specified in this operand.
58) pd_ha_ipaddr_inherit = Y | N
This operand specifies whether to inherit IP addresses when using the rapid system switchover facility. Decide whether to specify this operand for a HiRDB/Parallel Server. How this facility is run differs depending on whether IP addresses are inherited. For details, see the HiRDB Version 8 System Operation Guide.
Y: Inherits IP addresses.
N: Does not inherit IP addresses.
In server mode operations, IP addresses cannot be inherited.
Specification guidelines
  • Omit this operand if you use the standby-less system switchover (1:1) facility or standby-less system switchover (effects distributed) facility. Even if this operand is specified, it is invalid.
  • If a configuration in which IP addresses are inherited is used for a HiRDB/Parallel Server, specify N (no IP address inheriting) only for the units that are the targets of the server mode.
    You cannot specify Y for this operand if you specify N for the pd_ha_ipaddr_inherit operand of the system common definition.