Oracle^® Solaris Cluster Data Service for SAP NetWeaver Guide

How to Verify the Operation of the Fault Monitor for the SAP Instance Resource Types

This procedure is applicable for the following instance resource types:

• SAP central services

• SAP replicated enqueue server

• SAP application server instance

Perform this procedure on each set of two nodes where the SAP instance process can run.

1. Assume the root role on a cluster node.
2. Ensure that the resource group hosting the SAP instance resource is offline on all nodes.
3. Bring online the resource group to which the SAP instance belongs.

   # clresourcegroup online -n node instance-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.

   instance-rg

   Specifies the name of the resource group to be brought online. This group is the resource group to which the SAP instance belongs.

4. Terminate the SAP instance process.

   # su - sidadm -c "sapcontrol -nr instance_number -function Stop"

   Alternatively, kill the instance processes except the corresponding SAP sapstartsrv process. If you enable the interaction between Oracle Solaris Cluster and SAP NetWeaver, you must kill the instance processes.

5. Confirm that the SAP instance resource gets restarted.

   Run the clresource status command to confirm that the SAP instance resource is online on the first node.

6. Switch over the resource group hosting the SAP sapstartsrv to another node if the resource group is configured as a failover resource group. If the resource group is configured as a multiple master resource group, skip this step.

   # clresourcegroup switch -n node instance-rg

   -n node

   Specifies the name of the node on which the resource group is to be brought online.

   instance-rg

   Specifies the name of the resource group to be brought online. This group is the resource group to which the SAP instance belongs.