IBM® DB2 active/passive using cluster failover software

Conceptually, DB2® active/passive failover configurations using cluster failover software operates as described in "Active/Passive Cluster Failover Configurations". The standby node takes over the primary node's resources (the database files, logs) and identity (IP address, SAN WWNN). The database service is then started on the standby node. During the startup, DB2 goes through its normal crash recovery and ensures committed changes are made to the database and incomplete transactions are rolled back. When DB2 is finished with crash recovery, the database service is made available.

From the Sterling Selling and Fulfillment Foundation perspective, you can expect the following to occur after the primary node fails (and the database server is unavailable).

Setting up and testing an active/passive failover configuration can be tricky with many interdependencies and related parts. We strongly encourage you to contact the cluster failover vendors for assistance in planning and implementing your cluster failover.