Nonstop Database, HiRDB Version 9 System Operation Guide

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

9.2.3 Notes on executing the system reconfiguration command

Note on system log files (important)
When you execute the system reconfiguration command, system log files are swapped. Therefore, before you execute the pdchgconf command, check that swappable target files are available. If you execute the pdchgconf command when no swappable target files are available, HiRDB terminates abnormally. If this happens, prepare a swappable target file, and restart HiRDB with the pdstart command.

Environments in which the system reconfiguration command cannot be executed
The system reconfiguration command cannot be executed when any one of the following conditions applies:
  • HiRDB was started with the pdstart -r command.
  • A unit or server is stopped (including in reduced activation).#
  • An ongoing network communications failure has occurred between units.#
  • An updatable online reorganization session is executing.
  • The pdrplstop command is executing.
  • There is an in-memory RDAREA.
  • A temporary table unique to the SQL session has been instantiated.
  • The HiRDB expansion unit is used (the pd_system_expand_unit operand is specified).#
#: This is applicable to HiRDB parallel server configurations only.
Reference note
When a recovery-unnecessary front-end server is used, the environments in which the system reconfiguration command cannot be executed differ. For details, see 9.2.5(3) Relationship with a recovery-unnecessary front-end server (HiRDB parallel server configurations only).

Restrictions and limitations on executing the system configuration command
  • Do not execute any other command or utility while the system reconfiguration command is executing. If you do, an error message stating that HiRDB has stopped might be issued.
  • Cursors cannot be held when the system reconfiguration command is executed. Therefore, do not execute the command while a UAP that uses a holdable cursor is executing.
  • The UNTIL DISCONNECT lock specification cannot be retained when the system reconfiguration command is executed. Therefore, do not execute the command while a UAP that uses the LOCK statement of the UNTIL DISCONNECT specification is executing.
  • Responses to UAPs are slower than normal while the system reconfiguration command is executing.
  • If you execute the system reconfiguration command while using a HiRDB client of version 07-00 or earlier, the HiRDB server is disconnected from that HiRDB client. Therefore, if you are using HiRDB clients of version 07-00 or earlier, be careful to execute the system reconfiguration command only when doing so will not interfere with normal operations.

Notes on linkage with HiRDB Datareplicator
If you add or delete a unit or server while HiRDB is linked to HiRDB Datareplicator, you must rebuild the extraction environment of HiRDB Datareplicator. Furthermore, if a HiRDB transaction adds, updates, or deletes the extracted database while the extraction environment of HiRDB Datareplicator is being rebuilt, a mismatch with the target database occurs. For this reason, do not execute the system reconfiguration command while the extraction environment of HiRDB Datareplicator is being rebuilt.