<html><body><p><font size="2">Hi,</font><br><br><font size="2"> I have a two node DB2 Cluster with pacemaker and HADR. When I issue a reboot -f on the node where Primary Database is running, I expect the Standby database to be promoted as Primary. But what is happening is pacemaker waits for 180 seconds (guess that is the SBD timeout) and by the time the second node takes action, the DB is already in STANDBY/REMOTE_CATCHUP_PENDING/DISCONNECTED state and cannot be promoted anymore. If that is the expected behaviour, I believe in a node crash situation, the cluster does not work. Can someone guide me on what could be wrong here. </font><br><br><font size="2" face="Arial">Thanks & Regards<br></font><b><font size="2" face="Arial"><br>Dileep Nair</font></b><font size="2" face="Arial"><br>Squad Lead - SAP Base </font><br><font size="2" face="Arial">Togaf Certified Enterprise Architect<br>IBM Services for Managed Applications<br>+91 98450 22258 Mobile<br>dilenair@in.ibm.com<br><br>IBM </font><b><font size="2" face="Arial">Services</font></b><br><BR>
</body></html>