Restrictions for HADR in Db2 pureScale environments

There are a number of restrictions that you should be aware of if you are planning to deploy HADR in a Db2 pureScale environment.

The restrictions are as follows:
  • A peer window is not supported. The hadr_peer_window configuration parameter must be set to 0.
  • You cannot have more than one HADR standby database associated with a primary database.
  • The topology of the primary and the standby must be synchronized. If you add a member on the primary, that operation is replayed on the standby. If you drop a member on the primary, you must reinitialize the standby by using a backup or a split mirror from the primary's new topology.
  • The reads on standby feature is not supported.
  • You cannot use the integrated cluster manager, IBM Tivoli System Automation for Multiplatforms (SA MP), to manage automated failover; it manages high availability within the local cluster only.
  • Network address translation (NAT) between the primary and standby sites is not supported.
  • On Linux® for the IBM Z® platform, this feature is currently supported in Db2 pureScale version 11.5.8 and later.