Remove a front-end server (FES3) and a back-end server (BES3) from a HiRDB/Parallel Server. The procedure is detailed below.
For details about deleting RDAREAs, see 15.6 Deleting an RDAREA; for details about moving RDAREAs, see 15.8 Moving an RDAREA (RDAREA migration).
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:
pdstop |
Check that HiRDB terminates normally.
pdlogls -d sys -s bes3 |
pdlogunld -d sys -s bes3 -g log01 -o /unld/unldlog01 |
pdlogrm -d sys -s fes3 -f /sysarea/log01 1 |
Create HiRDB system definitions that reflect the changes in the server configuration.
If a back-end server for external server connection is deleted, delete definitions about the external server. If the unit is deleted without deleting the external server-related definitions, the configuration change may fail or an attempt to access a table or index stored in an RDAREA on the unit to be deleted will result in an error.
pdloginit -d sys -s bes3 -f /sysarea/log01 -n 5000 1 |
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.
pdconfchk |
If errors are detected, correct the HiRDB system definitions, and then execute the pdconfchk command again.
pdstart |
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.