Managing Serviceguard Extension for SAP on Integrity Linux Manufacturing Part Number: T2392-90001 December 2005
Legal Notices Copyright © 2005 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, nd Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. The information contained herein is subject to change without notice.
Contents 1. Understanding Serviceguard Extension for SAP on Integrity Linux Overview of SGeSAP on Integrity Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . One-Package Configuration Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Two-Package Configuration Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Central NFS Configuration Model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 4
Printing History Table 1 Editions and Releases Printing Date Part Number Edition SAP kernel release Operating System Releases December 2005 T2392-90001 First SAP kernel 4.6, 6.20, 6.40 ABAP only SuSE Linux Enterprise Server (SLES) 9 SP2 The printing date and part number indicate the current edition. The printing date changes when a new edition is printed. (Minor corrections and updates which are incorporated at reprint do not cause the date to change.
About this Manual... This document describes how to configure and install highly available SAP systems on Integrity Linux using Serviceguard. It refers to the HP product T2392AA – Serviceguard Extension for SAP on Integrity Linux.
Table 2 lists abbreviations used in this manual: Table 2 Abbreviations Abbreviation Meaning , System ID of the SAP system in uppercase/lowercase instance number of the SAP system , , names mapped to the local hostnames (output of uname -n) , , names mapped to local IP addresses of the client LAN , , names mapped to relocatable IP addresses of Serviceguard packages in the client LAN
Related Documentation The following documents contain additional related information: 8 • Serviceguard Extension for SAP on Integrity Linux Release Notes (Part Number T2392-90002). • Managing Serviceguard 11.16 for Linux (Part Number B9903-900xx) • Serviceguard for Linux Version A.11.16 Release Notes (Part Number B9903-900xx) • Managing Serviceguard NFS for Linux (Part Number T1442-900xx) • Serviceguard NFS for Linux Version A.01.02 Release Notes (Part Number T1442-900xx) • SAP WAS 6.
Understanding Serviceguard Extension for SAP on Integrity Linux 1 Understanding Serviceguard Extension for SAP on Integrity Linux HP Serviceguard Extension for SAP on Integrity Linux (SGeSAP/LX IPF) extends Serviceguard's powerful failover capabilities to SAP environments. It continuously monitors the health of each SAP node and automatically responds to failures or threshold violations. It can also minimize planned downtime when performing SAP upgrades.
Understanding Serviceguard Extension for SAP on Integrity Linux Overview of SGeSAP on Integrity Linux Overview of SGeSAP on Integrity Linux SAP environments allows a great amount of flexibility in setup and configuration.
Understanding Serviceguard Extension for SAP on Integrity Linux Overview of SGeSAP on Integrity Linux A sample configuration in Figure 1-1 shows node1 with a failure, which causes the package containing the database and central instance to fail over to node2. Figure 1-1 One-Package Failover Scenario Serviceguard for Linux Cluster DB and CI in one package Shared Disk node2 node1 DB/CI Pkg DB and CI package move to another node in in the event of a failure.
Understanding Serviceguard Extension for SAP on Integrity Linux Overview of SGeSAP on Integrity Linux Two-Package Configuration Model If you are planning to distribute the database and central instance between two nodes, use the two-package model. The SAP functionality is separated into two Serviceguard packages, one for the database (DB) and the other for the SAP central instance (CI). The database package contains the filesystems for the NFS mount points.
Understanding Serviceguard Extension for SAP on Integrity Linux Overview of SGeSAP on Integrity Linux If either node1 or node2 fails, the package can fail over to node3. If a failover to a node that is not idle takes place (for example if node3 were used as an application server), SGeSAP/LX IPF, if requested, can bring down running instances to free the resources needed to get the system up.
Understanding Serviceguard Extension for SAP on Integrity Linux Overview of SGeSAP on Integrity Linux Central NFS Configuration Model The one-package as well as the two-package configuration model can be combined with a central NFS package furtheron referred to as SAPNFS package. In this case, the DB or DBCI package no longer blends the HA NFS functionality with the database failover functionality.
Understanding Serviceguard Extension for SAP on Integrity Linux Application Servers Application Servers The database and the SAP central instance are always running on nodes that are protected by Serviceguard. Other SAP services can be run on Linux application server hosts. These hosts can be but must not need to be part of the Serviceguard cluster. If the additional SAP application servers are run on nodes inside the Serviceguard for Linux cluster, they can be protected by Serviceguard for Linux.
Understanding Serviceguard Extension for SAP on Integrity Linux Application Servers For all application server nodes outside the Serviceguard for Linux cluster, refer to the following for each of the SAP services: 16 • Dialog—Logon using saplogon for an application server groups instead of sapgui for each individual application server.
Understanding Serviceguard Extension for SAP on Integrity Linux Highly Available NFS Highly Available NFS Distributed SAP environments require the Network File System (NFS) to be highly available. SGeSAP/LX IPF packages can be combined with the Serviceguard NFS toolkit for Linux to achieve this functionality. Typically, the SGeSAP/LX IPF database package also provides HA NFS functionality.
Understanding Serviceguard Extension for SAP on Integrity Linux Networking Networking Communication with the highly available components takes place by using special IP addresses, called relocatable IP addresses. They are handled by Serviceguard for Linux. Consider them as addresses of a Serviceguard package rather than host machine addresses. Some of the SAP processes still require that hostnames are not longer than eight characters and do not contain special characters.
Understanding Serviceguard Extension for SAP on Integrity Linux Planning the LVM Layout for Clustered SAP Environments Planning the LVM Layout for Clustered SAP Environments This section provides a general discussion of the SGeSAP for Integrity Linux cluster directory and volume group layout.
Understanding Serviceguard Extension for SAP on Integrity Linux Planning the LVM Layout for Clustered SAP Environments • the SAP System ID of the referred SAP component in uppercase. • the SAP System ID of the referred SAP component in lowercase. • a database System ID; usually identical to a . • SAP Instance Number of the referred SAP instance. • relocatable IP address of a CI package on a client subnet.
Understanding Serviceguard Extension for SAP on Integrity Linux Planning the LVM Layout for Clustered SAP Environments packages will then lead to a lack of necessary NFS ressources for otherwise unrelated SAP Systems. The SAPNFS package avoids this unpleasant dependency. It is an option to move the system specific volume groups to the SAPNFS package. This can be done, to keep HA NFS mechanisms completely separate.
Understanding Serviceguard Extension for SAP on Integrity Linux Planning the LVM Layout for Clustered SAP Environments NOTE This filesystem layout closely relates to the SAP installation recommendations. A major difference is the addition of an instance specific /usr/sap//DVEBMGS and /usr/sap//D mountpoints that allow to move instance specific data with the Serviceguard instance package.
Understanding Serviceguard Extension for SAP on Integrity Linux Planning the LVM Layout for Clustered SAP Environments latest executables that were stored centrally with those stored locally and copies all required updates. Figure 1-3 shows the filesystem layout with sapcpe.
Understanding Serviceguard Extension for SAP on Integrity Linux Planning the LVM Layout for Clustered SAP Environments Oracle LVM Layout All ORACLE server directories reside below /oracle/. These directories get shared via the database package. In addition, any SAP Application Server needs access to the Oracle client libraries, including the Oracle National Language Support files (NLS) shown in Table 1-2.
Understanding Serviceguard Extension for SAP on Integrity Linux Planning the LVM Layout for Clustered SAP Environments Oracle 9.x releases no longer maintain NLS compatibility with Oracle 8.x. Also, Oracle 9.x patches introduce incompatibilities with older Oracle 9.x NLS files. The following constraints need to be met: 1. The Oracle RDBMS and database tools rely on an ORA_NLS[] setting that refers to NLS files that are compatible to the version of the RDBMS. Oracle 9.
Understanding Serviceguard Extension for SAP on Integrity Linux Planning the LVM Layout for Clustered SAP Environments Table 1-3 Filesystem Layout for ORACLE Clusters Mount Point Access Point Potential Owning Packages Possible Volume Group Volume Group Type shared disk db dbci vgdb vgdbci db instance specific /oracle/client local none vg02 environment specific some local ORACLE client files reside in /oracle/ as part of the root filesystem local vg00 db insta
Understanding Serviceguard Extension for SAP on Integrity Linux Planning the LVM Layout for Clustered SAP Environments SAPDB LVM Layout SAPDB distinguishes an instance dependant path /sapdb/ and two instance independent paths, such as IndepData and IndepPrograms. By default all three point to a directory below /sapdb. An overview of the current settings can be viewed at the file /var/spool/sql/ini/SAP_DBTech.ini. The following is a sample SAP_DBTech.ini for a host with a SAPDB 7.
Understanding Serviceguard Extension for SAP on Integrity Linux Planning the LVM Layout for Clustered SAP Environments NOTE The [Globals] section is commonly shared between LC1 and AP1. This prevents setups that keep the directories of LC1 and AP1 completely separated. The following directories are of special interest: 28 • /sapdb/programs: this can be seen as a central directory with all SAPDB/Livecache executables.
Understanding Serviceguard Extension for SAP on Integrity Linux Planning the LVM Layout for Clustered SAP Environments needs to be configured for the shared logical volume to allow core dumps. It is also obvious, that files of that size should not be transferred via NFS. • /var/spool/sql: This directory hosts local runtime data of all locally running SAPDB/Livecache instances. Most of the data in this directory would become meaningless in the context of a different host after failover.
Understanding Serviceguard Extension for SAP on Integrity Linux Planning the LVM Layout for Clustered SAP Environments Database and SAP instances depend on the availability of /sapdb/programs.
Understanding Serviceguard Extension for SAP on Integrity Linux Planning the LVM Layout for Clustered SAP Environments SGeSAP/LX IPF Filestructure The Linux distribution of Serviceguard uses a special file, /etc/cmcluster.conf, to define the locations for configuration and log files within the Linux filesystem. These paths differ depending on the Linux distribution used. In this document, references to ${SGCONF} can be replaced by the definition of the prefix that is found in this file.
Understanding Serviceguard Extension for SAP on Integrity Linux Planning the LVM Layout for Clustered SAP Environments Figure 1-5 shows the Serviceguard control files containing run-time logic used to generate the SAP specific files. Figure 1-5 Control Files Containing Run-time Logic Serviceguard SAP Specific One pkg dbci.sh or sapdbci.sh or + sap.config sap.functions customer.functions Two pkg db.sh ci.sh 32 sapdb.sh sapci.
Understanding Serviceguard Extension for SAP on Integrity Linux Planning the LVM Layout for Clustered SAP Environments Package Directory Content for the One-Package Model In the one package model, the SAP functionality-database and central instance-along with the highly available NFS server are all been placed in one Serviceguard package. The SGeSAP/LX IPF scripts of the one package concept are organized as follows: Chapter 1 • ${SGCONF}/sg.conf - cluster configuration file of Serviceguard.
Understanding Serviceguard Extension for SAP on Integrity Linux Planning the LVM Layout for Clustered SAP Environments • ${SGCONF}//dbcitoolkit.sh - contains NFS specific flowlogic for package startup and package shutdown. It is optional, if a central HA NFS package is used. • ${SGCONF}/sap.functions - contains all standard runtime logic used by one package and two package configurations. Do not modify this file! • ${SGCONF}//customer.
Understanding Serviceguard Extension for SAP on Integrity Linux Planning the LVM Layout for Clustered SAP Environments Package Directory Content for the Two-Package Model In the two package model, the SAP functionality is separated into two Serviceguard packages. One for the database (DB) and the other for the SAP central instance (CI). The database package contains the filesystems for the NFS mount points.
Understanding Serviceguard Extension for SAP on Integrity Linux Planning the LVM Layout for Clustered SAP Environments 36 • ${SGCONF}//sapci.sh - contains SAP specific flowlogic for central instance package startup and shutdown. This file is valid for two package configurations only. It depends on /sap.config, /customer.functions, and sap.functions. • ${SGCONF}//sapapp.sh - contains flowlogic for a SAP application server package startup and shutdown. It depends on /sap.
Understanding Serviceguard Extension for SAP on Integrity Linux Planning the LVM Layout for Clustered SAP Environments Figure 1-6 illustrates the required configuration files, and the questions they answer, for an SGeSAP/LX IPF application package in Serviceguard.
Understanding Serviceguard Extension for SAP on Integrity Linux Planning the LVM Layout for Clustered SAP Environments The SGeSAP/LX IPF files work in tandem with standard Serviceguard files to monitor the health of the cluster and packages, and to move packages to another node in case of failure. Figure 1-7 illustrates the required control files for an SGeSAP/LX IPF application package in Serviceguard. Figure 1-7 Control Files Containing Run-time Logic Standard Serviceguard cmcld ci.sh, db.sh, dbci.
Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances 2 Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances This chapter describes in detail how to convert an existing SAP installation to become part of a high availability cluster using Serviceguard for Linux for Integrity and the Serviceguard Extension for SAP on Integrity Linux (SGeSAP/LX IPF).
Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances The tasks are presented as a sequence of steps.
Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances Linux Configuration Linux Configuration The valid Linux kernel to deploy to the servers needs to be certified with the SAP LinuxLab and at the same time needs to be supported with HP SGeSAP/LX IPF. The SAP LinuxLab publishes kernels to deploy on its FTP server. The latest kernel to deploy can be obtained from SAP. Instructions from where to download these kernels can be found on http://www.sap.com/linux/.
Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances Linux Configuration • Directory Structure Configuration This section describes the changes that need to be done in order to distribute the SAP filesystems across logical volumes on local and shared disksystems. The steps in this section are only performed once on the primary host. The primary host is the host where the SAP Central Instance was installed.
Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances Linux Configuration Directory Structure Configuration The main purpose of this section is to ensure the proper LVM layout and the right distribution of the different filesystems that reside on shared disks. Logon as root to the system where the SAP Central Instance is installed. If the database is installed on a different host, also open a shell as root on the database machine.
Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances Linux Configuration rmdir /usr/sap/ mv /usr/sap/.new /usr/sap/ chmod 751 /usr/sap/ chown adm:sapsys /usr/sap/ cd /usr/sap//DVEBMGS rm -r * # be careful with this cd .. mount /usr/sap//DVEBMGS cd DVEBMGS ls # remove everything that is different from DVEBMGS, # Example: rm -r SYS # rm -r D00 cd DVEBMGS find .
Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances Linux Configuration RUNDIRECTORY /sapdb/data/wrk/ --dbmcli on > param_directput RUNDIRECTORY /sapdb//wrk OK --dbmcli on > IS050 Installation Step: The use of local executables with SGeSAP/LX IPF is required. Check if the Central Instance host and all application servers have a directory named //SYS/exe/ctrun.
Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances Linux Configuration Cluster Node Synchronization Repeat the steps in this section for each node of the cluster that is different than the primary. Logon as root to the primary host. Prepare a logon for each of its backup hosts. IS100 Installation Step: Look at the groupfile file, /etc/group, on the primary side.
Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances Linux Configuration IS120 Installation Step: Look at the service file, /etc/services on the primary side: Replicate all services listed in Table 2-3 that exist on the primary node onto the backup node.
Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances Linux Configuration IS140 Installation Step: If the primary node has the Central Instance installed: Copy the adm home directory to the backup node. This is a local directory on each node. Default home director y path is /home/adm. IS150 Installation Step: For certain releases, such as 6.x or higher (no start-/stopsap script in adm home directory), the following steps may be skipped.
Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances Linux Configuration Never use the relocatable address in these filenames. If an application server was already installed, do not overwrite any files which will start the application server. If the rc-files have been modified, correct any hardcoded references to the primary hostname. IS160 Installation Step: If the system has a SAP kernel release < 6.
Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances Linux Configuration IS190 Installation Step: If the primary node has the Central Instance installed and the backup node has no internal application server with local executables installed: For example: On the primary node: cd /usr/sap//SYS find . -depth -print | cpio -o >/tmp/SYS.
Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances Linux Configuration IS220 Installation Step: Create a local mountpoint for each filesystem that was specified in section “Planning the LVM layout for Clustered SAP Environments” to have a “shared disk and HA NFS” access point. Refer to Table 1-1 and the corresponding table that represents entries for the required database type. Depending on the past usage of the hosts, some of the directories might already exist.
Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances Linux Configuration Cluster Node Configuration Repeat the steps in this section for each node of the cluster. Logon as root. SGeSAP/LX IPF needs remote login to be enabled on all cluster hosts. The traditional way to achieve this is via remote shell commands. If security concerns prohibit this, it is also possible to use secure shell access instead.
Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances Linux Configuration Create an .rhosts file in the home directories of the Linux users root, adm. Allow login for root as root from all nodes including the node you are logged into. Allow login for root and adm as adm from all nodes including the node you are logged into. Be careful with this step, many problems result from an incorrect setup of remote access. Check the setup with remsh commands.
Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances Linux Configuration Ensure that $HOME/.ssh/authorized_keys2 is not writable by group and others. The same is valid for the complete path. Permissions on ~ should be 755. Permissions on ~/.ssh/authorized_keys2 must be 600 or 644. Allowing group/other write access to .ssh or authorized_keys2 will disable automatic authentication.
Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances Linux Configuration IS370 Installation Step: If you need to establish frontend and server LANs to separate network traffic, be sure to add static routing entries to the internet routing configurations of /etc/sysconfig/network/routing file. Route all relocatable client LAN addresses to the local server LAN addresses. For example, a two package concept would result in two entries: 255.255.255.
Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances Linux Configuration IS420 Installation Step: Create a file called /etc/auto.import. This is the indirect automounter map file. In this file, all cross-mounted directories will now be configured to be accessed via /import. This action consists of several steps that belong together. They are combined in one installation step to prevent that parts of the process are forgotten.
Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances Linux Configuration ln -s /import/trans /usr/sap/trans ln -s /import/ /sapmnt/ 5. Create an entry in the automounter map auto.import that chains the client import directories omitting /import to the server export directories.
Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances Linux Configuration External Application Server Host Configuration Repeat the steps in this section for each host that has an external application server installed. In case the SAP System has external application servers running on non-cluster hosts, these systems need to be adopted. See IS100, IS110, IS120: In /etc, the group, passwd, and services files need to be synchronized with the cluster nodes.
Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances Cluster Configuration Cluster Configuration This section describes the cluster configuration through the following topics: • SGeSAP on Integrity Linux Configuration • HA NFS Toolkit Configuration • Serviceguard Configuration SGeSAP on Integrity Linux Configuration The Serviceguard Extension for SAP on Integrity Linux (SGeSAP/LX IPF) needs information about the SAP specific setup.
Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances Cluster Configuration IS520 Installation Step for SuSE: In addition, for a one package installation you need the following package control and configuration files: cp /opt/cmcluster/sap/SID/sapdbci.sh \ ${SGCONF}//sapdbci.sh For the two package installation you need: cp /opt/cmcluster/sap/SID/sapdb.sh \ ${SGCONF}//sapdb.sh cp /opt/cmcluster/sap/SID/sapci.sh \ ${SGCONF}//sapci.
Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances Cluster Configuration IS570 Installation Step: Specify the relocatable hostnames of the database and the Central Instance in the parameters DBRELOC and CIRELOC. They will be the same if you use the one package concept. Specify the relocatable hostname in TRANSRELOC, the host from which the mount to the transport directory /usr/sap/trans is initiated.
Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances Cluster Configuration In the ASNAME[*] array, the instance name of the application server is specified. The name is built by the abbreviations of the services that are offered by the application server. The name of a Dialog Instance is D. The name becomes unique by combining it with the instance ID.
Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances Cluster Configuration Table 2-4 provides an overview of reasonable ASTREAT values.
Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances Cluster Configuration Table 2-4 Overview of reasonable ASTREAT values ASTREA T value STOP_ DEP STOP_ LOCAL RESTART 24 1 (16) 1 (8) 0 STOP 0 START 0 Restrictions Should only be configured for Instances that have different SID and have dependencies to AS The ASPLATFORM[* array need to be specified as the platform for an Application Server that is controlled by the package.
Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances Cluster Configuration OS610 Optional Step: If you want to use DB_RECONNECT with any instance of your SAP component, you must disable the automatic restart of that component (ASTREAT not set to ${RESTART_DURING_FAILOVER}). This prevents the Instance from restarting in the event of a database or central instance failover. This means that the Instance profiles must be configured to use DB_RECONNECT.
Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances Cluster Configuration OS650 Optional Step: It is possible to failover both packages of the two package concept to the same node. If both packages try to come up on a single node after a failover at the same time, it is likely that the Central Instance package wants to start up the Central Instance before the database is fully recovered.
Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances Cluster Configuration You can also use strict policy, if your SAP system is the only one running at the site and you are low on memory. Strict policy frees up more of its own shared memory segments than the normal policy does. Advanced Options of sap.config In ${SGCONF} there is a file called customer.functions. Do not change the sap.functions.
Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances Cluster Configuration 3. stop_addons_postci: relates to start_addons_preci 4. stop_addons_predb: relates to start_addons_postdb 5. stop_addons_postdb: relates to start_addons_predb The customer.functions template that is delivered with SGeSAP/LX IPF provides several examples within the hook functions. They can be activated via additional parameters in the lower part of sap.config.
Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances Cluster Configuration OS690 Optional Step: For the two package concept, there might be a need to also have a mechanism in place, that collects the same operating system values as saposcol on the Central Instance host and feeds them back into the SAP component for display with the SAP transaction OS07. sapccmsr is a program that can be used to achieve these results.
Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances Cluster Configuration OS710 Optional Step: SGeSAP/LX IPF maintains a LOGLEVEL that can be set via sap.config and that defines the level of detail that is written by SGeSAP/LX IPF to the package logfile. Table 2-5 shows allowed values range from zero to two, with two being the default and highest level of detail.
Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances Cluster Configuration Table 2-6 Default Value Settings for SGeSAP/LX IPF (Continued) Value DEFAULT Name ORASID ora name of Oracle Administrator ORACLE_SID SID of Oracle Database ORACLE_HOME /oracle/ database home directory LOGFILE_STARTDB /startdb.log fully qualified path for startdb logfile LOGFILE_STOPDB /stopdb.
Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances Cluster Configuration HA NFS Toolkit Configuration The cross-mounted filesystems need to be added to a package that provides HA NFS services. This is usually the dbci package, the db package or the SAPNFS package. Logon as root to the primary host: IS750 Installation Step: Copy the HA NFS toolkit scripts into the package directory.
Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances Cluster Configuration IS760 Installation Step: Edit the renamed toolkit.sh file in the package directory. Change the default name to the hanfs.sh file to reflect the changed filename. The following is an example for two package concept: In dbtoolkit.sh replace the line HA_SCRIPT=${0%/*}/hanfs.sh with the line HA_SCRIPT=${0%/*}/dbhanfs.sh IS770 Installation Step: Edit the renamed hanfs.
Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances Cluster Configuration Serviceguard Configuration Refer to the standard Serviceguard for Linux for Integrity manual Managing Serviceguard for Linux to learn about creating and editing a cluster configuration file and how to apply it to initialize a cluster with cmquerycl(1m) and cmapplyconf(1m). The following section assumes that a cluster is up and running on the intended primary node and all backup nodes.
Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances Cluster Configuration Specify NODE_NAME entries for all hosts on which the package should be able to run. Specify the package control script names in the package configuration files: For one package concept specify in ${SGCONF}//dbci.config: RUN_SCRIPT ${SGCONF}//dbci.sh HALT_SCRIPT ${SGCONF}//dbci.sh For two package concept specify in ${SGCONF}//db.config: RUN_SCRIPT ${SGCONF}//db.
Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances Cluster Configuration IS830 Installation Step: The control file(s) created in IS800 need to be edited. Refer to the document Managing Serviceguard for Linux for general information about the file content. Define volume groups, MD RAID devices and logical volumes, IP addresses and subnets in the package control scripts dbci.sh or db.sh and ci.sh as appropriate.
Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances Cluster Configuration test_return 51 } function customer_defined_halt_cmds { ${SGCONF}//sapdbci.sh stopDBCI 2>/dev/null test_return 52 } For a two package concept: Use the commands stopDB, startDB to call the database control flow sapdb.sh from the customer defined sections in file db.sh. Similarly use stopCI, startCI to call the Central Instance package control flow sapci.sh from the file ci.sh.
Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances Cluster Configuration IS860 Installation Step: Distribute the package setup to all backup nodes, ie you have to create package directories ${SGCONF}/ on all backup nodes, copy all integration files below ${SGCONF}/ from the primary host’s package directory to the backup host’s package directory using rcp(1) and similarly copy ${SGCONF}/sap.functions from the primary host to the same location on the backup hosts.
Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances Cluster Configuration IS880 Installation Step: The verification of the base setup should be done in SGeSAP/LX IPF debug-mode. Create a file called ${SGCONF}//debug on all nodes in the cluster. This enables you to start the Serviceguard packages without running the SGeSAP/LX IPF specific steps. Reboot all cluster hosts. Start the cluster and run all packages. This might be done automatically.
Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances Application Configuration Application Configuration This section describes the application configuration through the following topics: • Additional Steps for Oracle Databases • Additional Steps for SAPDB Databases • SAP WAS Configuration Additional Steps for Oracle Logon as root to the primary host of the database where the package is running in debug mode.
Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances Application Configuration # Startup the database without changing the ARCHIVELOG state # echo "connect / as sysdba;" > $SRVMGRDBA_CMD_FILE echo "connect internal;" > $SRVMGRDBA_CMD_FILE echo "startup;" >> $SRVMGRDBA_CMD_FILE echo "exit;" >> $SRVMGRDBA_CMD_FILE eval $SRVMGRDBA command=@$SRVMGRDBA_CMD_FILE >> $LOG 2>&1 The sample replacement code for ORACLE 9 releases can be found in the file /opt/cmcluster/sap/SID/startdb.
Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances Application Configuration The syntax is slightly different for ORACLE 8 releases. In this case, sample replacement code can be found in /opt/cmcluster/sap/SID/startdb.lsnrctl (SuSE) or /usr/local/cmcluster/sap/SID/startdb.lsnrctl (Red Hat). OR920 Oracle Database Step: Perform the following steps as ora. Configure the listener to listen on the relocatable name of the database package.
Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances Application Configuration Revisit the hosts of OR930.
Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances Application Configuration Additional Steps for SAPDB Databases Logon as root to the primary host of the database where the db or dbci package is running in debug mode. SD960 SAPDB Database Step: Create additional links in /sapdb/ on the primary node. For example: su - sqd ln .dbenv_.csh .dbenv_.csh ln .dbenv_.sh .dbenv_.
Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances Application Configuration SAP WAS ABAP Configuration Logon as adm on the primary node on which the Central Instance has been installed. The appropriate Serviceguard package should still run on this host in debug mode. IS980 Installation Step: Change into the profile directory by typing the alias: cdpro In the DEFAULT.PFL change the following entries and replace the hostname with the relocatable name.
Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances Application Configuration rsdb/reco_trials = 15 rsdb/reco_sleep_time = 60 rsdb/reco_sosw_for_db = off (based on OSS #109036) rsdb/reco_sync_all_server = on IS997 Installation Step: For each secondary node, the SAP instance profiles and SAP startup profiles need to be copied.
Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances Application Configuration Figure 2-1 shows TMS configuration Dispay for SAP transport configuration files. Figure 2-1 TMS Configuration Display IS1010 Installation Step: You will need a separate license for all cluster nodes from SAP. These can be ordered from SAP free of charge by indicating that Serviceguard on Linux is used as clustering software.
Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances Application Configuration IS1040 Installation Step: Import the changed SAP profiles via SAP transaction RZ10. IS1050 Installation Step: The destination for print formatting, which is done by a Spool Work process, uses the application server name. To make a spooler highly available on the Central Instance server, set the destination of the printer to __ using transaction SPAD.
Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances Application Configuration IS1080 Installation Step: SAP Internet Communication Manager (ICM) may run as part of any application server. It is started as a separate multi-threaded process and can be restarted independently from the application server. E.g. usage of BW web reporting, Business Server Pages (BSP) rely on ICM to work properly.
Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances Application Configuration 90 Chapter 2
