pdstart [{-i|-r|-l|dbdestroy}]
- Starting the HiRDB system
pdstart [{-i|-r|-l|dbdestroy}]
- Starting a unit
pdstart {-x host-name|-u unit-identifier}[{-r|-l|dbdestroy}]
- Starting a server
pdstart -s server-name
- Starting the system by resetting the front-end server from its SUSPENDed status
pdstart -a [-s front-end-server-name]
- Starting a unit from a unit
pdstart -q [{-r|-l}]
- Starting the alternate system when using the standby-less system switchover (1:1) facility (placing the alternate system in standby status)
pdstart -q -c
- Starting a server on the specified target unit when using the standby-less system switchover (effects distributed) facility
pdstart [{-x host-name|-u unit-identifier}] -s server-name
Specifies the startup mode for the HiRDB system. When this option is omitted, the HiRDB system performs normal startup if the previous termination was normal termination or performs a restart if the previous termination was forced or abnormal termination. In the case of a restart, database recovery processing is performed.
- -i
- If databases have been initialized by the database initialization utility (pdinit), specifies that the databases are to be reinitialized.
- -r
- Specifies that the master directory RDAREA is to be backed up by the database copy utility (-M x specified). Also specifies that if HiRDB will not start due to an error in the master directory RDAREA, the database recovery utility (pdrstr) is to be executed.
- -l:
- When Real Time SAN Replication based on the log-only synchronous method is used, specifies that HiRDB is to be started at the log application site.
- At the log application site, the system log information sent from the transaction execution site is input to keep the database up-to-date at the log application site. Therefore, the database cannot be accessed from the log application site.
- Rules
- When Real Time SAN Replication based on the log-only synchronous method is used, the command with the -l option specified can be executed from the log application site. If it is executed from the transaction execution site, an error results.
- When log application processing is executed with the -l option specified, the system switchover facility cannot be used. Even if HiRDB terminates abnormally due to a failure during log application processing, system switchover does not take place.
Also note that the pdstart command with the -l option specified cannot be executed at the secondary system. If it is executed, the KFPS05813-E message is displayed.
- When log application processing is executed with the -l option specified, neither reduced activation nor a recovery-unnecessary front-end server can be used. This is because the HiRDB at the log application site cannot be started when there are units that have not started.
- In the case of a HiRDB/Parallel Server with multiple units to which Real Time SAN Replication based on the log-only synchronous method is applied, the files for storing the site status are placed only in the unit containing the system manager. In other units, the site status is determined by instructions from the system manager unit.
Therefore, in the case of a HiRDB/Parallel Server to which Real Time SAN Replication based on the log-only synchronous method is applied, when you independently start a non-system manager unit as a transaction execution site, do not specify the -l option.
On the other hand, to start the unit independently as a log application site, make sure that you specify the -l option.
The following shows combinations of site status and pdstart command options when a non-system manager unit is started independently:
Site status | Unit to be started | pdstart command's option | Combination of options |
---|
-u or -x | -q | -l |
---|
Transaction execution | System manager | Y | N | N | Combinable |
Y | N | Y | Not combinable |
Other than system manager | N | Y | N | Combinable |
N | Y | Y | Not combinable |
Log application | System manager | Y | N | N | Not combinable |
Y | N | Y | Combinable |
Other than system manager | N | Y | N | Not combinable |
N | Y | Y | Combinable |
Legend:
Y: Specified
N: Omitted
- dbdestroy
- Specifies that HiRDB is to be restarted by forced restart because it would not restart. When HiRDB is restarted with this option specified, all RDAREAs (including system RDAREAs) are destroyed.
- {-x host-name|-u unit-identifier} [-r|-l|dbdestroy]
Specifies that a unit is to be started.
- -x host-name
<identifier> ((1-32)) - When a unit is to be started, specifies the name of the host containing the unit. This option cannot be specified together with the -i option.
- When the standby-less system switchover (effects distributed) facility is used, the command starts the host and guest BESs on the specified host's unit. The command starts the server specified as the running system by the cluster software as the running system and places the server specified as the standby system in acceptable status. The server started as the running system is in acceptable status when viewed from another unit in the HA group.
- -u unit-identifier
<identifier> ((4 characters)) - Specifies the identifier of the unit to be started. This option cannot be specified simultaneously with the -i option.
- When the standby-less system switchover (effects distributed) facility is used, the command starts the host and guest BESs on the specified unit.
- The command starts the server specified as the running system by the cluster software as the running system and places the server specified as the standby system in acceptable status. The server started as the running system is in acceptable status when viewed from another unit in the HA group.
- For details about -r, -l, and dbdestroy, see the description of {-i|-r|-l|dbdestroy}.
- -s server-name
<identifier> (1-8))
When a server is to be started, specifies the name of the server.
- Notes when the standby-less system switchover (effects distributed) facility is used:
- When the -u option is omitted, the command starts the specified servers on all active units in the HA group. Note that only the one server that was specified as the running system by the cluster software is started as the running system and that all other servers are started as being in acceptable status.
- When the -u option is specified, the command starts the specified servers on that unit. In this case, the command starts the server specified as the running system by the cluster software as the running system and the server specified as the standby system as being in acceptable status. When viewed from other units in the HA group, the server started as the running system is in acceptable status.
- For details about the standby-less system switchover (effects distributed) facility, see the HiRDB Version 8 System Operation Guide.
- -a [-s front-end-server-name]
Restarts a front-end server after resolving the cause of its SUSPEND status (waiting for the recovery of the data dictionary RDAREA or the starting of the dictionary server). Regardless of whether the -s option is specified, this option starts all the front-end servers in which an error occurred.
Specifies that the unit is to be started on a HiRDB/Parallel Server. When the standby-less system switchover facility is used, specify this option to start the standby unit.
When the -q option is specified, the host corresponding to the unit to be started (host with the -x or -c operand specified in the pdunit statement in the system common definition) is directly logged into and the command is executed.
If the -q option is specified, you must start all units before the pd_reduced_check_time operand value in the system definition is reached (when omitted, 20 minutes). If the command cannot start any of the units, HiRDB startup processing is cancelled.
For details about -r, and -l, see the description of {-i|-r|-l|dbdestroy}.
When the standby-less system switchover (1:1) facility is used, specifies that the alternate system is to be placed in standby status. Specify this option in the following cases:
- If planned switchover is executed using a cluster software command, the alternate system is stopped. In such a case, use the pdstart -q -c command to place the alternate system in standby status as a safeguard in the event of an error.
- The alternate system is stopped if you stop the normal BES unit with a command such as pdstop -u and restart the normal BES unit with the pdstart -q command after the alternate system of the corresponding alternate BES unit has stopped. In such a case, use the pdstart -q -c command to place the alternate system in the standby status as a safeguard in the event of an error.
To execute the pdstart -q -c command, directly log onto the host of the alternate system that is to be placed in standby status (host specified in -x of the pdunit operand in the system definition).