JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris Cluster Data Service for SAP Guide     Oracle Solaris Cluster
search filter icon
search icon

Document Information

Preface

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

Configuration Restrictions

Configuration Requirements

Standard Data Service Configurations

Configuration Considerations

Failover and Scalable Applications

Scalable Applications

Configuration Planning Questions

Packages and Support

Upgrading Oracle Solaris Cluster HA for SAP

How to Upgrade a Resource Type or Convert a Failover Application Resource to a Scalable Application Resource

Preparing the Nodes and Disks

How to Prepare the Nodes

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 J2EE Engine Cluster With Your Oracle Solaris Cluster Oracle Solaris Cluster HA for SAP With an Application Server

How to Configure an SAP J2EE Engine With Your Oracle Solaris Cluster Oracle Solaris Cluster HA for SAP With Central Instance

How to Configure an SAP Web Dispatcher With Your Oracle Solaris Cluster Oracle Solaris Cluster HA for SAP

Configuring Your Highly Available Database

Where to Go From Here

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

Where to Go From Here

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

Setting Up a Lock File

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

How to Verify the Installation and Configuration of Oracle Solaris Cluster HA for SAP as a Failover Data Service

How to Verify the Installation and Configuration of Oracle Solaris Cluster HA for SAP as a Scalable Data Service

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

Index

Setting Up a Lock File

Use the procedure in this section to perform the following tasks.

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 Oracle Solaris Cluster 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.

How to Set Up a Lock File for Central Instance or the Failover Application Server

Use this procedure to set up a lock file for the central instance or the failover application server.

  1. Install the latest patch for the sapstart executable, which enables Oracle Solaris Cluster HA for SAP users to configure a lock file.
  2. Set up the lock file for the central instance or the failover application server on a cluster file system.
  3. Edit the profile that sapstart uses to start the instance such that you add the new SAP parameter, sapstart/lockfile, for the central instance or failover application server. This profile is the one that is passed to sapstart as a parameter in the startsap script.

    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
    sapstart/lockfile

    New parameter name.

    /usr/sap/SAPSID/Service-StringSystem-Number/work

    Work directory for the central instance.

    /usr/sap/SAPSID/Dinstance-id/work

    Work directory for failover application server.

    startup_lockfile

    Lock file name that Oracle Solaris Cluster 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.


How to Set Up a Lock File for Scalable Application Server

Use this procedure to set up a lock file for a scalable application server.

  1. Install the latest patch for the sapstart executable, which enables Oracle Solaris Cluster HA for SAP users to configure a lock file.
  2. Set up the application server lock file on the local file system.
  3. Edit the profile that sapstart uses to start the instance such that you add the new SAP parameter, sapstart/lockfile, for scalable application server. This profile is the one that is passed to sapstart as a parameter in the startsap script.
    sapstart/lockfile =/usr/sap/local/SAPSID/Dinstance-id/work/startup_lockfile
    sapstart/lockfile

    New parameter name

    /usr/sap/local/SAPSID/Dinstance-id/work

    Work directory for the scalable application server

    startup_lockfile

    Lock file name that Oracle Solaris Cluster 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.