For a HiRDB/Parallel Server, this function moves RDAREA to another server. The figure below provides an overview of moving RDAREAs.
Figure 7-8 Overview of moving RDAREAs
![[Figure]](figure/zu070210.gif)
- Prerequisites
- The RDAREAs to be moved must be in shutdown and closed status. A shared RDAREA must be in shutdown and closed status at all back-end servers.
- Before moving RDAREAs, use pdcopy to make a backup of the RDAREAs to be moved, master directory RDAREA, and data dictionary RDAREA.
- Before moving RDAREAs, you should check and, if necessary, revise the resource requirements for the target server.
- When an RDAREA is moved, an error results unless all its related RDAREAs are also moved. Related RDAREAs include the following:
- For a non-partitioned table, related RDAREAs are all RDAREAs that contain the table, indexes, and LOB data.
- For a row-partitioned table, related RDAREAs are all RDAREAs that contain the tables corresponding to the partitioning conditions, indexes, and LOB data.
If there is any non-partitioning key index (including a non-partitioning key index used for partitioning in a server), you must delete it. After you finish moving an RDAREA, re-create the non-partitioning key index. If UNIQUE is specified for the non-partitioning key index, you may not be able to re-create it. For details, see UNIQUE in CREATE INDEX in the manual HiRDB Version 9 SQL Reference.
If a primary key has been defined other than the non-partitioning keys, you must delete the target table after saving its data, re-define the table after moving the RDAREA, and then recover the data. Note that if a primary key has been defined other than the partitioning keys, you may not be able to re-define the table due to the unique index.
- A temporary table RDAREA cannot be moved. An error results if an attempt is made to do so. To move a temporary table RDAREA, first delete the RDAREA with the remove rdarea statement, and then use the create rdarea statement with the target server specified to re-create it.