To start HiRDB (all base units), excluding HiRDB expansion units, execute the pdstart command in the unit in which the system manager is located. When all base units have been started, the message KFPS05210-I is output. Therefore, confirm that this message has been output.

Notes on starting HiRDB

When HiRDB starts, which units start varies depending on the operation specified for the pdstart command and how the HiRDB expansion unit was previously terminated. The following table shows which units start when the pdstart command is executed, and the start processing completion point.

Before starting HiRDB, execute the pdls command to confirm that all units have been terminated, and then execute the pdstart command.

Table 29-1 Units that start when the pdstart command is executed and the start processing completion point (when a HiRDB expansion unit is used)

pdstart option	Previous termination status of the HiRDB expansion unit#1, #2	Units that start	HiRDB start processing completion point
pdstart (without option)	Normal termination	Base units	When all base units have started (the message KFPS05210-I is output)
	Planned termination Forced termination Abnormal termination	Base units and the HiRDB expansion unit that was started during the previous session	When all base units and the HiRDB expansion unit that was started during the previous session have started (the messages KFPS05210-I and KFPS05273-I are output)
pdstart -r	--	Base units#3	When all base units have started (the message KFPS05210-I is output)
pdstart -i#4, #5 pdstart dbdestroy#4		Base units

Legend: --: Not affected by the previous termination status of the HiRDB expansion unit

#1:

You can check how the HiRDB expansion unit terminated during the previous session based on whether the message KFPS05274-I has been output. If this message has been output, normal termination occurred. If not, planned termination, forced termination, or abnormal termination occurred.

#2:

The status file for the unit in which the system manager is located stores the termination status of the HiRDB expansion unit.Therefore, if HiRDB starts after re-creating the status file for the unit in which the system manager is located, only the base units start regardless of the termination status of the HiRDB expansion unit during the previous session.

#3:

The pdstart -r command does not start HiRDB expansion units. To back up the RDAREA of a HiRDB expansion unit or to recover the RDAREA, use the pdstart -u -r command to start that HiRDB expansion unit.

#4:

Before you execute the pdstart -i or pdstart dbdestroy command, confirm that all units have been terminated. If the pdstart -i or pdstart dbdestroy command is executed before all units have been terminated, HiRDB may not recognize the start of some of the units. Execute the pdls -d ust command at each unit, and if the unit is running, use the pdstop -z command to terminate it.

#5:

If the pdstart -i command is executed to initialize the database after a HiRDB expansion unit has been configured, perform the procedure given in 29.3.2 Configuring a HiRDB expansion unit beginning with step 3 (Create a HiRDB file system area) to reconfigure a HiRDB expansion unit. If you start the HiRDB expansion unit without first reconfiguring it, database initialization will not be reflected in the HiRDB expansion unit. Consequently, during creation of an RDAREA in the HiRDB expansion unit, a conflict is detected and an error occurs.