Removing a server while HiRDB is stopped

Nonstop Database, HiRDB Version 9 System Operation Guide

11.5.2 Removing a server while HiRDB is stopped

Remove a front-end server (FES3) and a back-end server (BES3) from a HiRDB parallel server configuration. The following figure illustrates the procedure:

[Figure]

Notes

Do not remove the system manager or dictionary server manager.
Do not remove a front-end server if there would be no more front-end servers.
Do not remove a back-end server if there would be no more back-end servers.

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

(1) Use the pdmod command to delete or move the RDAREAs of BES4

For details about deleting RDAREAs, see 15.7 Deleting an RDAREA; for details about moving RDAREAs, see 15.9 Moving an RDAREA (RDAREA migration).

(2) Modify client environment definitions

Check if the following operands in the client environment definitions are specified; if the front-end server (FES3) that you plan to remove is specified in these operands, change their values as appropriate:

PDFESHOST
PDSERVICEGRP
PDSERVICEPORT

(3) Use the pdstop command to stop HiRDB normally

 
pdstop

Check that HiRDB terminates normally.

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

 
pdlogls -d sys -s bes3

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

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

(6) Use the pdlogrm and pdstsrm commands to delete the unit 3 system files

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

Explanation

Deletes the system log files for FES3, BES3, and BES4.
Deletes the synchronization point dump files for FES3, BES3, and BES4.
Deletes the server status files for FES3, BES3, and BES4.
Deletes the unit status files for unit 3.

(7) Change the HiRDB system definition

Create HiRDB system definitions that reflect the changes in the server configuration.

(8) Use the pdloginit and pdstsinit commands to create the system files needed for unit 3

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

Explanation

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

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

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

(10) Use the pdstart command to start HiRDB normally

 
pdstart

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.