Skip Navigation Links | |
Exit Print View | |
Oracle Solaris Cluster Data Service for SAP Guide Oracle Solaris Cluster |
1. Installing and Configuring Oracle Solaris Cluster HA for SAP
Oracle Solaris Cluster HA for SAP Overview
Installing and Configuring Oracle Solaris Cluster HA for SAP
Planning the Oracle Solaris Cluster HA for SAP Installation and Configuration
Standard Data Service Configurations
Failover and Scalable Applications
Configuration Planning Questions
Upgrading Oracle Solaris Cluster HA for SAP
Installing and Configuring SAP and Database
How to Install SAP and the Database
How to Install and Enable an SAP Scalable Application Server
Configuring Your Highly Available Database
Verifying the SAP Installation
How to Verify SAP and the Database Installation With Central Instance
How to Verify an SAP Failover Application Server
Verifying an SAP Scalable Application Server
Installing the Oracle Solaris Cluster HA for SAP Packages
How to Install the Oracle Solaris Cluster HA for SAP Packages
Setting Up SAP on Non-Global Zones for HAStoragePlus Configuration
How to Set Up SAP on Non-Global Zones for HAStoragePlus Configuration
Registering and Configuring Oracle Solaris Cluster HA for SAP
Oracle Solaris Cluster HA for SAP Extension Properties
Oracle Solaris Cluster HA for SAP Extension Properties for the Central Instance
Oracle Solaris Cluster HA for SAP Extension Properties for the Application Servers
How to Register and Configure Oracle Solaris Cluster HA for SAP With Central Instance
How to Register and Configure Oracle Solaris Cluster HA for SAP as a Failover Data Service
How to Register and Configure Oracle Solaris Cluster HA for SAP as a Scalable Data Service
How to Set Up a Lock File for Central Instance or the Failover Application Server
How to Set Up a Lock File for Scalable Application Server
Verifying the Oracle Solaris Cluster HA for SAP Installation and Configuration
How to Verify Oracle Solaris Cluster HA for SAP Installation and Configuration and Central Instance
Understanding Oracle Solaris Cluster HA for SAP Fault Monitor
Oracle Solaris Cluster HA for SAP Fault Probes for Central Instance
Oracle Solaris Cluster HA for SAP Fault Probes for Application Server
This section contains the procedures that you need to install and configure SAP and the database.
Use this procedure to install SAP and the database.
If you are installing SAP 7.0 and later versions or NW2004 SR1, use the logical host while installing the software. During configuration the SAP installer prompts you to skip all the steps that ask you to replace the physical-hostname references with logical-hostname references. These updates to file names and file contents with such references are not required, because when you install SAP 7.0 and later versions or NW2004 SR1 using the logical host, the SAP installer creates files and file contents using the logical hostname. Thus the updates are already taken care of.
Note - Before you install SAP software on a cluster file system, use the scstat(1M) command to verify that the Oracle Solaris Cluster software is fully operational.
After you edit the /etc/system file, reboot each node. See the SAP document R/3 Installation on UNIX-OS Dependencies for details about kernel parameter changes.
See How to Install and Enable an SAP Scalable Application Server for the procedure on how to install a scalable application server in a Oracle Solaris Cluster environment.
Next Steps
Go to How to Enable Failover SAP Instances to Run in a Cluster or How to Install and Enable an SAP Scalable Application Server.
Use this procedure to install scalable application server instances. This procedure assumes that you installed the central instance and the database. This procedure includes additional steps for SAP 6.10, SAP 6.20, SAP 6.40, SAP 7.0 and later users to ensure that Oracle Solaris Cluster HA for SAP can manage and bring online SAP 6.10, SAP 6.20, SAP 6.40, SAP 7.0 and later services. SAP 6.10, SAP 6.20, SAP 6.40, SAP 7.0 and later versions create one startsap script and one stopsap script. Other SAP versions create one startsap script and one stopsap script for each service you create. This difference accounts for the additional steps for SAP 6.10, SAP 6.20, SAP 6.40, SAP 7.0 and later users.
To configure a J2EE engine cluster with your Oracle Solaris Cluster HA for SAP, first complete this procedure. Then complete the additional steps in How to Configure an SAP J2EE Engine Cluster With Your Oracle Solaris Cluster Oracle Solaris Cluster HA for SAP With an Application Server.
To configure an SAP Web dispatcher with your Oracle Solaris Cluster HA for SAP agent, first complete this procedure. Then complete the additional steps in How to Configure an SAP Web Dispatcher With Your Oracle Solaris Cluster Oracle Solaris Cluster HA for SAP.
Tip - The following file system layout ensures ease of use and prevents data from being overwritten.
Cluster file systems
/sapmnt/SAPSID
/usr/sap/SAPSID -> all subdirectories except the app-instance subdirectory
/usr/sap/SAPSID/home -> the SAPSIDadm home directory
/usr/sap/trans
Local file systems
/usr/sap/local/SAPSID/app-instance
Ensure that the central instance and the database can fail over.
Set up the lock file on the cluster file system for the central instance to prevent a multiple startup from a different node.
For the procedure on how to set up a lock file on the central instance, see How to Set Up a Lock File for Central Instance or the Failover Application Server.
Ensure that all application servers can use the SAP binaries on a cluster file system.
See the SAP document Installation of the SAP R/3 on UNIX for details about how to install the central instance and the database.
Create a local directory for each new application server.
Example:
# mkdir -p /usr/sap/local/SUN/D03
# chown sapsidadm:sapsys /usr/sap/local/SUN/D03
Caution - You must perform this step. If you do not perform this step, you will inadvertently install a different application server instance on a cluster file system. The two application servers will then overwrite each other. |
Example:
# ln -s /usr/sap/local/SAPSID/D03 /usr/sap/SAPSID/D03
# cp /usr/sap/SAPSID/SYS/exe/run/startsap \ $SAPSID_HOME/startsap_instance-number # cp /usr/sap/SAPSID/SYS/exe/run/stopsap \ $SAPSID_HOME/stopsap_instance-number
Example:
# vi startsap_03
Before:
LOGFILE=$R3S_LOGDIR/`basename $0.log`
After:
LOGFILE=$R3S_LOGDIR/`basename $0`_`uname -n`.log
Note - This user whose home directory contains the .XUSER.62 file is an internal database user who has permissions to start, stop, and query the database.
The nodes that run the scalable application server are in the resource group node-zone-list, which is located in the scalable application server .
Note - Update the files under the SAPSIDadm home directory so that they refer to the corresponding logical hosts. This ensures that the necessary environment variables are sourced.
Next Steps
To configure a J2EE engine cluster with your Oracle Solaris Cluster Oracle Solaris Cluster HA for SAP, go to How to Configure an SAP J2EE Engine Cluster With Your Oracle Solaris Cluster Oracle Solaris Cluster HA for SAP With an Application Server.
To configure an SAP Web dispatcher with your Oracle Solaris ClusterOracle Solaris Cluster HA for SAP agent, go to How to Configure an SAP Web Dispatcher With Your Oracle Solaris Cluster Oracle Solaris Cluster HA for SAP.
If you are not using a J2EE engine cluster or an SAP Web dispatcher with your Oracle Solaris Cluster Oracle Solaris Cluster HA for SAP, go to Configuring Your Highly Available Database.
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 Oracle Solaris 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. The previous statement does not apply to SAP 7.0 and later versions and NW2004 SR1.
To configure a J2EE engine cluster with your Oracle Solaris Cluster Oracle Solaris 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 Oracle Solaris Cluster Oracle Solaris Cluster HA for SAP With Central Instance.
To configure a J2EE engine cluster with your Oracle Solaris Cluster HA for SAP with an SAP Application Server, go to How to Configure an SAP J2EE Engine Cluster With Your Oracle Solaris Cluster Oracle Solaris Cluster HA for SAP With an Application Server.
To configure SAP Web dispatcher with your Oracle Solaris Cluster Oracle Solaris Cluster HA for SAP agent, first complete this procedure. Then complete the additional steps in How to Configure an SAP Web Dispatcher With Your Oracle Solaris Cluster Oracle Solaris Cluster HA for SAP.
# cp /usr/sap/SAPSID/SYS/exe/run/startsap \ $SAPSID_HOME/startsap_logical-hostname_instance-number # cp /usr/sap/SAPSID/SYS/exe/run/stopsap \ $SAPSID_HOME/stopsap_logical-hostname_instance-number
# echo "/usr/sap/SAPSID/SYS/exe/run/startsap instance-name logical-host" > \ $SAPSID_HOME/startsap_instance-number
# chmod 755 $SAPSID_HOME/startsap_instance-number
# echo "/usr/sap/SAPSID/SYS/exe/run/stopsap instance-name logical-host" > \ $SAPSID_HOME/stopsap_instance-number
# chmod 755 $SAPSID_HOME/stopsap_instance-number
In the SAPSIDadm home directory, modify all the file names that reference a physical server name.
# su - sapsidadm # mkdir backup # cp *.* backup # for i in .*physical-hostname.*> do> mv $i `echo $i | sed \ "s/_physical-hostname//"`> done # for i in *physical-hostname*> do> mv $i `echo $i | \ sed "s/physical-hostname/logical host/"`> done
In the SAPSIDadm home directory, modify all the file contents, except log file contents, that reference a physical server name.
In the SAP profile directory, modify all the file names that reference a physical server name.
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
rdisp/enqname=ci-logical-hostname_COK_00
Note - This step is not applicable for SAP 7.0 and later versions or NW2004 SR1.
In the oraSAPSID or oradbsid home directory, modify all the file names that reference a physical server name.
In the oraSAPSID or oradbsid home directory, modify all the file contents, except log file contents, that reference a physical server name.
Next Steps
To configure a J2EE engine cluster with your Oracle Solaris Cluster HA for SAP with a Central Instance, go to How to Configure an SAP J2EE Engine With Your Oracle Solaris Cluster Oracle Solaris Cluster HA for SAP With Central Instance.
To configure a J2EE engine cluster with your Oracle Solaris Cluster HA for SAP with an SAP Application Server, go to How to Configure an SAP J2EE Engine Cluster With Your Oracle Solaris Cluster Oracle Solaris Cluster HA for SAP With an Application Server.
To configure an SAP Web dispatcher with your Oracle Solaris Cluster HA for SAP agent, go to How to Configure an SAP Web Dispatcher With Your Oracle Solaris Cluster Oracle Solaris Cluster HA for SAP.
If you are not using a J2EE engine cluster or an SAP Web dispatcher with your Oracle Solaris Cluster HA for SAP agent, go to Configuring Your Highly Available Database.
After you have completed How to Install and Enable an SAP Scalable Application Server, perform the following steps.
Note - The SAP J2EE engine is started by the SAP dispatcher, which is under the protection of the Oracle Solaris ClusterOracle Solaris Cluster HA for SAP. If the SAP J2EE engine fails, the SAP dispatcher will restart it.
logical-host-ci:port
com.sap.instanceId = logical-host-as_SAPSID_SYSNR
sapbasis.ashost = logical-host-as
Next Steps
Go to Configuring Your Highly Available Database
After you have completed How to Enable Failover SAP Instances to Run in a Cluster or How to Enable Failover SAP Instances to Run in a Cluster, perform the following steps.
Note - The SAP J2EE engine is started by the SAP dispatcher which is under the protection of the Oracle Solaris Cluster Oracle Solaris Cluster HA for SAP. If the SAP J2EE engine fails, the SAP dispatcher will restart it.
as1–1h:port;as2–1h:port ...
com.sap.instanceId = logical-host-ci_SAPSID_SYSNR
sapbasis.ashost = logical-host-ci
host = logical-host-ci
Next Steps
Go to Configuring Your Highly Available Database.
After you have configured the SAP Web dispatcher with your Oracle Solaris Cluster Oracle Solaris Cluster HA for SAP, perform the following steps.
Note - The SAP Web dispatcher has the capability of auto restart. If the SAP Web dispatcher fails, the SAP Web dispatcher watch dog process will restart. Currently, there is no Oracle Solaris Cluster agent available for the SAP Web dispatcher.
For example, SAPSYSTEM = 66 is used in the profile for the SAP Web dispatcher.
For more information, see SAP OSS note 517484.
Next Steps