Nonstop Database, HiRDB Version 9 System Operation Guide

[Contents][Index][Back][Next]

1.1.6 Checking for startup completion

A server in a HiRDB parallel server configuration cannot start if any of the units cannot be started.# This section explains how to check whether startup of HiRDB (or a unit) has been completed.

#: The situation is different when a HiRDB expansion unit is used. For details, see 29.4.1 Starting HiRDB.

Organization of this subsection
(1) Checking for HiRDB startup completion
(2) Checking for completion of startup of a unit

(1) Checking for HiRDB startup completion

(a) Checking the termination status of the pdls -d svr command

After you have executed the pdstart command, execute the pdls -d svr command from any unit and note its termination status. The following table shows the action to be taken by the HiRDB administrator based on the termination status of the pdls -d svr command.

Table 1-2 Termination status of the pdls -d svr command and required actions

Termination status of the pdls -d svr command Action to be taken by the HiRDB administrator
0 You can execute an application (SQL).
4 HiRDB startup might still be underway; execute the pdls -d svr command at approximately 5-second intervals until the termination status is no longer 4. Execute the pdls -d svr command over a period of time roughly equivalent to the value specified in the pd_system_complete_wait_time operand.
8 An error occurred during HiRDB startup. See the message that is output to syslogfile and remove the cause of the error; then restart HiRDB.
(b) Checking the termination status of the pdstart command

To start HiRDB from the unit in which the system manager is located, execute the pdstart command. If the termination status of the pdstart command is 0, you can execute an application (SQL).

If the termination status of the pdstart command is not 0, an error occurred during HiRDB startup. See the message that is output to syslogfile and remove the cause of the error; then restart HiRDB.

(2) Checking for completion of startup of a unit

After you have executed the pdstart -q command, execute the pdls -d ust command on the unit and note its termination status. The following table shows the action that must be taken by the HiRDB administrator based on the termination status reported by the pdls -d ust command.

Table 1-3 Termination status of the pdls -d ust command and required actions

Termination status of the pdls -d ust command Action to be taken by the HiRDB administrator
0 The unit is running. If the unit where the command was executed contains a front-end server, you can execute an application (SQL) for which this unit's front-end server is specified in the PDFESHOST and PDSERVICEGRP operands in the client environment definition.
1 An error occurred during command execution. Check the displayed message, eliminate the cause of the error, and then re-execute the command.
4 HiRDB startup might still be underway; execute the pdls -d ust command at approximately 5-second intervals until the termination status is no longer 4. Execute the pdls -d ust command over a period of time roughly equivalent to the value specified in the pd_system_complete_wait_time operand.
8 or 12 An error occurred during unit startup. See the message that is output to syslogfile and remove the cause of the error; then restart the unit.
16 The operation might be incorrect. First use the pdsetup command to register HiRDB in the OS, then restart the unit.