Nonstop Database, HiRDB Version 9 System Operation Guide

[Contents][Index][Back][Next]

15.10.1 Before moving HiRDB file system areas

Organization of this subsection
(1) HiRDB file system areas that can be moved
(2) Procedure
(3) Notes

(1) HiRDB file system areas that can be moved

Whether a HiRDB file system area can be moved depends on the type of RDAREAs stored in it. The following table shows the HiRDB file system areas that can be moved.

Table 15-6 HiRDB file system areas that can be moved

Type of RDAREA stored HiRDB operating status
Running Stopped
Master directory RDAREA N Y
Data dictionary RDAREA N Y
Data directory RDAREA N Y
Data dictionary LOB RDAREA N Y
User RDAREA Y Y
User LOB RDAREA Y Y
Registry RDAREA Y Y
Registry LOB RDAREA Y Y
List RDAREA Y Y

Legend:
Y: This type of HiRDB file system area can be moved.
N: This type of HiRDB file system area cannot be moved.

(2) Procedure

The procedure described below is applicable when HiRDB is running. If HiRDB is stopped, skip steps 1, 2, and 6.

Procedure
  1. Place all the RDAREAs stored in the HiRDB file system area to be moved in shutdown and closed status.
  2. Refresh the user server process to disconnect the HiRDB file system area to be moved from HiRDB's resident processes.
  3. Copy to the target disk the HiRDB file system area that constitutes the source RDAREAs. Make sure that the target HiRDB file system area name (full path name) does not exceed the permitted maximum length (for details, see pdfmkfs (initializes HiRDB file system areas) in the manual HiRDB Version 9 Command Reference). If the HiRDB file system area name exceeds the maximum length, the pdfstatfs command that is executed in step 4 with the target entity's path name specified will issue the KFPI21574-E message and terminate with an error.
  4. Delete the HiRDB file system area that constitutes the source RDAREAs.
  5. Create a symbolic link with the same name as for the source HiRDB file system area for the target HiRDB file system area.
  6. Release the RDAREA from their shutdown and closed status and place it in open status.

(3) Notes

  1. Make sure you correctly create, delete, and manage symbolic links (such as by checking the existence of and access rights to the target entities). If access from HiRDB to a target HiRDB file system area fails, the corresponding RDAREAs are shut down.
  2. To delete the entity of a symbolic link target (HiRDB file system area), specify the entity's path name. If a symbolic link is specified, the symbolic link, not the entity, is deleted.
  3. When you place an RDAREA for which a symbolic link was created on a different disk in order to move it, specify the path name of the entity as the source for copying in step 3 in (2) Procedure. If a symbolic link is specified, the symbolic link, not the entity, is copied.