You can configure the automatic client reroute feature (ACR) of DB2® to adapt it to work with the database in your environment.
The method that you use to configure the automatic client reroute feature depends on the type of high availability database configuration that is already in place.
In all cases, the standby database must be online and functional before the automatic client reroute feature can properly reestablish the connection. Automated failover to the standby node is a more efficient approach than a manual takeover.
For more information, see the automatic client reroute section of the High Availability and Disaster Recovery Options for DB2 on Linux, UNIX, and Windows IBM Redbooks® publication.
When you enable the automatic client reroute feature and use the verification command, you can see that an alternative database is specified by checking the data that is returned. You can check for the same alternative database on all nodes in the topology:
Database 1 entry: | |
---|---|
Database alias | MAXIMO |
Database name | MAXIMO |
Local database directory | /home/db2inst1 |
Database release level | d.00 |
Comment | |
Directory entry type | Indirect |
Catalog database partition number | 0 |
Alternate server hostname | virtualhostname |
Alternate server port number | 50000 |