Using automated client rerouting with HADR

The client reroute mechanism is based on transferring the client application requests from a failed server to one that is available and running. After we initiate a takeover or takeover by force, the primary database is no longer available to handle requests from clients, and all connections will be redirected to the new primary database.

Getting ready

All connections will be established from the DB2 client installed in Chapter 1, DB2 Instance—Administration and Configuration. In the meantime, we'll initiate a takeover and see how the client connections are reestablished to the standby site. The rerouting capability was set up during HADR implementation using Control Center.

How to do it...

1. First, we have to catalog nodedb21, db2inst1, and the NAV database, on the client.

2. Connect to the NAV primary database:

   [db2clnt1@nodedb22 ~]$ db2 "connect to NAV user db2inst1 using db2inst1"
   
      Database Connection Information
   
    Database server        = DB2/LINUXX8664...