HADB Resource Keeps Restarting After Panicking One of the Cluster Nodes (6278435)

Problem Summary: After bringing the resource online and panicking one of the nodes in the cluster (for example, shutdown or uadmin), the resource keeps restarting on the other nodes. The user will not be able to issue any management commands.

Workaround: To prevent this problem, log onto a single node as root or a role with equivalent access privileges and increase the probe_timeout of the resource to a value of 600 seconds, using the following command:

scrgadm -c -j hadb resource -x Probe_timeout=600

To verify your change, shutdown one of the cluster nodes and check to make sure the resource does not go into the degraded state.