test

Sun Cluster Data Service for SAP Guide for Solaris OS

ProcedureHow to Enable Failover SAP Instances to Run in a Cluster

During SAP installation, the SAP software creates files and shell scripts on the server on which you installed the SAP instance. These files and scripts use physical server names. To run the SAP software with Sun Cluster software, replace references to a physical server with references to a network resource (logical hostname). Use this procedure to enable SAP to run in a cluster.

To configure a J2EE engine cluster with your Sun Cluster HA for SAP with a Central Instance, after you complete this procedure, complete the additional steps in How to Configure an SAP J2EE Engine with your Sun Cluster HA for SAP with Central Instance.

To configure a J2EE engine cluster with your Sun Cluster HA for SAP with an SAP Application Server, go to How to Configure an SAP J2EE Engine Cluster with your Sun Cluster HA for SAP with an Application Server.

To configure SAP Web dispatcher with your Sun Cluster HA for SAP agent, after you complete this procedure, complete the additional steps in How to Configure an SAP Web Dispatcher With Your Sun Cluster HA for SAP.

Steps

  1. Make backup copies of the files you will modify in Step 5 through Step 8.

  2. Log in to the node on which you installed the SAP software.

  3. Shut down the SAP instances (central instance and application server instances) and the database.

  4. Are you using SAP 6.10 or SAP 6.20?

  5. Make a copy of the startsap script and the stopsap script, and save these files in the SAPSIDadm home directory. The filenames that you choose must specify this instance.


    # cp /usr/sap/SID/SYS/exe/run/startsap  \
$SAPSID_HOME/startsap_logical-hostname_instance-number
# cp /usr/sap/SID/SYS/exe/run/startsap \
$SAPSID_HOME/stopsap_logical-hostname_instance-number

  6. Become user sapsidadm, and then perform the following tasks.

    • In the SAPSIDadm home directory, modify all of the file names that reference a physical server name.

    • In the SAPSIDadm home directory, modify all of the file contents—except log file contents—that reference a physical server name.

    • In the SAP profile directory, modify all of the file names that reference a physical server name.

  7. As user sapsidadm, add entries for the parameter SAPLOCALHOST.

    Add this entry to the SAPSID_Service-StringSystem-Number_logical-hostname profile file under the /sapmnt/SAPSID/profile directory.

    For Central Instance:


    SAPLOCALHOST=ci-logical-hostname

    This entry enables the external application server to locate the central instance by using the network resource (logical hostname).

    For Application Server:


    SAPLOCALHOST=as-logical-hostname

  8. Become user orasapsid, and then perform the following tasks.

    • In the oraSAPSID home directory, modify all of the file names that reference a physical server name.

    • In the oraSAPSID home directory, modify all of the file contents—except log file contents—that reference a physical server name.

  9. Ensure that the /usr/sap/tmp directory owned by user sapsidadm and group sapsys exists on all nodes that can master the failover SAP instance.

Next Steps

To configure a J2EE engine cluster with your Sun Cluster HA for SAP with a Central Instance, go to How to Configure an SAP J2EE Engine with your Sun Cluster HA for SAP with Central Instance.

To configure a J2EE engine cluster with your Sun Cluster HA for SAP with an SAP Application Server, go to How to Configure an SAP J2EE Engine Cluster with your Sun Cluster HA for SAP with an Application Server.

To configure an SAP Web dispatcher with your Sun Cluster HA for SAP agent, go to How to Configure an SAP Web Dispatcher With Your Sun Cluster HA for SAP.

If you are not using a J2EE engine cluster or an SAP Web dispatcher with your Sun Cluster HA for SAP agent, go to Configuring Your Highly Available Database.