High availability in DB2 pureScale environments

DB2 pureScale is designed to be a high-availability solution. In the case when one member is failing, for different reasons, the first step is to try to restart it; if this is not possible, then an automatic failover will be conducted on one of the available members. This is a summary description of the automatic rerouting mechanism, which is absolutely transparent for clients. The next case is related to CF failures; in this case, all the work is taken by the peer CF, which will become the new primary, after performing the synchronization steps.

Getting ready

In this recipe, we will simulate a CF failure; next, we will follow the phases of transition of the second CF until it becomes the primary CF.

How to do it…

1. Stop the primary CF gracefully, by executing the following command:

   	db2sdin1@fndb1-pre-mgt:/home/db2sdin1# db2stop cf 128
   	SQL1064N  DB2STOP processing was successful.
   	db2sdin1@fndb1-pre-mgt:/home/db2sdin1#
   

2. Query from DB2_GET_INSTANCE_INFO...