1. Installing and Configuring HA for SAP
Installing and Configuring HA for SAP
Planning the HA for SAP Installation and Configuration
Standard Data Service Configurations
Failover and Scalable Applications
Configuration Planning Questions
Installing and Configuring SAP and Database
How to Install SAP and the Database
How to Install and Enable an SAP Scalable Application Server
How to Enable Failover SAP Instances to Run in a Cluster
How to Configure an SAP Web Dispatcher With Your Oracle Solaris Cluster HA for SAP
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 HA for SAP Packages
How to Install the 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 HA for SAP
HA for SAP Extension Properties
HA for SAP Extension Properties for the Central Instance
HA for SAP Extension Properties for the Application Servers
How to Register and Configure HA for SAP With Central Instance
How to Register and Configure HA for SAP as a Failover Data Service
How to Register and Configure HA for SAP as a Scalable Data Service
Verifying the HA for SAP Installation and Configuration
How to Verify HA for SAP Installation and Configuration and Central Instance
How to Verify the Installation and Configuration of HA for SAP as a Failover Data Service
How to Verify the Installation and Configuration of HA for SAP as a Scalable Data Service
Understanding HA for SAP Fault Monitor
HA for SAP Fault Probes for Central Instance
Use the procedure in this section to perform the following tasks.
Set up a lock file for the central instance or the failover application server.
Set up a lock file for a scalable application server.
Set up a lock file to prevent multiple startups of the SAP instance when the instance is already active on one node. Multiple startups of the same instance cause each startup to fail. Furthermore, the failure prevents SAP shutdown scripts from performing a clean shutdown of the instances, which might cause data corruption.
If you set up a lock file, when you start the SAP instance the SAP software locks the file startup_lockfile. If you start the same instance outside the Oracle Solaris Cluster environment and then try to start SAP under the Oracle Solaris Cluster environment, the HA for SAP data service will attempt to start the same instance. However, because of the file-locking mechanism, this attempt will fail. The data service will log appropriate error messages in /var/adm/messages.
The only difference between the lock file for the central instance or the failover application server and the lock file for a scalable application server is that the lock file for the scalable application server resides on the local file system and the lock file for the central instance or the failover application server resides on a cluster file system.
Use this procedure to set up a lock file for the central instance or the failover application server.
For the central instance, type the following.
sapstart/lockfile =/usr/sap/SAPSID/ \ Service-StringSystem-Number/work/startup_lockfile
For the failover application server, type the following.
sapstart/lockfile =/usr/sap/SAPSID/ Dinstance-id/work/startup_lockfile
New parameter name.
Work directory for the central instance.
Work directory for failover application server.
Lock file name that HA for SAP uses.
SAP creates the lock file.
Note - You must locate the lock file path on a cluster file system. If you locate the lock file path locally on the nodes, a startup of the same instance from multiple nodes cannot be prevented.
Use this procedure to set up a lock file for a scalable application server.
sapstart/lockfile =/usr/sap/local/SAPSID/Dinstance-id/work/startup_lockfile
New parameter name
Work directory for the scalable application server
Lock file name that HA for SAP uses
SAP creates the lock file.
Note - The lock file will reside on the local file system. The lock file does not prevent multiple startups from other nodes, but the lock file does prevent multiple startups on the same node.