Removing a unit while HiRDB is stopped

Nonstop Database, HiRDB Version 9 System Operation Guide

11.2.2 Removing a unit while HiRDB is stopped

Remove unit 3 from a HiRDB parallel server configuration. The following figure illustrates the procedure:

[Figure]

Notes

Do not remove a unit containing the system manager or dictionary server.
Do not remove a unit if there would be no more front-end servers.
Do not remove a unit 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 BES3; (2) Modify client environment definitions; (3) Use the pdstop command to stop HiRDB normally; (4) Use the pdlogrm and pdstsrm commands to delete the unit 3 system files; (5) Modify HiRDB system definitions; (6) Use the pdconfchk command to check the HiRDB system definitions; (7) Use the pdstart command to start HiRDB normally

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

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 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 and BES3.
Deletes the synchronization point dump files for FES3 and BES3.
Deletes the server status files for FES3 and BES3.
Deletes the unit status files for unit 3.

(5) Modify HiRDB system definitions

Create HiRDB system definitions that reflect the change in the unit configuration.

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

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