19.5 Notes

  1. A maximum of 1120 RDAREAs can be restored per server by a single execution of the database recovery utility.
  2. During database recovery, no other user can access an RDAREA subject to recovery processing.
  3. When executing the database recovery utility, do not specify an unload log file that was created before executing the database initialization utility. If such an unload log file is specified, the operation cannot be guaranteed.
  4. To restore an extracted database subject to data linkage, use the backup copy of the database and the log obtained after the backup was made. If you use any other method to restore the database, inconsistency results between the extracted database and the target database.
  5. If the database recovery utility execution is cancelled due to a power failure or by the kill command, the HiRDB file system area may be damaged. If the pdfls command detects inconsistency, restore the HiRDB file system area using one of the following methods:
    • Re-create the HiRDB file system area using the pdfmkfs command and execute the recovery utility for each RDAREA to restore the HiRDB files contained in the HiRDB file system area.
    • Execute the pdfbkup and pdfrstr commands to back up and restore the HiRDB file system area.
  6. If a regular file is used for the HiRDB file system area that contains the RDAREAs subject to recovery processing, and the pdfmkfs command is executed without specifying the -I option, you need to use the backup file created by the database copy utility to restore database from the log.
  7. If both EasyMT and JP1/Magnetic Tape Access are installed in the system, the utility starts JP1/Magnetic Tape Access.
  8. The maximum number of copies of the database recovery utility that can be executed concurrently depends on the value of the pd_utl_exec_mode operand in the system common definition:
    • pd_utl_exec_mode=0
      You can execute a maximum of 32 copies concurrently.
    • pd_utl_exec_mode=1
      You can execute as many copies as there are specified in the pd_max_users operand.
  9. If you made a backup copy with the pdcopy command with the -J option specified and some RDAREAs were skipped, recovery processing using that backup copy will not restore the skipped RDAREAs.
  10. The return codes of pdrstr are as follows:
    0: Normal termination
    4: Warning termination (recovery processing terminated normally, but an error occurred at the warning level that is unrelated to recovery processing)
    8: Abnormal termination (an error occurred during recovery processing, but some RDAREAs were restored)
    12: Abnormal termination
  11. If you use Real Time SAN Replication based on the log-only synchronous method and execute pdrstr at the transaction execution site, you must perform the preparations for log application. For details about the preparations for log application, see the manual HiRDB Version 8 Disaster Recovery System Configuration and Operation Guide.
  12. If you selected utf-8 as the character encoding in the pdsetup command, you can use a file with a BOM as the control statements file for pdrstr. Note that even when a file with a BOM is used as the control statements file, the BOM is skipped. No BOM is included in the file that is output by pdrstr.