The following prerequisites must be satisfied in order to update while HiRDB is operating:

• Version, HiRDB server type, addressing mode
  The following items must be the same for the HiRDB update version and the operating HiRDB; these items can be checked with the pdadmvr command:
  
  • Version number and revision number
  • HiRDB server type (HiRDB single server configuration or HiRDB parallel server configuration)
  • Addressing mode (32-bit mode or 64-bit mode)
• Operating system parameters
  Estimates of the operating system parameters that will be required by HiRDB after the switch must be within the bounds of the currently set kernel parameters.
  
• HiRDB directory
  The installation directory must not be the same as the HiRDB directory.
  
• Library sharing
  In the case of multi-HiRDBs, the libraries must not be shared.
  
• Free disk space
  There must be sufficient free disk space in the HiRDB directory to store both the currently operating HiRDB and the HiRDB update version. See the release notes for the free space required for the HiRDB update version.
  
• HiRDB client
  A HiRDB client that is working online must be running on a HiRDB server that is not being updated. Such a HiRDB client that is operating on a HiRDB server that is to be updated must be terminated and the online job must be terminated.
  
• Client library
  The HiRDB/Developer's Kit and HiRDB/Run Time that are being used by a HiRDB client that is working online must be version 07-00 or later. If an earlier version is being used, the connection of the HiRDB client will be released during updating.
  
• Application of the automatic reconnect facility
  A HiRDB client that is connected to HiRDB must use the automatic reconnect facility (PDAUTORECONNECT=YES). If the automatic reconnect facility is not being used, the connection of the HiRDB client will be released during updating. For details about the automatic reconnect facility, see the HiRDB Version 9 UAP Development Guide.