Nonstop Database, HiRDB Version 9 System Operation Guide

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

9.2.4 HiRDB status after the system reconfiguration command has executed

After the system reconfiguration command has executed, HiRDB is in the same status it would be when it restarts normally. This means that the following events occur:

  1. System log files are swapped.
  2. Message log files are swapped. To retain messages in the message log file, back up the message log file before you execute the system reconfiguration command.
  3. Global buffers assigned with the database structure modification utility become invalid.
  4. Global buffers modified dynamically by the pdbufmod command become invalid.
  5. The time count of the cleanup interval for troubleshooting information specified with the pd_spool_cleanup_interval operand resets to 0.
  6. If normal or force (default) is specified in the pd_spool_cleanup operand, troubleshooting information that has already been output is deleted.
  7. Any statistical information collection change made with the pdstbegin or pdstend command becomes invalid, and the values specified in the pd_statistics and pdstbegin operands take effect.
  8. Any resident process count change made with the pdchprc command becomes invalid, and the specification in the HiRDB system definitions takes effect.
  9. If the pd_db_io_error_action=unitdown specification becomes invalid due to recurrence of an I/O error after HiRDB (or a unit in the case of a HiRDB parallel server configuration) terminates abnormally, the unitdown specification takes effect.
  10. Lists used for narrowed searches are lost.