test

Sun Cluster Data Service for SAP Guide for Solaris OS

Verifying the SAP Installation

This section contains the procedures you need to verify the SAP installation.

ProcedureHow to Verify SAP and the Database Installation With Central Instance

Use this procedure to verify the SAP central instance. Perform the following steps on all the potential nodes on which the central instance can run.

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


    # clresourcegroup create sap-ci-resource-group [-n node-zone-list]
    Note –

    Use the -n option to the clresourcegroup(1CL) command to select the set of nodes on which the SAP central instance can run.

  2. Verify that you have added to your name service database all the network resources that you use.

  3. Add a network resource (logical hostname) to the failover resource group.


    # clreslogicalhostname create -g sap-ci-resource-group \
 -d sap-ci-resource
    Note –

    If you require a fully qualified hostname, you must specify the fully qualified name with the -h option and you cannot use the fully qualified form in the resource name.

  4. Enable the resource group.

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


    # clresourcegroup online -emM sap-ci-resource-group

  5. Log in to the cluster member that hosts the resource group for the central instance.

  6. Ensure that the database is running.

  7. If you are you using the MaxDB database, create a .XUSER.62 file in the SAPSIDadm home directory as described in How to Install and Configure MaxDB in Sun Cluster Data Service for MaxDB Guide for Solaris OS. Verify that the .XUSER.62 file is correctly configured by using the -d option of the R3trans command. You must be an SAPSIDadm user to perform this verification.

    If you are not using the MaxDB database, proceed to the next step.

  8. Manually start the central instance.

  9. Start the SAP GUI by using the logical hostname, and verify that SAP initializes correctly.

    The default dispatcher port is 3200.

  10. Manually stop the central instance.

  11. Switch this resource group to another cluster member that can host the central instance.


    # clresourcegroup switch -n node sap-ci-resource-group

  12. Repeat the steps Step 5 to Step 10 until you verify startup and shutdown of the central instance on each cluster node that can host the central instance.

Next Steps

Go to How to Verify an SAP Failover Application Server.

ProcedureHow to Verify an SAP Failover Application Server

Use this procedure to verify SAP and the database installation for the failover application server. Perform the following steps on all the potential nodes on which the failover application server can run.

  1. Create the failover resource group to hold the network and application server resources.


    #  clresourcegroup create sap-as-fo-resource-group
    Note –

    Use the -p option to the clresourcegroup command to select the set of nodes on which the SAP application server can run.


    # clresourcegroup create sap-as-fo-resource-group [-p node-zone-list]

  2. Verify that you added to your name service database all the network resources that you use.

  3. Add a network resource (logical hostname) to the failover resource group.


    # clreslogicalhostname create -g sap-as-fo-resource-group \
 -d sap-as-fo-logical-hostname
    Note –

    If you require a fully qualified hostname, you must specify the fully qualified name with the -h option and you cannot use the fully qualified form in the resource name.

  4. Enable the resource group.

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


    # clresourcegroup online -emM sap-as-of-resource-group

  5. Log in to the cluster member that hosts the application server resource group.

  6. If you are you using the MaxDB database, proceed to Step 7. Otherwise go to Step 9.

  7. Create a .XUSER.62 file in the SAPSIDadm home directory as described in How to Install and Configure MaxDB in Sun Cluster Data Service for MaxDB Guide for Solaris OS.

  8. Verify that the .XUSER.62 file is correctly configured by using the -d option of the R3trans command.

    Note –

    You must be an SAPSIDadm user to perform this verification.

  9. Manually start the application server.

  10. Start the SAP GUI by using the logical hostname, and verify that SAP initializes correctly.

  11. Manually stop the application server.

  12. Switch this resource group to another cluster member that can host the application server.


    # clresourcegroup switch -n nodesap-as-fo-resource-group

  13. Repeat the steps Step 5 to Step 10 until you verify startup and shutdown of the application server on each cluster node that can host the application server.

Next Steps

Go to Installing the Sun Cluster HA for SAP Packages.

Verifying an SAP Scalable Application Server

If you installed scalable application server instances in How to Install and Enable an SAP Scalable Application Server, you verified the installation of an SAP scalable application server in Step 10 of How to Install and Enable an SAP Scalable Application Server.

Where to Go From Here

Go to Installing the Sun Cluster HA for SAP Packages.