Nonstop Database, HiRDB Version 9 System Operation Guide

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

11.1.1 Adding a unit while HiRDB is running

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]

Use of the system reconfiguration command (pdchgconf command) eliminates the need to terminate HiRDB normally. Note that HiRDB Advanced High Availability must be installed in order to use this command.

Organization of this subsection
(1) Deploy a new server machine
(2) Create updated HiRDB system definitions
(3) Use the pdloginit and pdstsinit commands to create the system files required for unit 3
(4) Use the pdconfchk command to check the updated HiRDB system definitions
(5) Use the pdchgconf command to modify the HiRDB system definitions
(6) Use the pdmod command to add or move RDAREAs
(7) 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:

(2) Create updated HiRDB system definitions

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

Procedure
  1. Create a $PDDIR/conf/chgconf directory.
  2. Copy the current HiRDB system definition files into the directory you created in step 1.
  3. Modify the HiRDB system definitions that are in the $PDDIR/conf/chgconf directory.
  4. Copy the HiRDB definition files in the $PDDIR/conf/chgconf directory to the $PDDIR/conf directory. Perform the operation in step 4 only for the server machine of the unit to be added.
    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.

(3) 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 -D         1
   :
pdloginit -d spd -s fes3 -f /sysarea/sync01 -n 5000 -D        2
   :
pdstsinit -s fes3 -f /sysarea/ssts01 -c 3000 -D               3
   :
pdstsinit -u UNT3 -f /sysarea/usts01 -c 3000 -D               4
   :
 

Explanation
  1. Creates system log files for FES3 and BES3.
  2. Creates synchronization point dump files for FES3 and BES3.
  3. Creates server status files for FES3 and BES3.
  4. Creates unit status files for unit 3.
Because these commands are executed in unit 3 rather than in unit 1 (system manager unit), the -D option must be specified for the pdloginit and pdstsinit commands.

(4) Use the pdconfchk command to check the updated HiRDB system definitions

 
pdconfchk -d chgconf
 

Check the HiRDB system definitions in the $PDDIR/conf/chgconf directory. If errors are detected, correct the HiRDB system definitions, and then execute the pdconfchk command again.

(5) Use the pdchgconf command to modify the HiRDB system definitions

 
pdchgconf
 

Replace the HiRDB system definitions with the updated HiRDB system definitions.

(6) 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).

If you did not modify the global buffer definitions in step (2), use the pdbufmod command to update the global buffers dynamically.

(7) Modify client environment definitions

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

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.