How to Verify the Operation of the Fault Monitor for the SAP Replicated Enqueue Preempter Resource
Type
Perform this procedure on each node where the SAP replicated enqueue preempter can run.
Note -
This procedure runs only
if the resource group is not in Maintenance.
-
Assume the root role on a cluster node.
-
Ensure that the resource group hosting the SAP replicated enqueue preempter resource is
offline on all nodes.
-
Set the pingpong interval to 300 for the resource group containing the
replicated enqueue server.
# clresourcegroup set -p Pingpong_interval=300 ers-rg
-
Bring online the resource group to which the SAP replicated enqueue preempter
belongs.
# clresourcegroup online -n node central-rg
- -n node
-
Specifies the name of the node on which the resource group is
to be brought online. This node is the node that you have just
logged in to.
- central-rg
-
Specifies the name of the resource group to be brought online.
This group is the resource group to which the SAP replicated enqueue preempter
belongs.
-
Bring online the resource group to which the SAP replicated enqueue server
belongs.
# clresourcegroup switch -n node2 central-rg
- -n
node2
-
Specifies the name of the node on which the resource group is
to be brought online. This node is the node that you have just
logged in to.
- central-rg
-
Specifies the name of the resource group to be brought online.
This group is the resource group to which the
SAP central services belongs.
-
Switch over the resource group hosting the SAP replicated enqueue preempter to the node
hosting the SAP replicated enqueue server.
-
Confirm that the SAP replicated enqueue server resource group gets restarted on a spare
node as long as a spare node is available.
Run the clresource status command to confirm that the
SAP replicated enqueue server resource is online on the first node.
-
Set the pingpong interval to 3600 for the resource group containing the
replicated enqueue server.
# clresourcegroup set -p Pingpong_interval=3600 ers-rg