Adding a server while HiRDB is stopped

Nonstop Database, HiRDB Version 9 System Operation Guide

11.4.2 Adding a server while HiRDB is stopped

Add a front-end server (FES3) and a back-end server (BES4) to unit 3. The following figure illustrates the procedure:

[Figure]

Organization of this subsection: (1) Check the memory requirements for unit 3; (2) Use the pdstop command to stop HiRDB normally; (3) Use the pdlogls command to check the status of the system log files in unit 3; (4) Use the pdlogunld command to unload any system log files in unload wait status; (5) Use pdlogrm and pdstsrm commands to delete the system files required for unit 3; (6) Modify HiRDB system definitions; (7) Use the pdloginit and pdstsinit commands to create the system files required for unit 3; (8) Use the pdconfchk command to check the HiRDB system definitions; (9) Use the pdstart command to start HiRDB normally; (10) Use the pdmod command to add or move RDAREAs; (11) Modify client environment definitions

(1) Check the memory requirements for unit 3

To add the servers, you must re-estimate the memory requirements for unit 3. You might also need to modify operating system parameters of the OS. For details about memory requirements and evaluating operating system parameters, see the HiRDB Version 9 Installation and Design Guide.

(2) Use the pdstop command to stop HiRDB normally

 
pdstop

Check that HiRDB terminates normally.

(3) Use the pdlogls command to check the status of the system log files in unit 3

 
pdlogls -d sys -s bes3

(4) Use the pdlogunld command to unload any system log files in unload wait status

 
pdlogunld -d sys -s bes3 -g log01 -o /unld/unldlog01

If you decide not to unload the system logs, use the pdcopy command to back up all RDAREAs. For details about making backups, see 6.4 Examples of backup.

(5) Use pdlogrm and pdstsrm commands to delete the system files required for unit 3

 
pdlogrm -d sys -s bes3 -f /sysarea/log01           1
   :
pdlogrm -d spd -s bes3 -f /sysarea/sync01          2
   :
pdstsrm -s bes3 -f /sysarea/ssts01                 3
   :
pdstsrm -u UNT3 -f /sysarea/usts01                 4
   :

Explanation

Deletes system log files for BES3.
Deletes synchronization point dump files for BES3.
Deletes server status files for BES3.
Deletes unit status files for unit 3.

(6) Modify HiRDB system definitions

Create HiRDB system definitions that reflect the changes in the server configuration. If you plan to add or move RDAREAs in step (10), also modify the global buffer definitions.

(7) 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, BES3, and BES4.
Creates synchronization point dump files for FES3, BES3, and BES4.
Creates server status files for FES3, BES3, and BES4.
Creates unit status files for unit 3.

Because you re-create the status files, the error shutdown status of RDAREAs is not inherited. If necessary, use the pdhold command to place RDAREAs in shutdown status again.

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

(9) Use the pdstart command to start HiRDB normally

 
pdstart

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

If necessary, you can add or move RDAREAs to BES4. 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).

(11) Modify client environment definitions

If necessary, specify the following operands in the client environment definitions 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.