Enabling the database connection hang detection feature for automated HADR
Starting in version 11.5.6, the database connection hang detection feature can be enabled for automated HADR environments with both TSA and Pacemaker.
For users on version 11.5.6, refer to the database connection hang detection feature for more information.
Before you begin
What to do next
export DB2_HADR_HANG_DETECTION=CONNECTexport DB2_HADR_HANG_SQL_BYPASS=SQL1040NIf using Kerberos or other GSSAPI plug-in authentication, you need to have the instance owner logged in to that authentication method before the connection attempt. In this case, the automation script which performs the database connection attempt may need to be manually modified to log in the instance owner to the authentication method.
For TSA, the /usr/sbin/rsct/sapolicies/db2/hadrV115_start.ksh script is used for
database connection attempts.
For Pacemaker, the /usr/lib/ocf/resource.d/heartbeat/db2hadr script is used for
database connection attempts.