3.4 Rules and notes

Organization of this section
(1) Rules
(2) Notes

(1) Rules

  1. The database initialization utility can be executed only while HiRDB is in end-of-initialization wait status (waiting after issuing the KFPS05201-Q message). HiRDB is placed in end-of-initialization wait status when no master directory RDAREA has been initialized or when HiRDB is started by the pdstart command with the -i option specified.
  2. The database initialization utility must be executed at the server machine that contains the single server or the server machine where the system manager is located.
  3. If an error occurs while the database initialization utility is executing, processing is cancelled immediately. The error must be corrected on the basis of the error messages output to the standard error output and to the message log file and then the database initialization utility must be re-executed.
  4. If the database initialization utility is terminated abnormally (aborted or placed in process shutdown status), the initialization status file (pdinit) may remain in $PDDIR/spool. This file must be deleted before the database initialization utility is re-executed.
  5. If the standby-less system switchover (1:1) facility is used and the alternate BES is placed in standby status, pdinit cannot be executed. To execute pdinit while using the standby-less system switchover (1:1) facility, start all normal BESs as running systems.
  6. The free space reusage facility is applied to dictionary tables when you execute the database initialization utility.

(2) Notes

  1. The following are the pdinit utility's return codes:
    0: Normal termination
    4: Normal termination (warning-level error occurred, but processing terminated normally)
    8: Normal termination (initialization terminated normally, but the communication about termination of initialization resulted in an error)
    12: Abnormal termination
  2. The pdinit results can be checked by the following methods:
    pddbls command (-r ALL -a specified)
    Retrieval of data dictionary table
    Database condition analysis utility
  3. If you selected utf-8 or utf-8_ivs as the character encoding in the pdsetup command, you can use a control statements file that contains a BOM. However, only ASCII characters are permitted for comments in the control statements file. If character encoding other than ASCII is used, pdinit may not function correctly.
  4. If you use a HiRDB expansion unit (by specifying the pd_system_expand_unit operand), pdinit cannot be used to create RDAREAs in the HiRDB expansion unit. You must use pdmod (database structure modification utility) to create RDAREAs in a HiRDB expansion unit.
  5. If Real Time SAN Replication based on the log-only synchronous method is used and pdinit was executed at the transaction execution site, you must execute the preparations for log application.