11.2.1 Removing a unit while HiRDB is running

Remove unit 3 from a HiRDB/Parallel Server. The procedure is detailed below.

[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 a unit that contains the system manager or dictionary server.
  • You cannot remove a unit if there would be no more front-end servers.
  • You cannot 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) 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 unit 3 system files

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

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

(2) Modify client environment definitions

Check if the following operands of 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:

(3) Create updated HiRDB system definitions

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

Procedure
  1. Create a $PDDIR/conf/chgconf directory.
  2. Copy the current HiRDB system definition files into the directory that you created in step 1.
  3. Modify the HiRDB system definitions that are in the $PDDIR/conf/chgconf directory.
If you are using the HiRDB External Data Access facility
If a back-end server for connecting to foreign servers is in the unit to be removed, delete the definitions related to foreign servers. If you remove the unit without deleting the foreign server-related definitions, either the configuration change will fail or an error will occur when an attempt is made to access a table or an index stored in an RDAREA of the unit that was removed.

(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 pdlogrm and pdstsrm commands to delete the unit 3 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
  :
pdstsrm -u UNT3 -f /sysarea/usts01  -D               4
  :

Explanation
  1. Deletes the system log files for FES3 and BES3.
  2. Deletes the synchronization point dump files for FES3 and BES3.
  3. Deletes the server status files for FES3 and BES3.
  4. Deletes the 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.

It is recommended that after the command has executed you check whether or not the execution results are correct. For details on how to check command execution results, see the manual HiRDB Version 8 Command Reference.