Sap Availability On Rac TWP 133712

Proiding ligh Aailability or
SAP Resources

.v Oracte !bite Paer
.rit 200

Providing High Availability for SAP Resources Page 2
Proiding ligh Aailability or SAP Resources

Oeriew o ligh Aailability or SAP Resources .......................................3
SAP Support or ligh Aailability ..................................................................3
Installation and Management ...........................................................................5
Oeriew O Installation and Coniguration.................................................6
lunctionality .......................................................................................................9
Usage ...............................................................................................................9
Conclusion........................................................................................................ 12
\orked Lxample............................................................................................. 13
Appendix 1 - Standard SAP Script Modiications..................................... 18
Script: startsap............................................................................................. 18
Script: stopsap............................................................................................. 21
Appendix 2 - Sample proile scripts - LNQULUL Serice ,ASC,......... 23
Appendix 3 - Sample proile scripts - RLPLICA1ION Serice ,LNR, 25
Appendix 4 - 1roubleshooting and Log liles............................................ 2
Appendix 5 - SAPC1L Bill o Materials ...................................................... 28

Proiding ligh Aailability or SAP Resources

OVERVIEW OF HIGH AVAILABILITY FOR SAP RESOURCES
Oracle Clusterware can proide high aailability or SAP resources just as it does
or Oracle resources. Oracle has created an Oracle Clusterware tool, SAP Control
,SAPC1L,, to enable you to easily manage SAP high aailability resources.
SAPC1L proides an easy-to-use interace to administer the resources, scripts, and
dependencies o Oracle Clusterware and SAP high aailability components.
SAPC1L consolidates the unctionality o the Oracle command-line tools by
enabling you to easily manage the SAP Lnqueue Serice, the SAP Replication
Serice, and the irtual IP address used by the SAP Lnqueue Serice.
SAP SUPPORT FOR HIGH AVAILABILITY
1he SAP Lnqueue Serice proides distributed lock management or SAP R,3
instances. 1he SAP Lnqueue Serice must be aailable wheneer an SAP
installation uses more than one SAP R,3 instance.
SAP uses an actie,passie approach to enable high aailability or the Lnqueue
Serice. 1here is exactly one Lnqueue Serice running in the SAP system. 1he
SAP system comprises multiple application instances on dierent nodes. One or
more SAP Replication Serices run on the node on which the actie Lnqueue
Serice runs in the eent o a ailure or planned outage.
Lach Replication Serice maintains a copy o the Lnqueue Serice`s lock table, this
copy is kept in a shared memory segment during runtime. 1he node that supports
the Lnqueue Serice also hosts a irtual IP address ,VIP, or communication.
\heneer the actie node ails or is shut down, the VIP and Lnqueue Serice ail
oer to the next node. 1he aailable node supports the Replication Serice.

SAP Lnqueue and Replication Serer Nodes
Providing High Availability is an essential
component in the world of business
continuity
This paper explains how to use Oracle
Clusterware to enable high availability for
SAP resources
The term service is used to signify the
SAP process that provides either
Enqueue or Replication
The nodes that host these services are
termed the Enqueue Server and the
Replication Server
Active
Enqueue
Service

Replication
Service

Passive
Replication
Service

Passive
Replication
Service

VIP

R/3
Instance

R/3
Instance

R/3
Instance

R/3
Instance


ORACLE CLUSTERWARE

Oracle Clusterware, ormerly known as Cluster Ready Serices ,CRS,, is an
integrated cluster management solution that enables linking multiple serers so that
they unction as a single system. \hile continuing to be required or Oracle RAC
databases, Oracle Clusterware can also support non-Oracle applications.
OVERVIEW OF THE SAPCTL IMPLEMENTATION
1his solution uses Oracle Clusterware to enable high aailability or the SAP
Lnqueue Serice. 1he implementation uses Oracle Clusterware modeling eatures
so that each managed entity is represented as a resource. 1his solution uses three
resources, one each or the Lnqueue Serice, Replication Serice, and the VIP
resource.
1he management policy or the Lnqueue Serice and VIP are conigured so that
the two are collocated, while the policy or the Replication Serice resource ensures
that it is neer running on the same node as the Lnqueue Serice. 1he ailoer
policy or the Lnqueue Serice resource guarantees that upon ailure, the Lnqueue
Serice is restarted on the node that is currently hosting the Replication Serice, i
any. 1he Replication Serice will be subsequently relocated to a dierent node i
one is aailable.

SUPPORTED CONFIGURATIONS

1he Lnqueue and Replication Serices can run on any node that supports SAP R,3
which is limited to the ollowing two conigurations:
All solutions require shared disk or the Oracle Cluster Registry ,OCR,
and oting disk deice.
All solutions assume that SAP runs in an Oracle RAC enironment.
Cotocatiov of vqveve ava Reticatiov errice. ritb tbe Oracte aataba.e. lor example, a
two-node Linux cluster running Oracle RAC and R,3 in a co-located coniguration.

Active
Enqueue
Service

Replication
Service

VIP
R/3 Instance R/3 Instance
RAC Instance RAC Instance
Node 1
Node 2

Cotocatiov of vqveve ava Reticatiov errice. iv tbe .ave Oracte R.C evrirovvevt a. tbe
Oracte aataba.e. lor example, a our-node Linux cluster running Oracle RAC on two
nodes and R,3 on two nodes o the same cluster.

INSTALLATION AND MANAGEMENT

\ou must install the Oracle Database sotware that you are using with your SAP
installation in the deault operating system group, OSDBA ,dba,. In addition, the
users sidadm, orasid rom SAP as well as the Oracle Clusterware owner
,oracle, must belong to the dba group. 1he dba group is also the primary group or
the Oracle Clusterware owner ,oracle, and orasid. lor more inormation about
groups and users or SAP enironments, reer to the SAP documentation.

REQUIREMENTS FOR RUNNING SAPCTL

Beore running SAPC1L, your enironment must meet the ollowing conditions:
1he ORA_CRS_lOML enironment ariable must be set to point at the
Oracle Clusterware installation.
\ou must run 'create', 'remoe', and 'update' commands as the 'root' user.
\ou may run 'start' and 'stop' commands as 'root', 'sapuser', or any user
belonging the 'sapuser's' primary group.
\ou may run 'status' and 'conig' commands as any user.

1hese requirements describe the deault Oracle permission scheme. \ou can,
howeer, modiy the permission scheme with the crs_setperm,, command.

Active
Enqueue
Service

Replication
Service

VIP
R/3 Instance R/3 Instance
RAC Instance RAC Instance
Node 1 Node 2 Node 3 Node 4
OVERVIEW OF INSTALLATION AND CONFIGURATION

1he procedures or installing this solution comprise the ollowing tasks:
Appropriately coniguring the SAP application
Registering the SAP Lnqueue and Replication Serices with the Oracle
Clusterware.

CONFIGURING SAP

1he coniguration changes that you need to make to enable SAPC1L are not
automated. Instead, you must manually conigure the changes. 1he required
changes are, howeer, minimal and aect only two shell scripts, namely startsap
and stopsap. 1he changes to these two scripts are documented in Appendix 1 o
this paper.

A ew other minor modiications to your existing coniguration, namely the
generation o nearly identical proiles with dierent ile names, are also required.
1his is because Oracle Clusterware does not change the hostname o the cluster
node i the VIP ails oer to another node. In addition, the SAP high aailability
agent coniguration must consider that SAP queries the hostname or uses the
cluster node`s hostname to identiy the proile and parameter ile sets to run on the
node.

Also note that using an Oracle RAC database requires additional proile changes.
1he coniguration steps or this are documented in the white paper 'Coniguring
SAP R,3 or use with Oracle RAC'.

STARTSAP/STOPSAP SCRIPTS

Use the SAP 'startsap' and 'stopsap' scripts to start and stop SAP R,3 application
instances. \ou must adapt these scripts to interact with Oracle Clusterware and to
enable the use o the SAP high aailability implementation with a standalone
Lnqueue Serice and Lnqueue Replication Serice.

1he modiications required or interaction with Oracle Clusterware are simple:
Ater a successul start or stop o the SAP application instances with instance type
ASCS or LNR, run a command with parameters to notiy the Oracle Clusterware
ramework about the change o state. All other modiications in the startsap and
stopsap scripts enable SAPC1L to distinguish the two instance types, ASCS and
LNR, rom the other application instance types such as dialog ,D,, batch ,B,,
gateway ,G\,, spool ,S, and update ,V,.

ASCS is the deault name or the standalone Lnqueue Serice. 1his ASCS instance
contains the Lnqueue Serice and the message serice, with a small number o
dialog work processes. LNR is the instance name or the Lnqueue Replication
serice instance, which is actually the replication process.

Appendix 1 shows a small portion o the 'startsap' and 'stopsap' scripts with the
modiications denoted in boxes to highlight the required changes. 1his example is
rom SAP release 620. \ou can use this example as a template.

USER PROFILE SID<ADM>

1he home directory or the SAP user sidadm contains proile scripts or the c-
shell and the Bourne or bash shell that are commonly used in UNIX enironments.
1here are our sets o scripts and the script sets hae the ollowing purposes:

lor the enironment o the SAP application.
1o ensure that the Oracle database uses the required enironment settings.
lor the SAP Jaa irtual machine.
lor SAP APO, an SAP tool that requires a specialized enironment setup.

1he appropriate script set is called during the execution o .login ,csh, or .proile
,sh,. A common attribute o these scripts is the hostname used as the last portion
o the script name. Because Oracle Clusterware can start the SAP Lnqueue Serice
and the SAP Lnqueue Replication Serice on all o the hosts in the cluster with
arbitrary hostnames, you must duplicate these scripts with as many dierent names
as there are hosts in the cluster. \ou must do this on all hosts that are eligible or
running the respectie programs.

1he important assumption is that according to SAP, the Oracle RAC database`s
home directory also resides on a shared cluster ile system. Note that this is not
necessarily the case in all SAP Lnqueue Replication high aailability deployments.

I the home directory is on a cluster ile system, then create links with the dierent
hostnames in the cluster to the arious proile scripts. In the ollowing example,
SAP sotware has initially been installed on node1 o a our-node cluster. Node2,
node3, and node4 are the other cluster members.

# su sid<adm>
# for TYPENAME in "sapenv sapsrc dbenv dbsrc"
do
for NODENAME in "node2 node3 node4"
do
ln .$TYPENAME_node1.sh .$TYPENAME_$NODENAME.sh
ln .$TYPENAME_node1.csh .$TYPENAME_$NODENAME.csh
done
done

In case o a .j2eee or .apo proile script, create the appropriate links in the same
manner i these SAP applications are also controlled by Oracle Clusterware. lurther
discussion o this topic is outside o the scope o this white paper.

Most likely, the SAP Replicated Lnqueue implementation is part o an Oracle RAC
coniguration that enables an SAP system. Delete the enironment ariable
dbs_ora_tnsname rom all o the proiles o the user sidadm. Reer also to the
change in the startsap script explained in Appendix 1. Setting the enironment
ariable dbs_ora_tnsname oerrides all o the subsequent settings or the selection
o the database connection. 1hereore, load balancing and ailoer to dierent
database instances would not be possible. lor details about coniguring SAP with
Oracle RAC databases, reer to the white paper 'Coniguring SAP R,3 or use with
Oracle RAC' on the SAP marketplace website at: http:,,serice.sap.com,dbaora.

USER PROFILE ORA<SID>

lor administratie purposes, a special Oracle database user is created by SAP. 1his
user is known as orasid in SAP installations. 1he user orasid is the Oracle
sotware owner or the database belonging to the SAP system. lor this user
account, the same changes to the proiles as or an SAP user account sidadm are
required. Reer to the preious section, 'USLR PROlILL SIDADM' or more
inormation about the required changes.

INSTANCE PROFILE: CENTRAL INSTANCE (ASCS), ENQEUE AND
MESSAGE SERVICE

\ou must adapt the proiles or use by the standalone enqueue to the actual node
in the cluster on which the serice runs. 1he node name is part o the ilename.
1hereore, you must create a copy o the iles with the appropriate name. 1he
directory holding the instance proile and the start commands should reside on a
shared cluster ile system. 1he deault path is ,usr,sap,SID,S\S,proile. An
example or a standalone Lnqueue Serice on a two-node cluster is aailable in
Appendix 2.

INSTANCE PROFILE: ENQUEUE REPLICATION INSTANCE (ENR)

1he Lnqueue Replication instance has an instance and a start proile similar to any
other SAP instance. 1he required modiications to these proiles are the same as
those that this paper described or the standalone enqueue instance.

lor eery node in the cluster, the last part o the ile names must match the
hostname. In addition, in the instance proile, you must change some o the
parameters accordingly as shown in the example in Appendix 3
An example or a standalone Lnqueue Replication Instance on a two-node cluster
is aailable in Appendix 3.

INSTANCE PROFILE: APPLICATION SERVER INSTANCES (DV)

1he SAP application serer instances, either conigured as a dialog or dialog and
update instances, are also eligible to be under the protection o Oracle Clusterware.
1he restriction in this case is the act that these instances must run on the cluster
nodes. 1his is not alid in three-tier conigurations. lor that, the complete
coniguration is not coered by this document. In addition, it is currently not part
o the SAPC1L implementation because the instance types are not recognized by
SAPC1L. 1hereore, the remaining application serer proiles remain unmodiied.

REGISTERING WITH ORACLE CLUSTERWARE

Registration with Oracle Clusterware, as well as the subsequent management o the
resources, is done by using SAPC1L. An oeriew o this utility ollows and a
'\orked Lxample' appears later in this paper.

MANAGEMENT INTERFACE

1he management o the Lnqueue and Replication Serice as well as the VIP
resource should be done using SAPC1L. 1his command line interace can manage
any number o the installations on an Oracle Clusterware managed enironment.
See Appendix 2 for the changes that are
required to these profiles

See Appendix 3 for the changes that are
required to these profiles


SAP LEGACY MANAGEMENT INTERFACES

In addition to SAPC1L and the other conentional tools or managing SAP
Lnqueue and Replication Serices, you can also use the startsap and stopsap scripts.
loweer, Oracle recommends that you use only one management interace at the
same time. As documented in this paper, these scripts need slight modiications to
interact with Oracle Clusterware. 1hird party sotware or management o SAP
systems will probably require additional coniguration changes.

FUNCTIONALITY

SAPC1L perorms the ollowing:
Updates the Oracle Clusterware coniguration o the SAP high aailability
subsystem.
Creates and remoes the Oracle Clusterware coniguration o the SAP high
aailability subsystem.
Starts the SAP high aailability subsystem that is wrapped with Oracle
Clusterware as a whole as well as its indiidual components.
Stops the SAP high aailability subsystem that is protected by the Oracle
Clusterware as a whole as well as its indiidual components.
Queries the state ,status, o the SAP high aailability subsystem as a whole as
well as that o the components that comprise it.
Queries the coniguration o the SAP high aailability subsystem.
Usage
sapctl <command> [<object>] -sapsid <SAP_SID> [options]
Command: start|stop|status|config|create|remove|update
Objects: all|enqueue|replication
NOTE: Create, remove, and update commands work on all objects only.
For detailed help about each command and object and its options, run
the following command:
sapctl <command> -h
<Objects>
all: Includes all o the resources associated with the solution or the speciied SAP
SID.
enqueue: Reers to the Lnqueue Serice
replication: Reers to the Replication Serice
<Commands>
start
Starts the resources associated with the object.
stop
A worked example using SAPCTL
appears later in this paper
Stops the resources associated with the object.
status
Displays the current state or status o resources that are associated with the
object. 1his includes the processed output o the resource state as reported by
crs_stat
conig
Displays the coniguration o the resources associated with the object. 1his
includes the ollowing:
- 1he location o the Oracle Clusterware lome
- Resource identiier o the SAP Lnqueue Serice
- Resource identiier o the SAP Replication Serice
- 1he location o the SAP scripts
- 1he SAP home
- 1he hosting members
- 1he public network interace
- Netmask
- 1he irtual IP address
create
Creates the Oracle Clusterware resources or the SAP high aailability
subsystem. 1his command is only supported or a single object 'all' and must
be run as the 'root' user because this operation must create a VIP resource.
1he ollowing parameter switches are supported:
Parameter Description
-sapsid 1he SID or the SAP instance
-i adapter name 1he name o the public network adapter
-nm netmask 1he network mask or the public network interace
-ip IP Address A New IP Address
-u sapuser 1he SAP User sidadm
-n node1 node2 . node,n, List o nodes in the cluster
-s path 1he lome directory o the SAP install
-e LnqInst 1he Lnqueue Serice identiier
-r RepInst 1he Replication Serice identiier

1he VIP resource will be created as being owned by the 'root' user, while
other resources are created as being owned by the SAP user. All o the
generated Oracle Clusterware action scripts are owned by the SAP user.
remoe
Remoes the Oracle Clusterware resources and Oracle Clusterware action
scripts or the SAP high aailability subsystem. 1his operand is only supported
or a single object 'all' and must be run as the 'root' user because this
operation must delete a VIP resource.

update
Updates the coniguration o the SAP high aailability subsystem. 1his
operand is only supported or a single object 'all'. 1he ollowing options are
supported:
Parameter Description
- IP Address
Updates the VIP alue or the VIP used by the Lnqueue
Serice.
-a node1 node2 . node,n,
Adds one or more node names as placement candidates
or SAPC1L`s Oracle Clusterware resources. 1his option
enables you to add nodes to the cluster ater the
installation.
-d node1 node2 . node,n,
Remoes one or more names as placement candidates or
SAPC1L`s Oracle Clusterware resources. 1his option
enables you to remoe nodes rom the cluster ater
installation.

CONCLUSION
1his paper has shown how to use Oracle Clusterware to enable protection o both
the SAP Lnqueue Serice and the SAP Replication Serice.

Oracle Clusterware proides an easy way to protect SAP Serices rom ailure.
More inormation about Oracle Clusterware can be ound at this link:
http:,,www.oracle.com,technology,products,database,clustering on the Oracle
1echnology Network.
A paper ocusing on SAP on Oracle is aailable here:
http:,,www.oracle.com,technology,deploy,perormance,pd,oracle_or_sap_no1405.pd

And as a reminder - lor details about coniguring SAP with Oracle RAC databases,
reer to the white paper 'Coniguring SAP R,3 or use with Oracle RAC' in older
media library on the SAP marketplace website at: http:,,serice.sap.com,dbaora .


WORKED EXAMPLE

1his worked example assumes that you hae completed the ollowing steps.
Oracle Clusterware is installed.
Oracle RAC is installed.
\ou hae installed SAP and the SAPC1L package
ORA_CRS_lOML enironment ariable is set to your Oracle
Clusterware home.
\ou need to know the ollowing inormation about your SAP installation:
Required
Information
Description 1ypical Lxample
SAP_SID 1he name o the SAP Instance
containing the SAP serices
that require protection
RAC
interace 1he name o the public
network interace
eth0
netmask 1he IP network Netmask 255.255.240.0
IP address A new IP address that will be
bound to the public network
interace
212.16.1.233
user 1he SAP user sidadm racadm
hosting_members 1he list o nodes that are
capable o running the SAP
serices
sapnode1 sapnode2`
saphome 1he lome directory or the
SAP User sidadm
/saphome/racadm
enqueue_instance 1he name o the SAP enqueue
serice
ASCS01
replication_instance 1he name o the SAP
replication serice
ENR01


The SAPCTL utility

[root@oracx2 bin]# sapctl
Production Copyright 2005, 2006, Oracle. All rights reserved
USAGE:
sapctl <command> [<object>] -sapsid <SAP_SID> [options]
command : start|stop|status|config|create|remove|update
objects : all|enqueue|replication
NOTE:
create, remove, and update commands work on all objects only
For detailed help on each command and object and its options use:
sapctl <command> -h

Enable Oracle Clusterware Protection for your SAP resources

[root@oracx2 bin]# sapctl create -sapsid RAC -if eth0 nm 255.255.255.0
-ip 140.86.242.63 -u racadm
-n "oracx1 oracx2 oracw1 oracw2" -s /saphome/racadm -e ASCS01 -r ENR01
Creating SAP VIP
Creating SAP Enqueue resource
Creating SAP Replication resource
Done

In this case, the SAP Central Instance o the SAP system RAC owned by the SAP
user racadm is going to be protected, the SAP enqueue serice called ASCS0J and
the Replication serice called LNR0J will be allowed to run on separate nodes
rom the ollowing node list "oracxJ oracx2 oracwJ oracw2". A new irtual IP
address J40.86.242.63 with a subnet o 2SS.2SS.2SS.0 will be loaded onto the eth0
network adapter.

Running this command creates three Oracle Clusterware resources: An application
VIP, an Lnqueue resource and a Replication resource. 1he script does not
automatically start these resources.
To see which SAP Instances have been protected by Oracle Clusterware

[root@oracx2 bin]# sapctl config
SAP_SIDs protected by the Oracle Clusterware are :
RAC

In this case only one SAP Instance called 'RAC' is being protected by Oracle
Clusterware.
Modify the Standard SAP scripts

\ou must now modiy the standard SAP scripts to enable them to work with
Oracle Clusterware. See 'Appendix 1- Standard SAP Script Modiications'.

\ou must ensure that you complete this procedure beore attempting to start the
SAP resources that the Oracle Clusterware protects.

The sample SAP scripts must be
modified according to the details
in Appendix 1 of this paper
Check the Configuration

[root@oracx2 bin]# sapctl config all -sapsid RAC
CRS_HOME=/oracle/CRS/1020_32
Resource ID of SAP Enqueue service = ASCS01
Resource ID of SAP Replication service = ENR01
Location of CRS SAP scripts = /usr/sap/RAC/SYS/exe/run
SAP Home = /usr/sap/RAC
Hosting Members = oracx1 oracx2 oracw1 oracw2
Interface = eth0
Netmask = 255.255.255.0
IP Address = 140.86.242.63

\ou can check the coniguration alues or a protected SAP instance using the
conig parameter.

Check the Status of the Oracle Clusterware Protected SAP resources

[root@oracx2 bin]# sapctl status all -sapsid RAC
SAP Enqueue service is OFFLINE
SAP VIP is OFFLINE
SAP Replication service is OFFLINE

1o check the status o the Oracle Clusterware resources that protect the SAP
serices use the status command.
Start the Oracle Clusterware Protected SAP resources

[root@oracx2 bin]# sapctl start all -sapsid RAC
Starting SAP Enqueue service
Starting SAP VIP
Starting SAP Replication service
SAP Enqueue service is ONLINE on oracx1
SAP VIP is ONLINE on oracx1
SAP Replication service is ONLINE on oracx2
Done

Notice that you can use this command to start either the enqueue or replication
serices. loweer you should start the enqueue serice irst.
Check the Status after the start
SAP Replication service is ONLINE on oracx2

1he resource may take a short while to start. 1hereore, some resources may
indicate that they are OllLINL while they are being started.

Stop the Enqueue Service (and associated VIP)

[root@oracx2 bin]# sapctl stop enqueue -sapsid RAC
Stopping SAP Enqueue service
Stopping SAP VIP
SAP VIP is OFFLINE
Done
\ou can use the stop command to stop the Lnqueue serice. 1his will also stop the
associated VIP.
Start the Enqueue Service (and associated VIP)

[root@oracx2 bin]# sapctl start enqueue -sapsid RAC
Starting SAP Enqueue service
Starting SAP VIP
Done
\ou can use the start command to start the Lnqueue serice. 1his will also start the
associated VIP.
Change the Config

[root@oracx2 bin]# sapctl update
USAGE:
sapctl update -sapsid <SAP_SID> [-a <add_nodes>] [-d <delete_nodes>] [-
ip <IP_Address>]
\ou can use the update command to modiy the nodes that the Oracle Clusterware
protected SAP serices are allowed to run on. \ou can also use these commands
either to add or to delete nodes or to modiy the IP address o the Virtual IP
resource.
Stop all of the Oracle Clusterware managed SAP resources

[root@oracx2 bin]# sapctl stop all -sapsid RAC
Stopping SAP Enqueue service
Stopping SAP VIP
Stopping SAP Replication service
SAP VIP is OFFLINE
Done

\ou can choose to not stop all o the Oracle Clusterware resources by replacing all
with either 'enqueue' or 'replication' but you should stop the replication serice irst.
Check the Status after the stop

SAP VIP is OFFLINE

Ater stopping all o the Oracle Clusterware resources, you will see that they are all
marked as 'oline'.
Remove Oracle Clusterware protection for SAP resources

[root@oracx2 bin]# sapctl remove all -sapsid RAC
Removing resource SAP Enqueue service
Removing resource SAP VIP
Removing resource SAP Replication service
Done
Note you cannot remoe clusterware protection or a single resource. \ou must
remoe protection or all o the resources within an SAP instance in a single
operation. 1his command must be run as the 'root' user.

APPENDIX 1 STANDARD SAP SCRIPT MODIFICATIONS
1here are two scripts that require changing beore the Oracle Clusterware protected
resources can start.
Script Name Location
startsap ,usr,sap,SID,S\S,exe,run
stopsap ,usr,sap,SID,S\S,exe,run

Prior to modiying these scripts copies o original startsap and stopsap scripts
should be made. 1he original scripts should be copied to startsap.orig and
stopsap.orig.
Script: startsap
Location: ,usr,sap,SID,S\S,exe,run directory.

#!/bin/sh
#--------------------------------------------------------------------------
#
# @(#) $Id: //bc/620-1/src/ins/SAPINST/impl/tpls/ind/ind/startsap#22 $
#
# NAME :
# startsap

( ----- cut here ---)
.
set_db_running()
{
set_sapdbhost;

if [ "$DB_SID" ]; then

printf "\nChecking $DB_SID Database\n" | tee -a $LOGFILE
echo "------------------------------" | tee -a $LOGFILE

# preserve old values

# ora
dbs_ora_tmp=$dbs_ora_tnsname
dbs_ora_tnsname=${dbs_ora_tnsname-${SID}};export dbs_ora_tnsname

dbs_ora_tnsname=$DB_SID;export dbs_ora_tnsname

# ada
if test "$DBNAME";then
DBNAME_TMP=$DBNAME
fi

( ----- cut here ---)

#====================================================================
#
# FUNCTION: start_instance
#
# PURPOSE: starts the SAP instance
#

start_instance()
{

( ----- cut here ---)

# Set START_PROFILE
START_PROFILE=START_${INSTANCE}_${HOSTNAME}

# SET LOGFILE
LOGFILE=$R3S_LOGDIR/`basename ${0}_${INSTANCE}.log`

init_log $0 $*;

printf "\nStarting SAP Instance $INSTANCE\n" | tee -a $LOGFILE
echo "------------------------------" | tee -a $LOGFILE
echo " Startup-Log is written to $LOGFILE"

$SAPSTART pf=$PROFILE_DIR/$START_PROFILE >> $LOGFILE 2>&1
returncode=$?

Copies of the original scripts
should be made prior to these
changes.
Remove this :
Add this :
case $returncode in
0) echo " Instance on host $LOCAL_HOST started" | tee -a $LOGFILE
# START IGS
STARTIGS="/usr/sap/$SAPSYSTEMNAME/$INSTANCE/igs/bin/startigs"
STARTIGSCMD="/usr/sap/$SAPSYSTEMNAME/$INSTANCE/igs/bin/startigs -p
/usr/sap/$SAPSYSTEMNAME/$INSTANCE/igs"
if [ -f "$STARTIGS" ]; then
$STARTIGSCMD >> $LOGFILE 2>&1
IGSRETURN=$?
case $IGSRETURN in
0) echo " IGS on host $LOCAL_HOST started" | tee -a $LOGFILE;;
*) echo " Startup of IGS failed" | tee -a $LOGFILE
printf " See $LOGFILE for details\n\n";;
esac
fi
if [ "$SERVICE" = "CS" ]; then
sap2crs start $SAPSYSTEMNAME $SERVICE $INSTANCE
fi
if [ "$SERVICE" = "ER" ]; then
sap2crs start $SAPSYSTEMNAME $SERVICE $INSTANCE
fi;;
1) echo " Instance already running" | tee -a $LOGFILE;;
*) echo " Startup of Instance failed" | tee -a $LOGFILE
printf " See $LOGFILE for details\n\n"
exit 5;;
esac
}

( ----- cut here ---)

##################################
###############################
############################
#########################
###################### M A I N Procedure
###################
################
#############
##########

( ----- cut here ---)

# Acquire instance name from filesystem
set_instance

TASK="ALL"

elif [ $# -eq 2 ];then

INSTANCE=ècho $2 | awk '/SCS[0-9][0-9]/{print $1} /ASCS[0-9][0-9]/{print $1}
/DVEBMGS[0-9][0-9]/{print $1} /JC[0-9][0-9]/{print $1} /D[0-9][0-9]/{print $1}
/J[0-9][0-9]/{print $1} /G[0-9][0-9]/{print $1}'`

INSTANCE=ècho $2 | awk '/ENR[0-9][0-9]/{print $1} /ASCS[0-9][0-9]/{print $1}
/J[0-9][0-9]/{print $1} /G[0-9][0-9]/{print $1}'`

if [ -z "$INSTANCE" ]; then
ARGSREVERSED="YES"
INSTANCE=ècho $1 | awk '/SCS[0-9][0-9]/{print $1} /ASCS[0-9][0-9]/{print
$1} /DVEBMGS[0-9][0-9]/{print $1} /JC[0-9][0-9]/{print $1} /D[0-9][0-9]/{print
$1} /J[0-9][0-9]/{print $1} /G[0-9][0-9]/{print $1}'`

INSTANCE=ècho $1 | awk '/ENR[0-9][0-9]/{print $1} /ASCS[0-9][0-9]/{print
$1} /J[0-9][0-9]/{print $1} /G[0-9][0-9]/{print $1}'`
fi
if [ ! -f /usr/sap/$SAPSYSTEMNAME/SYS/profile/START_${INSTANCE}_${HOSTNAME}
];then
echo "start profile START_${INSTANCE}_${HOSTNAME} not found"
exit 8
fi

( ----- cut here ---)


Add this :
Remove this :
Add this :
Remove this :
Add this :
DVEBMGS[0-9][0-9]/{print $1} /JC[0-9][0-9]/{print $1} /D[0-9][0-9]/{print $1}
/J[0-9][0-9]/{print $1} /G[0-9][0-9]/{print $1}'``

/J[0-9][0-9]/{print $1} /G[0-9][0-9]/{print $1}'``

if [ ! -z "$INSTANCE" ]; then
TASK="ALL"
else
set_instance

( ----- cut here ---)

# Set SERVICE

if [ ! -z "ècho $SCS_INSTANCE | awk '/SCS[0-9][0-9]/{print $1}'`" ];then
SERVICE="CS_ONLY"
elif [ ! -z "ècho $ASCS_INSTANCE | awk '/ASCS[0-9][0-9]/{print $1}'`" ];then
SERVICE="CS_ONLY"
fi

if [ ! -z "ècho $INSTANCE | awk '/SCS[0-9][0-9]/{print $1}'`" ];then
SERVICE="CS"
elif [ ! -z "ècho $INSTANCE | awk '/ASCS[0-9][0-9]/{print $1}'`" ];then
SERVICE="CS"
elif [ ! -z "ècho $INSTANCE | awk '/ENR[0-9][0-9]/{print $1}'`" ];then
SERVICE="ER
elif [ ! -z "ècho $INSTANCE | awk '/DVEBMGS[0-9][0-9]/{print $1}'`" ];then
SERVICE="CI"
elif [ ! -z "ècho $INSTANCE | awk '/JC[0-9][0-9]/{print $1}'`" ];then
SERVICE="JCI"
elif [ ! -z "ècho $INSTANCE | awk '/D[0-9][0-9]/{print $1}'`" ];then
SERVICE="DI"
elif [ ! -z "ècho $INSTANCE | awk '/J[0-9][0-9]/{print $1}'`" ];then
SERVICE="JDI"
elif [ ! -z "ècho $INSTANCE | awk '/G[0-9][0-9]/{print $1}'`" ];then
SERVICE="GW"
fi
if [ "$TRACE" ]; then
echo "SERVICE=$SERVICE"
fi

if [ -z "$SERVICE" ]; then
echo "Unknown instance type!"
exit 8
fi

Remove this :
Add this :
Add this :
Script: stopsap
Location: ,usr,sap,SID,S\S,exe,run directory.

#!/bin/sh
#--------------------------------------------------------------------------
#
# @(#) $Id: //bc/620-1/src/ins/SAPINST/impl/tpls/ind/ind/stopsap#16 $
#
# NAME :
# stopsap

( ----- cut here ---)

stop_instance()
{

( ----- cut here ---)

# STOP INSTANCE
if [ "$SERVICE" = "CS" ]; then
sap2crs stop $SAPSYSTEMNAME $SERVICE $INSTANCE
fi

if [ "$SERVICE" = "ER" ]; then
sap2crs stop $SAPSYSTEMNAME $SERVICE $INSTANCE
fi

if [ -f /usr/sap/$SAPSYSTEMNAME/$INSTANCE/work/kill.sap ]; then
eval sh /usr/sap/$SAPSYSTEMNAME/$INSTANCE/work/kill.sap >> $LOGFILE 2>&1
returncode=$?

( ----- cut here ---)

#====================================================================
##################################
###############################
############################
#########################
###################### M A I N Procedure
###################
################
#############
##########

( ----- cut here ---)

# Evaluate command line options, set INSTANCE and TASK

if [ $# -eq 0 ];then

set_instance

TASK="ALL"


/J[0-9][0-9]/{print $1} /G[0-9][0-9]/{print $1}'`

/J[0-9][0-9]/{print $1} /G[0-9][0-9]/{print $1}'`
if [ -z "$INSTANCE" ]; then
ARGSREVERSED="YES"
INSTANCE=ècho $1 | awk '/SCS[0-9][0-9]/{print $1} /ASCS[0-9][0-9]/{print
$1} /J[0-9][0-9]/{print $1} /G[0-9][0-9]/{print $1}'``

INSTANCE=ècho $1 | awk '/ENR[0-9][0-9]/{print $1} /ASCS[0-9][0-9]/{print
$1} /J[0-9][0-9]/{print $1} /G[0-9][0-9]/{print $1}'`
fi
if [ ! -f /usr/sap/$SAPSYSTEMNAME/SYS/profile/START_${INSTANCE}_${HOSTNAME}
];then
echo "start profile START_${INSTANCE}_${HOSTNAME} not found"
exit 8
fi

( ----- cut here ---)

elif [ $# -gt 2 ];then
Add this :
Remove this :
Add this :
Remove this :
Add this :

echo " Too many arguments..."
echo " Usage: `basename $0` [db|r3|j2ee|all|check] [<instance>]"
echo " Specify instance if you have installed multiple"
echo " instances of the same system on one host."
echo " Example: `basename $0` r3 DVEBMGS00"
exit 2


/J[0-9][0-9]/{print $1} /G[0-9][0-9]/{print $1}'`

( ----- cut here ---)

# Set SERVICE

if [ ! -z "ècho $SCS_INSTANCE | awk '/SCS[0-9][0-9]/{print $1}'`" ];then
SERVICE="CS_ONLY"
elif [ ! -z "ècho $ASCS_INSTANCE | awk '/ASCS[0-9][0-9]/{print $1}'`" ];then
SERVICE="CS_ONLY"
fi

if [ ! -z "ècho $INSTANCE | awk '/SCS[0-9][0-9]/{print $1}'`" ];then
SERVICE="CS"
elif [ ! -z "ècho $INSTANCE | awk '/ASCS[0-9][0-9]/{print $1}'`" ];then
SERVICE="CS"
elif [ ! -z "ècho $INSTANCE | awk '/ENR[0-9][0-9]/{print $1}'`" ];then
SERVICE="ER"
elif [ ! -z "ècho $INSTANCE | awk '/DVEBMGS[0-9][0-9]/{print $1}'`" ];then
SERVICE="CI"
elif [ ! -z "ècho $INSTANCE | awk '/JC[0-9][0-9]/{print $1}'`" ];then
SERVICE="JCI"
elif [ ! -z "ècho $INSTANCE | awk '/D[0-9][0-9]/{print $1}'`" ];then
SERVICE="DI"
elif [ ! -z "ècho $INSTANCE | awk '/J[0-9][0-9]/{print $1}'`" ];then
SERVICE="JDI"
elif [ ! -z "ècho $INSTANCE | awk '/G[0-9][0-9]/{print $1}'`" ];then
SERVICE="GW"
fi
if [ "$TRACE" ]; then
echo "SERVICE=$SERVICE"
fi

if [ -z $SERVICE ]; then
echo "Unknown instance type!"
exit 8
fi
Add this :
APPENDIX 2 SAMPLE PROFILE SCRIPTS - ENQUEUE SERVICE (ASC)
1he ollowing is an example o the proile scripts or a standalone Lnqueue Serice
on a two-node cluster. 1he hostnames o the cluster nodes are oracx1 and oracx2
in this example.
RAC_ASCS01_oracx1 ,usr,sap,RAC,S\S,proile
RAC_ASCS01_oracx2 ,usr,sap,RAC,S\S,proile
S1AR1_ASCS01_oracx1 ,usr,sap,RAC,S\S,proile
S1AR1_ASCS01_oracx2 ,usr,sap,RAC,S\S,proile

Script: RAC_ASCS01_oracx1
Location: ,usr,sap,RAC,S\S,proile directory.

SAPLOCALHOST=oracx1
SAPLOCALHOSTFULL=oracx1.de.oracle.com
INSTANCE_NAME=ASCS01
SAPSYSTEM=02
SAPSYSTEMNAME=RAC
rdisp/myname=oracx1_RAC_01
rdisp/mshost=ora_sap_vip
enque/table_size=4096
enque/process_location=LOCAL
enque/server/internal_replication=true
enque/server/replication=true
enque/enrep/keepalive_count=0
#for performance tuning
enque/server/threadcount=1
# these are needed to prevent the pools from being created
ipc/shm_psize_16=0
ipc/shm_psize_24=0
ipc/shm_psize_34=0
ipc/shm_psize_66=0

Script: RAC_ASCS01_oracx2

SAPLOCALHOST=oracx2
INSTANCE_NAME=ASCS01
SAPSYSTEM=02
SAPSYSTEMNAME=RAC
rdisp/myname=oracx2_RAC_01
ipc/shm_psize_16=0
ipc/shm_psize_24=0
ipc/shm_psize_34=0
ipc/shm_psize_66=0
Script: START_ASCS01_oracx1

#.******************************************************************************
#.* *
#.* Start profile START_ASCS01_oracx1
#.* *
#.******************************************************************************
#-----------------------------------------------------------------------
SAPSYSTEM =00
SAPSYSTEMNAME =RAC
INSTANCE_NAME =ASCS01

#-----------------------------------------------------------------------
# start SCSA administration
#-----------------------------------------------------------------------

Execute_00 =local $(DIR_EXECUTABLE)/sapmscsa -n
pf=$(DIR_PROFILE)/RAC_ASCS01_oracx1

#-----------------------------------------------------------------------
# start syslog send daemon
#-----------------------------------------------------------------------

_SE =se.sapRAC_ASCS01_oracx1
Execute_01 =local ln -s -f $(DIR_EXECUTABLE)/rslgsend $(_SE)
Start_Program_01 =local $(_SE) -F pf=$(DIR_PROFILE)/RAC_ASCS01_oracx1

#-----------------------------------------------------------------------
# start syslog collector daemon
#-----------------------------------------------------------------------

_CO =co.sapRAC_ASCS01_oracx1
Execute_02 =local ln -s -f $(DIR_EXECUTABLE)/rslgcoll $(_CO)
Start_Program_02 =local $(_CO) -F pf=$(DIR_PROFILE)/RAC_ASCS01_oracx1

#-----------------------------------------------------------------------
# start message server
#-----------------------------------------------------------------------

_MS =ms.sapRAC_ASCS01_oracx1
Execute_03 =local ln -s -f $(DIR_EXECUTABLE)/msg_server $(_MS)
Start_Program_03 =local $(_MS) pf=$(DIR_PROFILE)/RAC_ASCS01_oracx1

#-----------------------------------------------------------------------
# start enqueue server
#-----------------------------------------------------------------------

_EN =en.sapRAC_ASCS01_oracx1
Execute_04 =local ln -s -f $(DIR_EXECUTABLE)/enserver $(_EN)
Start_Program_04 =local $(_EN) pf=$(DIR_PROFILE)/RAC_ASCS01_oracx1

#-----------------------------------------------------------------------
Script: START_ASCS01_oracx2

#.******************************************************************************
#.* *
#.* Start profile START_ASCS01_oracx2
#.* *
#.******************************************************************************
#-----------------------------------------------------------------------
SAPSYSTEM =00
SAPSYSTEMNAME =RAC
INSTANCE_NAME =ASCS01

#-----------------------------------------------------------------------
# start SCSA administration
#-----------------------------------------------------------------------

Execute_00 =local $(DIR_EXECUTABLE)/sapmscsa -n
pf=$(DIR_PROFILE)/RAC_ASCS01_oracx2

#-----------------------------------------------------------------------
# start syslog send daemon
#-----------------------------------------------------------------------

_SE =se.sapRAC_ASCS01_oracx2
Execute_01 =local ln -s -f $(DIR_EXECUTABLE)/rslgsend $(_SE)
Start_Program_01 =local $(_SE) -F pf=$(DIR_PROFILE)/RAC_ASCS01_oracx2

#-----------------------------------------------------------------------
# start syslog collector daemon
#-----------------------------------------------------------------------

_CO =co.sapRAC_ASCS01_oracx2
Execute_02 =local ln -s -f $(DIR_EXECUTABLE)/rslgcoll $(_CO)
Start_Program_02 =local $(_CO) -F pf=$(DIR_PROFILE)/RAC_ASCS01_oracx2

#-----------------------------------------------------------------------
# start message server
#-----------------------------------------------------------------------

_MS =ms.sapRAC_ASCS01_oracx2
Execute_03 =local ln -s -f $(DIR_EXECUTABLE)/msg_server $(_MS)
Start_Program_03 =local $(_MS) pf=$(DIR_PROFILE)/RAC_ASCS01_oracx2

#-----------------------------------------------------------------------
# start enqueue server
#-----------------------------------------------------------------------

_EN =en.sapRAC_ASCS01_oracx2
Execute_04 =local ln -s -f $(DIR_EXECUTABLE)/enserver $(_EN)
Start_Program_04 =local $(_EN) pf=$(DIR_PROFILE)/RAC_ASCS01_oracx2

#-----------------------------------------------------------------------

APPENDIX 3 SAMPLE PROFILE SCRIPTS - REPLICATION SERVICE
(ENR)
1he ollowing is an example o the proile scripts or a standalone Replication
Serice on a two-node cluster. 1he hostnames o the cluster nodes are oracx1 and
oracx2 in this example.

RAC_LNR01_oracx1 ,usr,sap,RAC,S\S,proile
RAC_LNR01_oracx2 ,usr,sap,RAC,S\S,proile
S1AR1_LNR01_oracx1 ,usr,sap,RAC,S\S,proile
S1AR1_LNR01_oracx2 ,usr,sap,RAC,S\S,proile

Script: RAC_ENR01_oracx1

SAPLOCALHOST=oracx1
INSTANCE_NAME=ENR01
SAPSYSTEM=02
SAPSYSTEMNAME=RAC
rdisp/myname=oracx1_ENR_01
ipc/shm_psize_16=0
ipc/shm_psize_24=0
ipc/shm_psize_34=0
ipc/shm_psize_66=0

Script: RAC_ENR01_oracx2

SAPLOCALHOST=oracx2
INSTANCE_NAME=ENR01
SAPSYSTEM=02
SAPSYSTEMNAME=RAC
rdisp/myname=oracx2_ENR_01
ipc/shm_psize_16=0
ipc/shm_psize_24=0
ipc/shm_psize_34=0
ipc/shm_psize_66=0

Script: START_ENR01_oracx1

#.******************************************************************************
#.* *
#.* Startprofil START_ENR01_oracx1
#.* *
#.******************************************************************************
#-----------------------------------------------------------------------
SAPSYSTEMNAME =RAC
INSTANCE_NAME =ENR01

#-----------------------------------------------------------------------
# start enqueue replication server
#-----------------------------------------------------------------------

_ENR =enr.sapRAC_ENR01_oracx1
Execute_01 =local ln -s -f $(DIR_EXECUTABLE)/enrepserver $(_ENR)
Start_Program_01 =local $(_ENR) pf=$(DIR_PROFILE)/RAC_ENR01_oracx1

#-----------------------------------------------------------------------

Script: START_ENR01_oracx2

#.******************************************************************************
#.* *
#.* Startprofil START_ENR01_oracx2
#.* *
#.******************************************************************************
#-----------------------------------------------------------------------
SAPSYSTEMNAME =RAC
INSTANCE_NAME =ENR01

#-----------------------------------------------------------------------
# start enqueue replication server
#-----------------------------------------------------------------------

_ENR =enr.sapRAC_ENR01_oracx2
Execute_01 =local ln -s -f $(DIR_EXECUTABLE)/enrepserver $(_ENR)
Start_Program_01 =local $(_ENR) pf=$(DIR_PROFILE)/RAC_ENR01_oracx2

#-----------------------------------------------------------------------

APPENDIX 4 TROUBLESHOOTING AND LOG FILES

1he troubleshooting content in this section assumes that you are amiliar with the
Oracle Clusterware and SAP R,3 commands. \ou can troubleshoot SAPC1L by
examining the log iles as described in this section.

1he ollowing is the log o the actions that SAPC1L perorms. \ou should also
check to see which commands were executed:

/usr/sap/${SAP_SID}/sapctl.log

I you cannot resole your problem, then examine the ollowing log ile to
determine why resource actions do not perorm as expected:

/usr/sap/${SAP_SID}/crs.log

\ou can also examine the ollowing ile to troubleshoot issues with VIP resources:

${ORA_CRS_HOME}/log/<hostname>/racg/sap.${SAP_SID}.vip.log

In addition to the ip.log ile, you can also examine the content o the CRSD log
ile:

${ORA_CRS_HOME}/log/<hostname>/crsd/crsd.log


APPENDIX 5 - SAPCTL BILL OF MATERIALS
1his section describes the SAPC1L bill o materials ,BOM,. 1he un-compressed
tar ile contains the ollowing items:
.,bin,sapctl - 1his is a shell script that runs bin,sapctl.pl, it is included or
conenience.
.,bin,sapctl.pl - 1his is a Perl-based SAPC1L management utility
implementation.
.,doc,sapctl.doc - 1his is a copy o this document.
.,templates,crssapactions.pl.sbs - 1his is a template or the action perl
script used internally by SAPC1L.
.,templates,sap2crs.sbs - 1his is a template or the 'SAP to crs` proxy
script used internally by SAPC1L.
.,templates,sapwrap.sbs - 1his is a template or the action script wrapper
used internally by SAPC1L.

Providing High Availability for SAP Resources
April 2006
Version 1.0
Authors: David Austin, Mark Bauer, Andrey Gusev, Kurt Broeg, and Rajiv Jayaraman
Contributing Authors: Philip Newlan

Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores, CA 94065
U.S.A.

Worldwide Inquiries:
Phone: +1.650.506.7000
Fax: +1.650.506.7200
oracle.com

Copyright 2006, Oracle. All rights reserved.
This document is provided for information purposes only and the
contents hereof are subject to change without notice.
This document is not warranted to be error-free, nor subject to any
other warranties or conditions, whether expressed orally or implied
in law, including implied warranties and conditions of merchantability
or fitness for a particular purpose. We specifically disclaim any
liability with respect to this document and no contractual obligations
are formed either directly or indirectly by this document. This document
may not be reproduced or transmitted in any form or by any means,
electronic or mechanical, for any purpose, without our prior written permission.
Oracle, JD Edwards, and PeopleSoft, are registered trademarks of Oracle
Corporation and/or its affiliates. Other names may be trademarks
of their respective owners.

Sap Availability On Rac TWP 133712

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Sap Availability On Rac TWP 133712

Uploaded by

Copyright:

Available Formats

Proiding ligh Aailability or

You might also like