Oracle^® Solaris Cluster Data Service for SAP NetWeaver Guide

How to Verify the Operation of the Fault Monitor for the SAP sapstartsrv Process

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

1. Assume the root role on a cluster node.
2. Ensure that the resource group hosting the SAP sapstartsrv resource is offline on all nodes.
3. Bring online the resource group to which the SAP sapstartsrv 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 sapstartsrv belongs.

4. Terminate the SAP sapstartsrv process.

   # su - sidadm -c "sapcontrol -nr instance number -function StopService"

   Alternatively, kill the SAP sapstartsrv process.

   Once you enable the interaction between SAP NetWeaver and Oracle Solaris Cluster, you must kill the instance processes to achieve a restart.

5. Confirm that the SAP sapstartsrv process gets restarted.

   Run the clresource status command to confirm that the SAP sapstartsrv 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 central-rg

   -n node

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

   central-rg

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