Removing a server while HiRDB is running

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]

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.

Notes

You cannot remove the system manager or dictionary server.
You cannot remove a front-end server if there would be no more front-end servers.
You cannot 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) Create updated HiRDB system definitions; (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 pdlogrm and pdstsrm commands to delete the FES3 and BES4 system files

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

(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) Create updated HiRDB system definitions

Use the procedure explained below to create HiRDB system definitions that reflect the change in the server configuration.

Procedure

Create a $PDDIR/conf/chgconf directory.
Copy the current HiRDB system definition files into the directory that you created in step 1.
Modify the HiRDB system definitions that are in the $PDDIR/conf/chgconf directory.

(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

(6) Use the pdlogrm and pdstsrm commands to delete the FES3 and BES4 system files

 
pdlogrm -d sys -s fes3 -f /sysarea/log01 -D          1
   :
pdlogrm -d spd -s fes3 -f /sysarea/sync01 -D         2
   :
pdstsrm -s fes3 -f /sysarea/ssts01 -D                3
   :

Explanation

Deletes the system log files for FES3 and BES4.
Deletes the synchronization point dump files for FES3 and BES4.
Deletes the server status files for FES3 and BES4.

Because these commands are executed in unit 3 rather than in unit 1 (system manager unit), the -D option must be specified in the pdloginit and pdstsinit commands.