2.2.3 Operands related to HiRDB startup

8) pd_mode_conf = AUTO | MANUAL1 | MANUAL2
Specifies the HiRDB startup method.
AUTO:
HiRDB is automatically started. The automatic startup method automatically starts HiRDB when the OS is started.
However, you must manually start HiRDB in the following cases. In the manual startup method, you must execute the pdstart command to start HiRDB.
  • Normal start following normal termination (without restarting the OS)
  • Restart following planned termination (without restarting the OS)
  • Restart following forced termination
MANUAL1:
HiRDB is manually started. However, after abnormal termination, HiRDB is automatically started.
MANUAL2:
Manual startup.
Specification guidelines
  • To restart HiRDB (or the unit) automatically after HiRDB (or the unit) has terminated abnormally, specify AUTO or MANUAL1.
  • If you use the system switchover facility, specify MANUAL1 or MANUAL2. Which of these modes is more appropriate depends on how the system switchover facility is used. For details about how to operate the system switchover facility, see the HiRDB Version 9 System Operation Guide.
  • The startup mode is determined by the combination of the previous termination mode (normal termination, forced termination, planned termination, or abnormal termination) and the startup method specified by this operand, as shown in the following table:
    pd_mode_conf specificationPrevious termination modeStartup modeStartup method
    AUTONormal terminationNormal startupAutomatic startup or Manual startup#1
    Planned terminationRestart#2
    Forced terminationRestart#2Manual startup
    Abnormal terminationRestartAutomatic startup
    MANUAL1Normal terminationNormal startupManual startup
    Planned terminationRestart#2
    Forced terminationRestart#2
    Abnormal terminationRestartAutomatic startup
    MANUAL2Normal terminationNormal startupManual startup
    Planned terminationRestart#2
    Forced terminationRestart#2
    Abnormal terminationRestart#2
    #1: Automatic startup is used only when the OS is started. For normal start following normal termination and restart following planned termination (without restarting the OS), manual startup is used.
    #2: The dbdestroy option of the pdstart command can be used for a forced startup. However, when forced startup is used, the HiRDB database is not recovered automatically and must be recovered by the HiRDB administrator.
  • If you use Real Time SAN Replication based on the log-only synchronous method, the startup mode is always set to normal startup regardless of the value of this operand or the previous termination mode. In the case of a log application site, the changeable system definition operands are only those that can be changed during restart.
Note
  • To use automatic startup (pd_mode_conf=AUTO) in a HiRDB parallel server configuration, try to start all units within 20 minutes after starting the first unit. If all units are not started within 20 minutes, the HiRDB startup process is cancelled. You can use the pd_reduced_check_time operand to change this 20-minute time limit.
    Note that this time limit does not apply when you are restarting a unit after it or the OS was abnormally terminated.
  • If you use Real Time SAN Replication, AUTO cannot be specified. If AUTO is specified, HiRDB startup processing results in an error.
  • If you use Real Time SAN Replication based on the log-only synchronous method, MANUAL2 is assumed even when MANUAL1 is specified in this operand at the log application site.
9) pd_system_complete_wait_time = pdstart-command-completion-wait-time
~<unsigned integer>((610-3600))<<610>> (seconds)
Specifies the amount of time to wait for completion of the pdstart command's processing. This operand needs to be specified only when it is necessary to provide a longer wait time than the default value of 610 seconds (10 minutes and 10 seconds). If startup processing is not completed within the specified number of seconds after the pdstart command was entered, HiRDB outputs the KFPS05078-I message and returns the pdstart command with an error.
Even though the pdstart command is returned with an error, startup processing continues and HiRDB is started. Therefore, specify this operand only in the following cases:
  • When the KFPS05078-I message is the monitoring target
  • When another operation is to be performed automatically after the pdstart command terminates normally
Application criterion
Normally, this operand need not be specified. This operand is applied when the KFPS05078-I message is output and the pdstart command is returned with an error during HiRDB startup processing.
10) pd_start_time_out = HiRDB-start-preparation-maximum-wait-time
~<unsigned integer>((1-1440))<<15>> (minutes)
Specifies the maximum amount of time to wait for completion of HiRDB start preparation after pdstart command input. If HiRDB start preparation is not completed within the time specified in this operand after pdstart command input, the KFPS01861-E message (reason code = TIMEOUT) is output in the pdstart command input window.
Specification guidelines
Normally, you need not specify this operand. In an ordinary environment, the HiRDB start preparation time is at most 3 to 6 minutes, and therefore the default value [15 minutes] of this operand is sufficient for the maximum wait time. In rare cases, HiRDB start preparation might take more than 15 minutes because of factors such as server machine performance, disk size, and memory load. In this case, the KFPS01861-E message (reason code = TIMEOUT) is output in the pdstart command input window. If this occurs, specify a value greater than 15 minutes for this operand.
Reference note
Based on the time at which the following message was output, you can compute the wait time for the completion of the HiRDB startup preparation process and the wait time for the completion of the HiRDB startup:
[Figure]
11) pd_term_watch_count = maximum-number-of-successive-abnormal-terminations
~<unsigned integer>((1-3))<<3>>
If HiRDB (or a unit in the case of a HiRDB parallel server configuration) restart processing fails, HiRDB terminates abnormally and attempts to retry the restart processing. This operand specifies the maximum number of times that abnormal termination can occur consecutively during HiRDB restart processing.
If the number of abnormal terminations (within 30 minutes) due to failed restart processing reaches this operand value, HiRDB outputs the KFPS00715-E message and stops retrying the restart processing. If this occurs, HiRDB is placed in PAUSE status. After HiRDB is placed in PAUSE status, HiRDB can no longer be restarted because the pdstart command cannot be executed.
You can use the pdls -d ust command to check whether HiRDB is in PAUSE status.
To release HiRDB from PAUSE status, eliminate the cause of the abnormal termination in accordance with the information provided for the KFPS00715-E message, and then execute the pdrpause command. For a HiRDB parallel server configuration, execute the pdrpause command on the unit that is in PAUSE status.
Specification guidelines
If 2 or 3 (default) is specified in this operand and HiRDB restart processing fails, HiRDB retries the restart processing. For example, if 3 is specified, HiRDB attempts the restart processing a maximum of three times (retries the restart processing a maximum of two times).
If 1 is specified in this operand and HiRDB restart processing fails, HiRDB does not retry the restart processing. If you do not want to retry the restart processing, specify 1.
Notes
If the system switchover facility is being used, the abnormal termination count is not inherited between the running system and the standby system.