Adding a unit while HiRDB is stopped

Nonstop Database, HiRDB Version 9 System Operation Guide

11.1.2 Adding a unit while HiRDB is stopped

Add unit 3 to a HiRDB parallel server configuration. The added unit contains a front-end server (FES3) and a back-end server (BES3). The following figure illustrates the procedure:

[Figure]

Organization of this subsection: (1) Deploy a new server machine; (2) Use the pdstop command to stop HiRDB normally; (3) Modify HiRDB system definitions; (4) Use the pdloginit and pdstsinit commands to create the system files required for unit 3; (5) Use the pdconfchk command to check the HiRDB system definitions; (6) Use the pdstart command to start HiRDB normally; (7) Use the pdmod command to add or move RDAREAs; (8) Modify client environment definitions

(1) Deploy a new server machine

Deploy a new server machine, and install and set up HiRDB. For details about installing and setting up HiRDB, see the HiRDB Version 9 Installation and Design Guide.

Check that the following are the same as in your existing units:

HiRDB version
Addressing mode (32-bit or 64-bit mode)
POSIX library version installed/not installed
Character codes
Installation status of optional program products and related products

(2) Use the pdstop command to stop HiRDB normally

 
pdstop

Check that HiRDB terminates normally.

(3) Modify HiRDB system definitions

Create HiRDB system definitions that reflect the change in the unit configuration. If you plan to add or move RDAREAs as explained in step (7), update the global buffer definitions as well.

Note: Do not change the pdstart operand value for a server in the existing units (units 1 and 2). If it is changed, you must take additional actions, such as initializing system files. For details about the actions to be taken when the pdstart operand value is changed, see the description of the pdstart operand in the manual HiRDB Version 9 System Definition.

(4) Use the pdloginit and pdstsinit commands to create the system files required for unit 3

 
pdloginit -d sys -s fes3 -f /sysarea/log01 -n 5000          1
   :
pdloginit -d spd -s fes3 -f /sysarea/sync01 -n 5000         2
   :
pdstsinit -s fes3 -f /sysarea/ssts01 -c 3000                3
   :
pdstsinit -u UNT3 -f /sysarea/usts01 -c 3000                4
   :

Explanation

Creates system log files for FES3 and BES3.
Creates synchronization point dump files for FES3 and BES3.
Creates server status files for FES3 and BES3.
Creates unit status files for unit 3.

(5) Use the pdconfchk command to check the HiRDB system definitions

 
pdconfchk

If errors are detected, correct the HiRDB system definitions, and then execute the pdconfchk command again.

(6) Use the pdstart command to start HiRDB normally

 
pdstart

(7) Use the pdmod command to add or move RDAREAs

If necessary, you can add or move RDAREAs to BES3. For details about adding RDAREAs, see 15.2 Creating an RDAREA (RDAREA addition); for details about moving RDAREAs, see 15.9 Moving an RDAREA (RDAREA migration).

(8) Modify client environment definitions

If necessary, specify the following client environment definition operands for the front-end server (FES3) that you added:

PDFESHOST
PDSERVICEGRP
PDSERVICEPORT

We recommend that after the command has executed you check whether the execution results are correct. For details on how to check command execution results, see the manual HiRDB Version 9 Command Reference.