Sun Cluster 3.0 U1 Data Services Installation and Configuration Guide

How to Verify SAP and Database Installation With Central Instance

Perform this procedure to test starting and stopping the SAP central instance on all potential nodes on which the central instance can run.

  1. Create the failover resource group to hold the network logical-hostname and central-instance resources.


    # scrgadm -a -g sap-ci-resource-group
    

    Note -

    You can optionally select the set of nodes on which the SAP central instance can run with the -h option to the scrgadm(1M) command.


    # scrgadm -a -g sap-ci-resource-group -h nodelist
    


  2. Verify that you have added all the logical hostnames that you use to your name-service database.

  3. Run the scrgadm command to add a logical hostname to the failover resource group.


    # scrgadm -a -L -g sap-ci-resource-group -l logical-hostname -n nafo0@node1,nafo0@node2
    
  4. Enable the resource group.

    Run the scswitch(1M) command to move the resource group into a managed state and bring the resource group online.


    # scswitch -Z -g sap-ci-resource-group
    
  5. Log in to the cluster member that hosts the central-instance resource group.

  6. Start the central instance and the database.

  7. Start the SAP GUI to verify that SAP initializes correctly.

    The default dispatcher port is 3200.

  8. Stop the central instance and the database.

  9. Run the scswitch command.

    In the following example, the replaceable term sap-ci-resource-group represents the resource group that contains the logical-hostname resource for the central-instance resource. Switch this resource group to another cluster member that can host the central instance.


    # scswitch -z -h node -g sap-ci-resource-group
    
  10. Repeat Step 5 through Step 7 until you verify startup and shutdown of the central instance on each cluster node that can host the central instance.