Replacing a Pacemaker-managed HADR Db2 instance with a Tivoli SA MP-managed Db2 instance

If you are running Db2 on an HADR-configured Linux cluster that is managed by Pacemaker, you can use the db2cm utility to replace cluster management with IBM Tivoli System Automation for Multiplatforms (SA MP).

About this task

Important: In Db2® 11.5.8 and later, Mutual Failover high availability is supported when using Pacemaker as the integrated cluster manager. In Db2 11.5.6 and later, the Pacemaker cluster manager for automated fail-over to HADR standby databases is packaged and installed with Db2. In Db2 11.5.5, Pacemaker is included and available for production environments. In Db2 11.5.4, Pacemaker is included as a technology preview only, for development, test, and proof-of-concept environments.
Take note of the following information before you start your conversion:
  • Db2 clients can be disconnected during this operation if the original cluster is configured to use a virtual IP address (VIP).
  • The Db2 Mutual Failover hosts remain online throughout the operation but the automated failover to the Mutual Failover standby is disabled during the conversion. No takeover is required..
  • When running db2cm, ensure that you run the command as the root user.
The following placeholders are used in the command statements throughout this procedure:
  • <exportedFile> is the name of the file to which the instance owner backs up their existing SA MP cluster configuration.
  • <resourceModel> is the name of the Pacemaker resource model that you back up before proceeding with the conversion.
Note: The following procedure assumes an in-version conversion, which means that there is no change in the Db2 version.

Procedure

  1. Back up the current Pacemaker resource model, so that it is available for future use: 
    db2cm -export <exported_file_name>
  2. Delete the current Pacemaker resources and cluster: 
    INSTANCE_HOME/sqllib/bin/db2cm -delete -cluster
  3. Create the Tivoli SA MP resource model:
    • If a backup of a previous Tivoli SA MP configuration is to be restored using a db2haicu XML file, run the following command first on the standby instance and then on the primary instance:
      db2haicu -f exportedFile.xml
    • To create the resource model from scratch, run the db2haicu on the standby instance and follow the on-screen instructions.