Configuring a cluster automatically with the Db2 High Availability (HA) Feature

In a clustered environment, some database manager instance configuration and administration operations require related cluster configuration changes. The Db2 High Availability Feature (HA) Feature enables the database manager to automatically request cluster manager configuration changes whenever you perform certain database manager instance configuration and administration operations.

Before you begin

To enable the database manager to perform required cluster configuration for database administration tasks, you must configure the instance for high availability by using one of the following utilities:
db2cm
This creates a cluster domain for the instance managed by Pacemaker. The db2cm command is only supported on Linux systems. For more information, see Configuring high availability with the Db2 cluster manager utility (db2cm).
db2haicu
This creates a cluster domain for the instance managed by IBM® Tivoli® System Automation for Multiplatforms (SA MP) (TSA). In Db2 12.1.0 and later, the db2haicu command is only supported on AIX systems. For more information, see Configuring a clustered environment using Db2 High Availability Instance Configuration Utility (db2haicu).

Procedure

When you perform the following database manager instance configuration and administration operations, the database manager automatically performs related cluster manager configuration for you:

  • Starting a database using START DATABASE or db2start.
  • Stopping a database using STOP DATABASE or db2stop.
  • Creating a database using CREATE DATABASE.
  • Adding storage using CREATE TABLESPACE.
  • Removing storage using ALTER TABLESPACE DROP or DROP TABLESPACE.
  • Adding or removing storage paths using ALTER DATABASE.
  • Dropping a database using DROP TABLESPACE.
  • Restoring a database using the RESTORE DATABASE or db2Restore.
  • Specifying the table space containers for redirected restore using SET TABLESPACE CONTAINERS.
  • Rolling a database forward using ROLLFORWARD DATABASE or db2Rollforward.
  • Recovering a database using RECOVER DATABASE or db2Recover.
  • Creating event monitors using CREATE EVENT MONITOR.
  • Dropping event monitors using DROP EVENT MONITOR.
  • Creating and altering external routines using:
    • CREATE PROCEDURE
    • CREATE FUNCTION
    • CREATE FUNCTION
    • CREATE METHOD
    • ALTER PROCEDURE
    • ALTER FUNCTION
    • ALTER METHOD
  • Dropping external routines using:
    • DROP PROCEDURE
    • DROP FUNCTION
    • DROP METHOD
  • Start Db2 High Availability Disaster Recovery (HADR) operations for a database using START HADR.
  • Stop HADR operations for a database using STOP HADR.
  • Cause an HADR standby database to take over as an HADR primary database using TAKEOVER HADR.
  • Setting the database manager configuration parameter diagpath or spm_log_path.
  • Setting the database configuration parameter newlogpath, overflowlogpath, mirrorlogpath, or failarchpath.
  • Dropping a database manager instance using db2idrop.

Results

When the database manager coordinates the cluster configuration changes for database administration tasks listed, you do not have to perform separate cluster manager operations.