2.2.46 Operands related to server structure

215) pdstart -t server-type[-s server-name]
-x host-name | -u unit-identifier
[-m host-name[,host-name]...
[-n host-name[,host-name]...]]
[-c server-name | -g HA-group-identifier]
[-k stls]
This operand must be specified; it cannot be omitted.
Notes
  • To change a server name that has been specified (with the -s option specification), you need to use the database initialization utility to reconstruct the system. Therefore, avoid server names that might have to be changed later.
  • To change the specification of the -t, -u, -s, or -c option, you need to perform the operations described below. Therefore, avoid specifications that might have to be changed later.
  1. Initialization of the system log file (The system log file of the server for which the option was changed must be initialized.)
  2. Initialization of the synchronization point dump file (The synchronization point dump file of the server for which the option was changed must be initialized.)
  3. Initialization of the status file for unit and the status file for server (The status files for the unit and server for which the options were changed must be initialized.)
Remarks
You can change the -x, -m, and -n option values when HiRDB is restarted following a planned termination. For the other options, change their values after HiRDB is started normally.
HiRDB single server configuration
The server configuration of a HiRDB single server configuration is defined. The following items can be specified:
  • Server type
  • Server name
  • Host name or unit identifier
Specification guidelines
  • If multiple HiRDB single server configurations are connected and used, a unique server name must be specified for each HiRDB single server configuration.
  • When utility special units are used, their server names must also be different from other server names.
  • The pdstart operand need not be specified for a utility special unit. However, the pdstart operand must be specified for all HiRDB single server configuration that use the utility special unit.
-t server-type
Specifies the server type:
SDS: Single server
-s server-name
~<identifier>((1-8 characters))
Specifies the server name of the single server.
-x host-name
~<host name>((1-32 characters))
Specifies the host name specified for the -x option of the pdunit operand.
If the pdunit operand is omitted, HiRDB assumes that the standard host name is specified in the -x option of the pdunit operand. Therefore, specify the standard host name in this option.
-u unit-identifier
~<identifier>((4 characters))
Specifies the identifier of the unit that executes the server. Specifies the unit identifier specified by the -u option of the pdunit operand.
When the system switchover facility is used, specification of -u unit-identifier instead of -x host-name is recommended.
-m host-name[,host-name]...
~<host name>((1-32 characters))
Specifies the host name of the HiRDB single server configuration to which the HiRDB client connects using the multi-connection address facility. You can also specify this value in the IP address or FQDN format.
For details about the multi-connection address facility, see the HiRDB Version 9 Installation and Design Guide.
Specify this option when the network being used between HiRDB clients and HiRDB servers is different from the network being used between the server machines of the HiRDB servers. If a loopback address is specified in the pd_hostname operand, this option must be specified in order to access the HiRDB server from another host's HiRDB client.
Caution about specifying in host name format
  • You cannot specify aliases for host names.
Notes
  • You can specify a maximum of four this option.
  • If you specify multiple host names that are on the same network, the first host name specified is valid.
  • If you specify the host name of a server machine not containing a HiRDB single server configuration, that specification is ignored.
  • If the network for connecting HiRDB clients is separated from the network for communicating between HiRDB servers by a subnet, the multi-connection address facility cannot be used. If the -m option is specified, the HiRDB client might not be able to connect to the HiRDB server.
  • The following shows how to specify -m and -n options.
    HiRDB single server configurationHow to specify the pdstart operand
    System switchover configurationConfiguration in which the IP address (the IP address to which HiRDB clients are connected) of the network to be used between HiRDB clients and the HiRDB server is inherited during a system switchoverSpecification of the -m optionSpecification of the -n option
    AppliedAppliedSpecify the host name corresponding to the IP address of the network to be used between HiRDB clients and the HiRDB server.Omit this option.
    Not appliedSpecify the host name of the primary system for the network to be used between HiRDB clients and the HiRDB server.Specify the host name of the secondary system for the network to be used between HiRDB clients and the HiRDB server.
    Not applied--Specify the host name of the network to be used between HiRDB clients and the HiRDB server.Omit this option.
    Legend:
    --: The configuration in which the IP address is inherited is not applied.

  • To apply the system switchover configuration, use the configuration in which the IP address of the network to be used between HiRDB clients and the HiRDB server is inherited even if the IP address of the network to be used between HiRDB clients and the HiRDB server is not inherited. If the IP address of the network to be used between HiRDB clients and the HiRDB server is not inherited, the UAP connection processing will be slower after a system switchover to the secondary host.
  • If the system switchover facility that inherits IP addresses is used and a loopback address is specified in the -x option of the pdunit operand, specify the host name with a relocatable IP address in the -m option.
-n host-name[,host-name]...
~<host name>((1-32 characters))
Specify this option together with the -m option.
Specifies the host name of the HiRDB single server configuration to which the HiRDB client connects using the multi-connection address facility. You can specify this value also in the IP address or FQDN format.
Specify this option when the network being used between HiRDB clients and HiRDB servers is different from the network being used between the server machines of the HiRDB servers. When you are using a system switchover facility that does not inherit IP addresses, specify the host name of the secondary system.
Caution about specifying in host name format
  • You cannot specify aliases for host names.
Notes
  • You can specify a maximum of four this option.
  • If you specify multiple host names that are on the same network, the first host name specified is valid.
  • If you specify the host name of a server machine not containing a HiRDB single server configuration, that specification is ignored.
  • If the network for connecting HiRDB clients is separated from the network for communicating between HiRDB servers by a subnet, the multi-connection address facility cannot be used. If the -n option is specified, the HiRDB client might not be able to connect to the HiRDB server.
  • For details on how to specify the -m and -n options, see the section about the -m option.
  • If you specify this option, specify the standard host name in the pd_hostname operand.
-c server-name
~<identifier>((1-8 characters))
Omit this option, because it is used only for a HiRDB parallel server configuration.
-g HA-group-identifier
~<identifier>((1-8 characters))
Omit this option because it applies only to a HiRDB parallel server configuration.
-k stls
~<identifier>((4 characters))
Omit this option because it applies only to a HiRDB parallel server configuration.
HiRDB parallel server configuration
The server configuration of a HiRDB parallel server configuration is defined. The following items can be specified:
  • Server type
  • Server name
  • Host name or unit identifier
Specification guidelines
The following guidelines are for the server configuration:
  • Concurrent execution of SQL statements can be improved if the individual servers are distributed among separate server machines.
  • Concurrent execution of SQL statements can be improved if the system manager and front-end servers are defined in server machines connected using the TCP/IP protocol.
  • In some cases, it might be better to allocate multiple back-end servers to a single server machine, depending on the CPU workloads of the back-end servers.
Note
Only one system manager server and one dictionary server can be specified.
-t server-type
Specifies the server type:
MGR: System manager
FES: Front-end server
BES: Back-end server
DIC: Dictionary server
-s server-name
~<identifier>((1-8 characters))
Specifies a server name. This option need not be specified if the server type is MGR (system manager).
-x host-name
~<host name>((1-32 characters))
Specifies the host name specified for the -x option of the pdunit operand.
-u unit-identifier
~<identifier>((4 characters))
Specifies the identifier of the unit that executes the server. Specifies the unit identifier specified by the -u option of the pdunit operand.
When the system switchover facility is used, specification of -u unit-identifier instead of -x host-name is recommended.
-m host-name[,host-name]...
~<host name>((1-32 characters))
Specifies the host name of the front-end server to which the HiRDB client connects using the multi-connection address facility. You can specify this value also in the IP address or FQDN format.
For details about the multi-connection address facility, see the HiRDB Version 9 Installation and Design Guide.
Specify this option when the network being used between HiRDB clients and HiRDB servers is different from the network being used between the server machines of the HiRDB servers.
Caution about specifying in host name format
  • You cannot specify aliases for host names.
Notes
  • You can specify a maximum of four this option.
  • If you specify multiple host names that are on the same network, the first host name specified is valid.
  • If you specify the host name of a server machine not containing a front-end server, that specification is ignored.
  • If the network for connecting HiRDB clients is separated from the network for communicating between HiRDB servers by a subnet, the multi-connection address facility cannot be used. If the -m option is specified, the HiRDB client might not be able to connect to the HiRDB server.
  • The following shows how to specify the -m and -n options.
    Configuration of units on which a front-end server is placedHow to specify the pdstart operand
    System switchover configurationConfiguration in which the IP address (the IP address to which HiRDB clients are connected) of the network to be used between HiRDB clients and the HiRDB server is inherited during a system switchoverSpecification of the -m optionSpecification of the -n option
    AppliedAppliedSpecify the host name corresponding to the IP address of the network to be used between HiRDB clients and the HiRDB server.Omit the specification of this option.
    Not appliedSpecify the host name of the primary system for the network to be used between HiRDB clients and the HiRDB server.Specify the host name of the secondary system for the network to be used between HiRDB clients and the HiRDB server.
    Not applied--Specify the host name of the network to be used between HiRDB clients and the HiRDB server.Omit this option.
    Legend:
    --: The configuration in which the IP address is inherited is not applied.

  • To apply the system switchover configuration, use the configuration in which the IP address of the network to be used between HiRDB clients and the HiRDB server is inherited even if the IP address of the network to be used between HiRDB clients and the HiRDB server is not inherited. If the IP address of the network to be used between HiRDB clients and the HiRDB server is not inherited, the UAP connection processing will be slower after a system switchover to the secondary host.
  • If the system switchover facility that inherits IP addresses is used and a loopback address is specified in the -x option of the pdunit operand, specify the host name with a relocatable IP address in the -m option.
-n host-name[,host-name]...
~<host name>((1-32 characters))
Specify this option together with the -m option.
Specifies the host name of the front-end server to which the HiRDB client connects using the multi-connection address facility. You can specify this value also in the IP address or FQDN format.
Specify this option when the network being used between HiRDB clients and HiRDB servers is different from the network being used between the server machines of the HiRDB servers. When you are using a system switchover facility that does not inherit IP addresses, specify the host name of the secondary system.
Caution about specifying in host name format
  • You cannot specify aliases for host names.
Notes
  • You can specify a maximum of four this option.
  • If you specify multiple host names that are on the same network, the first host name specified is valid.
  • If you specify the host name of a server machine not containing a front-end server, that specification is ignored.
  • If the network for connecting HiRDB clients is separated from the network for communicating between HiRDB servers by a subnet, the multi-connection address facility cannot be used. If the -n option is specified, the HiRDB client might not be able to connect to the HiRDB server.
  • For details on how to specify the -m and -n options, see the section about the -m option.
  • If you specify this option, specify the standard host name in the pd_hostname operand.
-c server-name
~<identifier>((1-8 characters))
This option is related to the standby-less system switchover (1:1) facility. Specify for this option the name of the alternate BES name of the back-end server specified by the -s option.
If you specify the -c option, all of the following conditions must be satisfied. Otherwise, HiRDB cannot be started. Here, it is assumed that the -u option is specified for the pdstart operand.
  1. BES must be specified for the -t option.
  2. The normal BES unit and the alternate BES unit must not contain any servers except back-end servers.
  3. Specify the alternate BESs for all of the back-end servers in the normal BES unit (the unit specified in the -u option). Additionally, you must specify those BESs in the same unit (alternate BES unit).
  4. You cannot specify duplicate server names in the -c option in the normal BES unit.
  5. The number of back-end servers in the normal BES unit must be the same as the number of back-end servers in the alternate BES unit.
  6. If you specify the -c option for the pdstart operand of the alternate BES, you must specify for this option the back-end servers inside the normal BES unit.
-g HA-group-identifier
~<identifier>((1-8 characters))
When you use the standby-less system switchover (effects distributed) facility, this option specifies an HA group identifier. The HA group identifier is a set of units that becomes the destination to which the server specified by the -s option is to be moved, and must be specified in the pdhagroup operand. For details about HA groups, see the HiRDB Version 9 System Operation Guide.
When you specify this option, all of the following conditions must be satisfied. Otherwise, HiRDB cannot start.
[Figure]Condition for the server to be specified in the -s option
  • BES is specified for the -t option. (A back-end server must be specified.)
  • The -c option is not specified. (An alternate back-end server cannot be specified for this server.)
[Figure]Condition for the unit to be specified in the -u option
  • The normal unit belongs to the HA group specified by the -g option.
  • The normal unit is comprised of back-end servers only.
  • An HA group is specified as the moving destination for the servers comprising the normal unit.
[Figure]Condition for the HA group to be specified in the -g option
  • All units within the HA group belong to the same network segment.
  • The standby-less system switchover (effects distributed) facility is being applied. (pd_ha_agent = activeunits is specified.)
  • At least one host back-end server exists inside the unit.
  • The unit is comprised of back-end servers only.
  • All servers within the unit belong to an HA group.
-k stls
~<identifier>((4 characters))
Specify this option when using a recovery-unnecessary front-end server. To use a recovery-unnecessary front-end server, you need the HiRDB Non Recover FES.
If any of the following conditions is satisfied, HiRDB cannot start.
  • Specification for this option contains an error.
  • The server specified for the -t option is not a front-end server.
  • This option is specified for a unit containing a server that is not a front-end server.
  • HiRDB Non Recover FES is not set up.
Notes
When Real Time SAN Replication based on the log-only synchronous method is used, the recovery-unnecessary front-end server cannot be used at the log application site. When the -k stls option is specified, the KFPS04689-W message is displayed.
Relationship to other operands
  • If you specify this option, re-estimate the value of the pd_log_max_data_size operand.
  • If this option is specified for a front-end server, that front-end server's unit in the pd_start_skip_unit operand is ignored, if specified.
  • The system switchover facility is not applicable to a recovery-unnecessary front-end server unit. If your system uses the system switchover facility, make sure that nouse is specified in the pd_ha_unit operand for the recovery-unnecessary front-end server unit.