16.19.7 Preparing the DB directory

Prepare the DB directory by taking the steps described in the procedure below.

On the HADB server before migration, if regular files are being used for DB area files, other than work table DB area files, you need to change these files to block special files. For details about how to make these changes, see 16.10.4 Changing the storage location of DB areas.

1. Prepare a file system for the system directory.

   Prepare a file system to be used as the system directory. For details about the file system to be used as the system directory, see (2) File systems inherited at node switchover in 16.2.4 Storage configuration.

2. Prepare the file system that stores synonym dictionary files.

   For details about the file system that stores synonym dictionary files, see (2) File systems inherited at node switchover in 16.2.4 Storage configuration.

   This task is only required in environments that use synonym searches.

3. Prepare a disk for the work table DB area to be used by the added nodes.

   For each node, prepare a disk to be used as the work table DB area. For details about the disk to be used as the work table DB area, see (3) Disks for DB area files in 16.2.4 Storage configuration.

4. Execute the adbinit command on the added nodes.

   Create the DB directory by executing the adbinit command on the added nodes.

   Note the following points when doing so:

   • Specify N for the adb_init_dbarea_initialize operand in the initialization option, and create a framework only for the DB directory.

   • For the path of the block special file to be specified for the adb_init_wrk_blk_path operand in the initialization options, specify the disk to be used as the work table DB area, which you prepared in step 2.

   • For the path of the block special file to be specified for the adb_init_mst_blk_path, adb_init_dic_blk_path, and adb_init_stbl_blk_path operands in the initialization option and for the adbinitdbarea option, specify the path of the block special file of the DB area file that was being used by the HADB server before migration.

To Page Top