Using HP Serviceguard extension for Oracle E-Business Suite B.01.00, September 2010

ManualsBrandsHP ManualsSoftwareHP Serviceguard Extension for Oracle e-Business Suite

===================================================================

Using HP Serviceguard extension for Oracle E-Business Suite

====================================================================

Revision: B.01.00

CONTENTS:

A. Preface

B. Overview

C. Supported versions

D. Network Configuration

E. Setting Up E-Business Suite

F. Setting Up Serviceguard Extension for EBS

G. SGeEBS Configuration Example

H. Setting Up SGeEBS in the Cluster

I. Dependency between APPS and DB packages

J. Using SGeEBS with Continentalclusters

K. Troubleshooting Tips

L. EBS Licensing requirements

A. Preface:

This README file describes HP Serviceguard extension for Oracle

E-Business Suite (SGeEBS). This document is intended for users who

want to provide high availability (HA) for Oracle E-Business Suite

(EBS) R12 using HP Serviceguard releases 11.19 or 11.20. It covers

the basic steps for integrating EBS with an HP-UX Serviceguard

cluster.

This version of SGeEBS supports only EBS configurations running a

single application instance with a Single Instance Oracle Database.

It is assumed that the readers are familiar with Serviceguard cluster

configuration, and EBS concepts, including installation and

configuration.

B. Overview

SGeEBS consists of configuration templates and scripts for easy

integration of EBS with Serviceguard. The Database and Application

Tiers of EBS are packaged into two separate failover packages.

Under normal circumstances, these packages will be running on

different nodes of the cluster. When any of these nodes fail, both

packages will be running on the same node. For more details, refer

the whitepaper - "High availability extension to Serviceguard for

Oracle E-Business Suite Release 12 on HP-UX" located at

http://docs.hp.com -> High Availability.

The shell scripts are used to start, stop, and monitor the health

of APPS and DB Tier packages of EBS. These scripts get integrated

with Serviceguard Master Control Script. Section C of this document

provides supported versions of all related products of SGeEBS.

Sections D and E are about pre-requisites for setting up EBS in a

Summary of content (15 pages)

PAGE 1
=================================================================== Using HP Serviceguard extension for Oracle E-Business Suite ==================================================================== Revision: B.01.00 CONTENTS: A. B. C. D. E. Preface Overview Supported versions Network Configuration Setting Up E-Business Suite F. Setting Up Serviceguard Extension for EBS G. SGeEBS Configuration Example H. Setting Up SGeEBS in the Cluster I. Dependency between APPS and DB packages J.
PAGE 2
clustered environment. Sections F, G, and H are about setting up SGeEBS and configuring the EBS Tiers as failover packages. Section I describes the implementation of the complex dependency between the APPS and DB packages. Section J is about setting up SGeEBS in Continentalclusters and Section K is about trouble shooting tips and Section L is about EBS licensing requirements. This README file assumes that the user has already installed Serviceguard and configured a cluster having minimum of two nodes.
PAGE 3
EXAMPLE: (Package IP xx.yy.zz.10) xx.yy.zz.10 virtualhostname.domain.com virtualhostname - Mapping Clients/Users To The Active Instance E. Setting Up E-Business Suite SGeEBS can be used on servers on which EBS is already installed. The only constraint is that Oracle binaries, Oracle database and application base directories should be hosted on shared volume groups that can be activated on any node of the cluster.
PAGE 4
Further details of available capabilities and options in sharing an Applications tier file system can be found in My Oracle Support Knowledge Document 384248.1, Sharing the Application Tier For cloning the APPS Tier , please refer the Metalink article [ID 406982.1] titled "Cloning Oracle Applications Release 12 with Rapid Clone".
PAGE 5
3. /opt/cmcluster/ebs/common/apps - (Files of APPS Tier) ebsapps.conf toolkit.sh haebsapps.sh Tier haapps.sh servers ebsapps.mon - EBS APPS user configuration file - Wrapper used from SG run script to invoke EBS APPS Tier - Main shell script - for starting, Stopping EBS APPS - Second level scripts to start/stop EBS Apps Tier - Called by haebsapps.sh to monitor EBS Apps Tier servers 4. /etc/cmcluster/modules/ebs db db.1 apps apps.1 - - (ADF Module files of EBS) Soft link to db.
PAGE 6
The example configuration uses installation directory mode operation. This example on SGeEBS Package Setup and Configuration is for an EBS installation using LVM. There should be separate Volume groups for DB Tier and APPS Tier.
PAGE 7
# package_type failover ----------------------------------------------------------------------# # "run_script_timeout" is the number of Seconds allowed for package to start. # "halt_script_timeout" is the number of Seconds allowed for package to halt.
PAGE 8
----------------------------------------------------------------------# # # Define DB Tier Virtual Host name ebs/db/DB_VHOST ebsdatabase ----------------------------------------------------------------------# # # Define whether the database instance is using ASM or not ebs/db/ASM no ----------------------------------------------------------------------# # # ip subnets and addresses ip_subnet 15.xxx.yy.0 ip_address 15.xxx.yy.
PAGE 9
APPS Tier connects to the DB Tier Listener by hostname and not by IP address. 2. It takes relatively long time for the DB Tier to come up and go down. To avoid timeouts, set high values for run_script_timeout and halt_script_timeout c. Specifying configuration parameters of APPS Tier package Attributes which are to be modified in ebsappspkg.conf specifically for this configuration are only shown here.
PAGE 10
# # # Define Oracle database session name ebs/apps/INSTANCE_NAME VIS ----------------------------------------------------------------------# # # # Define name of database package of EBS corresponding to the Apps package ebs/apps/DBPACKAGE_NAME ebsdbpkg ----------------------------------------------------------------------# # Define base directory in which Intance-specific EBS APPS info is installed # ebs/apps/BASE_DIR /oraapps ----------------------------------------------------------------------# # Nam
PAGE 11
# # "fs_name", "fs_directory", "fs_mount_opt", "fs_umount_opt", "fs_fsck_opt", # and "fs_type" specify the filesystems which are used by this package. # fs_name /dev/vg_OracleAppsTier/lv_OracleAppsTier fs_directory /oraapps fs_type "vxfs" fs_mount_opt "-o rw" fs_umount_opt "" fs_fsck_opt "" ----------------------------------------------------------------------NOTES: 1. We need to set DNS with the symbolic hostname for the package IP address. 2.
PAGE 12
For default configurations contents of the Application password file are: apps <- User Name apps <- Password SGeEBS Apps package looks for Application password file in the $TKIT_DIR/apps directory 4. Enable and start the packages # cmmodpkg -e -n -n ebsdbpkg # cmmodpkg -e ebsdbpkg Run cmviewcl command and make sure that ebsdbpkg has come up on one node.
PAGE 13
package fails without getting an opportunity to execute the stop sequence then the APPS package will not be brought down. This happens when the node on which the DB package fails due to hardware errors or power outage, for example. The APPS package can survive for some time without the DB package. During this time, you will see one or more of the following messages in the package log file.
PAGE 14
with the -e option to start up only the primary packages and enable switching. The APPS and DB packages of EBS should be configured in two separate recovery groups. In Continentalclusters, Recovery group is used to define a set of related primary packages on one cluster and the recovery packages on another cluster that protect the primary packages. The cmrecovercl command, when run, will start up the recovery packages and enable switching during the cluster recovery operation.
PAGE 15
2. The Apps Tier start and stop takes 1 to 2 minutes. It is expected behavior. 3. When you bring down EBS, always make sure that the APPS Tier is brought down first. 4. If you bring down the DB Tier, when the APPS Tier is up and running, it will bring down APPS Tier first. 5. SGeEBS uses Oracle supplied scripts to start/stop and monitor the APPS Tier servers. If these scripts are not present in the corresponding directories, SGeEBS cannot work properly. 7. Look for error messages in the Package log file.