An Oracle White Paper June 2013

Installation and Configuration of SAP HA ASCS/ERS Instances on the Oracle Database Appliance

A Best Practices Guide

Installation Prerequisites........................................................................ 3 ASCS Installation................................................................................... 4 ERS Installation...................................................................................... 5 Additional HA Specific Steps.................................................................. 9

Installation Prerequisites As the first step in installing a high-availability SAP system distributed over several hosts, you must install the ASCS instance on a shared disk. On the Oracle Database Appliance we use the ACFS file system for the shared disk. Therefore verify that /sapmnt and /usr/sap/ are configured on ACFS and distributed via NFS to all involved servers. The ASCS instance has its own virtual IP address or virtual hostname. This IP address is managed by the Oracle Clusterware . During the installation of ASCS the SAP installer must be able to resolve this IP Address. The Oracle Clusterware resource control program crsctl starts and stops an IP address. Example: [root@lsoda01 sap]# /u01/app/11.2.0.3/grid/bin/crsctl start ip -A ascs-vip/255.255.252.0/bond0 [root@lsoda01 sap]# ifconfig -a | grep bond0 bond0 Link encap:Ethernet HWaddr 00:21:28:F1:36:8C bond0:1 Link encap:Ethernet HWaddr 00:21:28:F1:36:8C bond0:2 Link encap:Ethernet HWaddr 00:21:28:F1:36:8C bond0:3 Link encap:Ethernet HWaddr 00:21:28:F1:36:8C xbond0 Link encap:Ethernet HWaddr 90:E2:BA:05:DF:C0 [root@lsoda01 sap]# ifconfig -a bond0:3 bond0:3 Link encap:Ethernet HWaddr 00:21:28:F1:36:8C inet addr:10.20.91.107 Bcast:10.20.91.255 Mask:255.255.252.0 UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1

Server: 10.17.121.30 Address: 10.17.121.30#53 Name: ascs-vip.wdf.sap.corp Address: 10.20.91.43 [root@ascs-vip]#

Before starting the installation, make sure that you have identified the required scenario as described in the Master Guide of SAP’s Software Provisioning Manager.

ASCS Installation With the virtual hostname the SAP installation can be started to install ASCS. [root@lsoda01 sap]# sapinst SAPINST_USE_HOSTNAME=ascs-vip

We do not show all installation steps, only the initial entry.

ERS Installation After successfully finishing the ASCS installation the next step will be the installation of the Enqueue Replication Server Instance ERS. ERS must be installed on all nodes using the local hostname, which is the default of SAPinst. So just call SAPinst without any runstring parameter.

When you have finished the installation on the first cluster node continue installing ERS instance on the second cluster node.

Additional HA Specific Steps To prepare the system for switching over the ASCS instance we need to do additional steps. ASCS is installed on a shared file system (ACFS) therefore it is available on all nodes, but only registered on the first node. For the registration use the following steps. On the first node (the installation node of ASCS) stop ASCS: lsoda01:os1adm 102> sapcontrol -nr 00 -function Stop

On the first node (the installation node of ASCS) stop service ASCS: sapcontrol -nr 00 -function StopService

Stop the virtual IP address on the first node: [root@lsoda01 inst_ERS]# crsctl stop ip -A ascs-vip/bond0

Start the virtual IP address on the second node: [root@lsoda02 inst_ERS]# crsctl start ip -A ascs-vip/255.255.252.0/bond0

With the switched virtual IP address we register the ASCS instance on the second node: [root@lsoda02 inst_ERS]# /usr/sap/hostctrl/exe/saphostctrl -function RegisterInstanceService -sid OS1 -nr 00 -saplocalhost ascs-vip Webmethod returned successfully Operation ID: 002128F134F81ED2B69FA9DB436E93DF ----- Log messages ---Info: saphostcontrol: Executing 'sapstartsrv' Info: saphostcontrol: 'sapstartsrv' successfully executed Info: saphostcontrol: Executing 'sapstartsrv' Info: saphostcontrol: 'sapstartsrv' successfully executed [root@lsoda02 inst_ERS]#

During registration SAP customizes the shell script /etc/init.d/sapinit. This service script starts all sapstartservices at boot time. To verify services are started use the command below: [root@lsoda02 inst_ERS]# ps -ef | grep sap os1adm 7089 1 0 Jun19 ? 00:00:04 /usr/sap/OS1/ASCS00/exe/sapstartsrv pf=/usr/sap/OS1/SYS/profile/START_ASCS00_ascs-vip –D os1adm 9175 1 0 Jun19 ? 00:00:03 /usr/sap/OS1/ERS10/exe/sapstartsrv pf=/usr/sap/OS1/ERS10/profile/START_ERS10_lsoda02 -D -u os1adm root 7698 1 0 Jun19 ? 00:00:00 /usr/sap/hostctrl/exe/saphostexec pf=/usr/sap/hostctrl/exe/host_profile sapadm 7701 1 0 Jun19 ? 00:00:02 /usr/sap/hostctrl/exe/sapstartsrv pf=/usr/sap/hostctrl/exe/host_profile -D root 8827 1 0 Jun19 ? 00:01:57 /usr/sap/hostctrl/exe/saposcol -l -w60 pf=/usr/sap/hostctrl/exe/host_profile

To guarantee that the ASCS and ERS services will not be started during system boot, we need to comment out some lines in the file /etc/init.d/sapinit on both nodes as Oracle Clusterware takes care of the start and stop. First stop the operating system services sapinit using: [root@lsoda02 inst_ERS]#/etc/init.d/sapinit stop

Then edit the file /etc/init.d/sapinit and comment out the lines below. 425 # 426 # Implements the start 427 # 428 start() { 429 setup_limit 430 431 current_dir=`pwd` 432 if [ -x "${HOSTEXEC_PATH}" ]; then 433 ${HOSTEXEC_PATH} pf=${HOSTEXEC_PROFILE_PATH} 434 fi 435 436 read_sapservices 437 438 ##### for index in `${SEQ_CMD} 0 $((${#g_commands[@]} - 1))` 439 ##### do 440 ##### vv=`sh -c "${g_commands[index]}"` 441 ##### if [ -n "$vv" ]; then 442 ##### echo "failed to start ${g_commands[index]}: $vv" 443 ##### fi 444 ##### done 445 446 cd ${current_dir} 447 unset vv 448 unset index

Start the service sapinit again: [root@lsoda02 init.d]# ./sapinit start Control that the ASCS and ERS services are not started: [root@lsoda02 init.d]# ps -ef | grep sap root 32458 1 0 16:12 ? 00:00:00 /usr/sap/hostctrl/exe/saphostexec pf=/usr/sap/hostctrl/exe/host_profile sapadm 32509 1 0 16:12 ? 00:00:00 /usr/sap/hostctrl/exe/sapstartsrv pf=/usr/sap/hostctrl/exe/host_profile -D root 32600 1 0 16:12 ? 00:00:00 /usr/sap/hostctrl/exe/saposcol -l -w60 pf=/usr/sap/hostctrl/exe/host_profile root 32667 16917 0 16:12 pts/0 00:00:00 grep sap

Please do not forget to comment out the lines as explained above in /etc/init.d/sapinst on the second node. With the program sapcontrol you can start and stop the services and instances ASCS and ERS: sapcontrol sapcontrol sapcontrol sapcontrol

–nr –nr –nr –nr

-function StartService -function StopService -function Start -function Stop

Installation and Configuration of the SAP HA ASCS/ERS Instances on the Oracle Database Appliance June 2013

Copyright © 2013, Oracle and/or its affiliates. All rights reserved. This document is provided for

Author: Martin Sautter

information purposes only and

Contributing Authors: Jan

the contents hereof are subject to change without notice. This document is not warranted to be

Klokkers

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

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

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 Corporation

Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be

World Headquarters

trademarks of their respective owners.

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

0613