Moving a unit while HiRDB is stopped

Move a unit of a HiRDB parallel server configuration. The following figure illustrates the procedure:

[Figure]

Note: Because moving the system manager unit has far-ranging effects, we recommend that you do not move the system manager unit.

Organization of this subsection: (1) Deploy a new server machine; (2) Use the pdrorg command to unload the table data on BES1, one RDAREA at a time; (3) Use the pdstop command to stop HiRDB normally; (4) Use the pdlogls command to check the status of the system log files in the source unit; (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 system files in the source unit; (7) Modify HiRDB system definitions; (8) Use the pdloginit and pdstsinit commands to create the system files needed for the target unit; (9) Use the pdconfchk command to check the HiRDB system definitions; (10) Use the pdstart command to start HiRDB normally; (11) Use the pdcopy command to back up all RDAREAs; (12) Use the pdmod command to re-initialize the RDAREAs in the target unit; (13) Use the pdrorg command to reload the table data in the target unit, one RDAREA at a time; (14) Use the pdcopy command to back up all RDAREAs; (15) Modify client environment definitions

(1) Deploy a new server machine

Deploy a new server machine, and install and set up HiRDB. For details about installing and setting up HiRDB, see the HiRDB Version 9 Installation and Design Guide.

Check that the following are the same as in your existing units:

HiRDB version
Addressing mode (32-bit or 64-bit mode)
POSIX library version installed/not installed
Character codes
Installation status of optional program products and related products

(2) Use the pdrorg command to unload the table data on BES1, one RDAREA at a time

For details about unloading table data on a per-RDAREA basis, see the manual HiRDB Version 9 Command Reference.

(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 the source unit

(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 system files in the source unit

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

Explanation

Deletes the system log files (for FES1 and BES1) in the source unit.
Deletes the synchronization point dump files (for FES1 and BES1) in the source unit.
Deletes the server status files (for FES1 and BES1) in the source unit.
Deletes the unit control files in the source unit.

(7) Modify HiRDB system definitions

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

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

Explanation

Creates system log files for FES1 and BES1.
Creates synchronization point dump files for FES1 and BES1.
Creates server status files for FES1 and BES1.
Creates unit status files for unit 1.

(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

(11) Use the pdcopy command to back up all RDAREAs

(12) Use the pdmod command to re-initialize the RDAREAs in the target unit

(13) Use the pdrorg command to reload the table data in the target unit, one RDAREA at a time

Use the unload data file that you created in step (2) as input data. For details about reloading on a per-RDAREA basis, see the manual HiRDB Version 9 Command Reference.

(14) Use the pdcopy command to back up all RDAREAs

(15) Modify client environment definitions

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

PDFESHOST
PDSERVICEGRP
PDSERVICEPORT

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.

11.3.2 Moving a unit while HiRDB is stopped