11gr2 RAC with 11.5.10.2

Using Oracle 11g Release 2 Real Application Clusters with Oracle E-Business Suite Release 11i [ID 823586.1]

Modified: Dec 1, 2011 Type: WHITE PAPER Status: PUBLISHED Priority: 3

Oracle Applications Release 11i (11.5.10) offers numerous configuration options that can be chosen to suit particular business scenarios,uptime requirements, hardware capability, and availability requirements. This document describes how to migrate Oracle ApplicationsRelease 11i (Release 11.5.10) running on a single database instance to an Oracle Real Application Clusters (Oracle RAC) environmentrunning Oracle Database 11g Release 2 (11gR2).

Note: At present, this document applies to UNIX and Linux platforms only. If you are using Windows and want to migrate to OracleRAC or ASM, you must follow the procedures described in the Oracle Real Application Clusters Administration and DeploymentGuide 11g Release 2 (11.2) and the Oracle Database Administrator's Guide 11g Release 2 (11.2).

The most current version of this document can be obtained in My Oracle Support Knowledge Document 823586.1.

There is a change log at the end of this document.

Note: Most documentation links are to the generic 11gR2 documentation. However, where links are provided to installationdocumentation, the links resolve to the Linux doc set. Please refer to your specific platform for installation documentation.

A number of conventions are used in describing the Oracle Applications architecture:

Convention Meaning

Application tier Machines (nodes) running Forms, Web, and other services (servers). Sometimes called middle tier.

Database tier Machines (nodes) running the Oracle Applications database.

oracle User account that owns the database file system (database ORACLE_HOME and files).

CONTEXT_NAMEThe CONTEXT_NAME variable specifies the name of the Applications context that is used by AutoConfig. Thedefault is <SID>_<hostname>.

CONTEXT_FILE

Full path to the Applications context file on the application tier or database tier. The default locations are asfollows.Application tier context file:<APPL_TOP>/admin/<CONTEXT_NAME>.xmlDatabase tier context file:<RDBMS ORACLE_HOME>/appsutil/<CONTEXT_NAME>.xml

APPSpwd Oracle Applications database user password.

Monospace Text Represents command line text. Type such a command exactly as shown.

< >Text enclosed in angle brackets represents a variable. Substitute a value for the variable text. Do not type theangle brackets.

\On UNIX or Linux, the backslash character can be entered to indicate continuation of the command line on the nextscreen line.

This document is divided into the following sections:

Section 1: OverviewSection 2: EnvironmentSection 3: Database Installation and Oracle RAC MigrationSection 4: ReferencesAppendix A: Sample rconfig XML fileAppendix B: Sample <context_name_ifile.ora> for concurrent processing nodesAppendix C: Example Grid InstallationAppendix D: Database Conversion - Known IssuesAppendix E: Using SCAN Listener with E-Business Suite 11i

Section 1: Overview

Document Display https://supporthtml.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jsp...

1 of 17 08-Mar-2012 5:09 PM

You should be familiar with Oracle Database 11gR2, and have a good knowledge of Oracle Real Application Clusters (RAC). Refer to theOracle Real Application Clusters Administration and Deployment Guide 11g Release 2 (11.2) when planning to set up Oracle RealApplication Clusters and shared devices.

1.1 Cluster Terminology

You should understand the terminology used in a cluster environment. Key terms include the following.

Automatic Storage Management (ASM) is an Oracle database component that acts as an integrated file system and volumemanager, providing the performance of raw devices with the ease of management of a file system. In an ASM environment, youspecify a disk group rather than the traditional datafile when creating or modifying a database structure such as a tablespace.ASM then creates and manages the underlying files automatically.

Cluster Ready Services (CRS) is the primary program that manages high availability operations in an RAC environment. Thecrs process manages designated cluster resources, such as databases, instances, services, and listeners.

Parallel Concurrent Processing (PCP) is an extension of the Concurrent Processing architecture. PCP allows concurrentprocessing activities to be distributed across multiple nodes in an Oracle RAC environment, maximizing throughput and providingresilience to node failure.

Real Application Clusters (RAC) is an Oracle database technology that allows multiple machines to work on the same data inparallel, reducing processing time significantly. An Oracle RAC environment also offering resilience if one or more machinesbecome temporarily unavailable as a result of planned or unplanned downtime.

Grid Infrastructure is the new unified ORACLE_HOME for both ASM and CRS. That is, Grid Infrastructure Install replacesClusterware Install in 11gR2. See Oracle Grid Infrastructure Installation Guide 11g Release 2 (11.2) for Linux.

1.2 Configuration Prerequisites

The prerequisites for using Oracle RAC with Oracle Applications Release 11i are:

If you do not already have an existing single instance environment, install Oracle Applications using Rapid Install.

Note: If you are not planning ASM as part of RAC conversion ensure that all your data files, control files and redo log files ofexisting single instance database are located on a shared disk . If your data files, control files and redo log files reside on alocal disk, move them to a shared disk and recreate the control files. Refer to Oracle Database Administrator's Guide 11gRelease 2 (11.2) for more information on recreating the control files.

1.

Set up the required cluster hardware and interconnect medium.2.

Apply the following Oracle Applications patches before you start to configure your environment to use Oracle RAC.

Minipack 11i.AD.I.5 - Patch 51616761.11GR2 APPS INTEROPERABILITY PATCH - <Patch 8815204>2.USE OF LITERAL CAUSING PERFORMANCE ISSUE WHEN INSERTING DATA INTO USER DEFINED ATTRIBUTES TABLES -<Patch 5644137>

3.

CZ1CT102:ISTORE CACHE COMPONENTS TO BE DISABLED FOR SHOWING ADD TO CART BUTTONS - Patch 64007624.11i.ATG_PF.H RUP6 - Patch 59037655.11.5.10:SFM UNABLE TO PROCESS ORDERS IN RAC CONFIG - Patch 4022732

The Readme for this patch states that Concurrent Manager setup for Oracle RAC should already have been done asa prerequisite. However, this patch can be applied before setting up Oracle RAC.

6.

To use the named db listener feature of AutoConfig, apply TXK RUP-U (Patch 9535311) or higher. This patch is also anautoconfig prerequisite in the most recent interoperability note, Oracle Applications Release 11i with Oracle Database11g Release 2 , Document 881505.1 .

7.

3.

Section 2: Environment

2.1 Software and Hardware Configuration

For supported hardware configurations, refer to the relevant platform installation guides - for example, Oracle Grid InfrastructureInstallation Guide 11g Release 2 (11.2) for Linux and Oracle Real Application Clusters Installation Guide 11g Release 2 (11.2) for Linuxand UNIX. The minimum software versions are detailed below.

Component Version


2 of 17 08-Mar-2012 5:09 PM

Oracle Applications Release 11i 11.5.10.2

Oracle Database 11.2.0.1 or higher

Oracle Cluster Ready Services 11.2.0.1 or higher

You can obtain the latest Oracle Database 11gR2 software from: http://www.oracle.com/technology/software/products/database/index.html

Note: The Oracle Cluster Ready Services can be at a release level equal to or greater than the Oracle Database version, but not ata lower level.

2.2 ORACLE_HOME Nomenclature

This document refers to various ORACLE_HOMEs, as follows:

ORACLE_HOME Purpose

SOURCE_ORACLE_HOME Database ORACLE_HOME used by Oracle Applications Release 11i. Can be any supported version.

11gR2 ORACLE_HOME Database ORACLE_HOME installed for 11gR2 Oracle RAC Database.

11gR2 CRS ORACLE_HOME ORACLE_HOME installed for 11gR2 Cluster Ready Services (Infrastructure home).

8.0.6 ORACLE_HOME ORACLE_HOME installed by Oracle E-Business Suite on application tier.

Section 3: Database Installation and Oracle RAC Migration

The configuration steps you need to carry out are divided into a number of stages:

3.1 Install Oracle Clusterware 11g Release 23.2 Install Oracle Database Software 11g Release 2 and Upgrade Applications Database to 11g Release 23.3 Configure Listener3.4 Configure Shared Storage3.5 Convert Database 11g Release 2 to Oracle RAC3.6 Post- Migration Steps3.7 Enable AutoConfig on Database Tier3.8 Establish Applications Environment for Oracle RAC3.9 Configure Parallel Concurrent Processing

Note: You should take complete backups of your environment before executing these procedures, and take further backups aftereach stage of the migration. These procedures should be validated on test environments before being carried out in a productionenvironment. Users must be logged off the system during these procedures.

3.1 Install Oracle Clusterware 11g Release 2

Note: Installation of Oracle Clusterware 11g Release 2 is now part of the Infrastructure install. This task requires an understandingof the type of cluster and infrastructure that have been chosen, a description of which is outside the scope of this document. Forconvenience, the general steps involved are outlined below, but you should use the Infrastructure documentation set as the primaryreference.

3.1.1 Check Network Requirements

In Oracle Database 11g Release 2, the Infrastructure install can be configured to specify address management via node addresses ornames (as per older releases), or via Grid Naming Services. Regardless of the choice here, nodes must satisfy the followingrequirements:

Each node must have at least two network adapters: one for the public network interface, and one for the private network


3 of 17 08-Mar-2012 5:09 PM

interface (interconnect).For the public network, each network adapter must support the TCP/IP protocol.For the private network, the interconnect must support the user datagram protocol (UDP) using high-speed network adapters,and switches that support TCP/IP (Gigabit Ethernet or better is recommended).To improve availability, backup public and private network adapters can be configured for each node.The interface names associated with the network adapter(s) for each network must be the same on all nodes.

If Grid Naming Services is not used, the following addresses must also be set up:

An IP address and associated host name for each public network interface, registered in DNS.One unused virtual IP address (VIP) and associated virtual host name that are registered in DNS, resolved in the host file, orboth, and which will be configured for the primary public network interface. The virtual IP address must be in the same subnet asthe associated public interface. After installation, clients can be configured to use either the virtual host name or virtual IPaddress. If a node fails, its virtual IP address fails over to another node.A private IP address (and optionally a host name) for each private interface. Oracle recommends that you use private network IPaddresses for these interfaces.An additional virtual IP address (VIP) and associated virtual host name for the Scan Listener, registered in DNS.

For further information, see the Pre-installation requirements in Oracle Grid Infrastructure Installation Guide 11g Release 2 (11.2) Linux.

Note: A common mistake is to not set up ntpd correctly - see Network Time Protocol Setting in the Oracle Grid InfrastructureInstallation Guide

3.1.2 Verify Kernel Parameters

As part of the typical Infrastructure install, a fixup script is generated to handle most common kernel parameter issues. Follow theinstallation instructions for running this script.

Detailed hardware and OS requirements are detailed in Advanced Installation Oracle Grid Infrastructure for a Cluster Pre-installationTasks [Linux]

3.1.3 Set up Shared Storage

The available shared storage options either ASM or shared file system (clustered or NFS). Use of raw disk devices is only supported forupgrades.

These storage options are detailed in Oracle Grid Infrastructure Installation Guide 11g Release 2 (11.2) - Configuring Storage Linux.

3.1.4 Check Account Setup

Configure the oracle account's environment for Oracle Clusterware and Oracle Database 11gR2, as per the Oracle GridInfrastructure Installation Guide 11g Release 2 (11.2) Linux

3.1.5 Configure Secure Shell on All Cluster Nodes

Secure Shell configuration is covered in detail in both the Oracle Real Application Clusters Installation Guide and Oracle GridInfrastructure Installation Guide. The 11gR2 installer now provides the option to automatically set up passwordless ssh connectivity, sounlike previous releases manual set up of Secure Shell is not necessary.

For further details on manual set up of passwordless ssh, see Appendix E in Oracle Grid Infrastructure Installation Guide 11g Release 2(11.2) for Linux).

3.1.6 Run Cluster Verification Utility (CVU)

The installer will automatically run the Cluster Verify tool and provide fix up scripts for OS issues. However, you can also run CVU priorto installation to check for potential issues.

Install the cvuqdisk package as per Installing the cvuqdisk Package for Linux in Oracle Grid Infrastructure Installation Guide 11gRelease 2 (11.2) for Linux).

1.


4 of 17 08-Mar-2012 5:09 PM

Use the following command to determine which pre-installation steps have been completed, and which need to be performed:

<11g Grid Software Stage>/runcluvfy.sh stage -pre crsinst -n <node_list>

Substitute <node_list> with with the names of the nodes in your cluster, separated by commas.

2.

Use the following command to check networking setup with CVU:

<11g Grid Software Stage>/runcluvfy.sh comp nodecon -n <node_list>[-verbose]

3.

Use the following command to check operating system requirements with CVU:

<11g Software Stage>/runcluvfy.sh comp sys -n <node_list> -p{crs|database} \

-osdba osdba_group -orainv orainv_group -verbose

Substitute <node_list> with a comma-separated list of the names of the nodes in your cluster.

4.

3.1.7 Install Oracle Clusterware 11g Release 2

Use the same oraInventory location that was created during the installation of Oracle Applications Release 11i, and make abackup of oraInventory before installation.

1.

Start runInstaller from the Oracle Clusterware 11g Release 2 staging area, and install as per your requirements - see Oracle GridInfrastructure Installation Guide 11g Release 2 (11.2) Linux

Note: Many customers will have an existing Grid Infrastructure install tailored to their requirements, so can skip this step.Those less experienced with clusterware, or who are perhaps doing a test install, should refer to Appendix C for an examplewalk through.

2.

Confirming Oracle Clusterware function:

After installation, log in as root, and use the following command to confirm that your Oracle Clusterware installation isrunning correctly:

<CRS_HOME>/bin/crs_stat -t -v

1.

Successful Oracle Clusterware operation can also be verified using the following command:

<CRS_HOME>/bin/crsctl check crs

CRS-4638: Oracle High Availability Services is online

CRS-4537: Cluster Ready Services is online

CRS-4529: Cluster Synchronization Services is online

CRS-4533: Event Manager is online

2.

Post-Install Actions3.By default, the Global Services Daemon (GSD) is not started on the cluster. To start GSD, change directory to the<CRS_HOME> and issue the following commands:

srvctl enable nodeapps –g

srvctl start nodeapps

1.

3.

3.2 Install Oracle Database Software 11g Release 2 and Upgrade Applications Database to 11g Release

2

Note: You should take a full backup of the oraInventory directory before starting this stage, in which you will run the OracleUniversal Installer (runInstaller) to carry out an ":Oracle Database Installation with Oracle RAC. In the Cluster NodesWindow, verify the cluster nodes shown for the installation. Select all nodes included in your Oracle RAC cluster.


5 of 17 08-Mar-2012 5:09 PM

To install Oracle Database 11g Release 2 software and upgrade existing database to 11g Release 2, refer to the interoperabilitynote, Oracle Applications Release 11i with Oracle Database 11g Release 2 , Document 881505.1, following all the instructionsand steps listed there except these:

Start the new database listener (Conditional)Implement and run AutoConfigRestart Applications server processes (Conditional)

Note: Ensure the database software is installed on all nodes in the cluster.

3.3 Listener Configuration in 11gR2

Listener configuration can often be confusing when converting an Oracle E-Business Suite database to use Oracle RAC.

There are two types of listener in 11gR2 Clusterware: the Scan listener and general database listeners. The Scan listener provides asingle named access point for clients, and replaces the use of Virtual IP addresses (VIP) in client connection requests (tnsnames.oraaliases). However, connection requests can still be routed via the VIP name, as both access methods are fully supported.

Note: AutoConfig does not support the SCAN listener. If you would like to use the SCAN listener, a customised solution isprovided in Appendix E

To start or stop a listener from srvctl, three configuration components are required:

An Oracle Home from which to run lsncrtlThe listener.ora file under the TNS_ADMIN network directoryThe listener name (defined in listener.ora) to start and stop

The Oracle Home can either be the Infrastructure home or a database home. The TNS_ADMIN directory can be any accessible directory.The listener name must be unique within the listener.ora file. See Oracle Real Application Clusters Administration and DeploymentGuide 11g Release 2 (11.2)

There are three issues to be considered:

Listener configuration in 11gR2 Clusterware.Listener requirements for converting to Oracle RACListener requirements for AutoConfig

3.3.1 Listener Configuration in 11gR2 Clusterware

In 11gR2, listeners are configured at the cluster level, and all nodes inherit the port and environment settings. This means that theTNS_ADMIN directory path will be the same on all nodes. So to create a new listener, listener_ebs, on port 1522, running from thedatabase ORACLE_HOME and with a user defined TNS_ADMIN directory, you would execute commands based on the following:

srvctl add listener -l listener_ebs -o <11gR2 ORACLE_HOME> -p 1522

srvctl setenv listener -l listener_ebs -T TNS_ADMIN= $TNS_ADMIN

When the listener starts, it will run from the database ORACLE_HOME. srvctl manages the listener.ora file across all nodes.

3.3.2 Listener requirements for converting to Oracle RAC

By default the Grid install creates a default listener this step is optional.

Tools such as rconfig impose additional restrictions on the choice of listener. The listener must be the default listener, and it must run

from the Grid Infrastructure home. So if the default listener is not set up for rconfig, the example in 3.3.1 would need to be changed

to:

srvctl add listener -p 1522

After conversion, you can reconfigure the listener as required.

3.3.3 Listener requirements for AutoConfig

Prior to named db listener support [ see Configuration Prerequisites ] , AutoConfig created listener names of the form


6 of 17 08-Mar-2012 5:09 PM

listener_<NODE_NAME>, i.e. different listener names on each node in the cluster. If the named db listener patch has not been applied ,then manual steps will be required to enable use of SRVCTL - see 3.7.4.

3.4 Configure Shared Storage

This document does not discuss the setup of shared storage as there are no Oracle E-Business Suite specific tasks in setting up ASM,NFS (NAS) or clustered storage.

For ASM, refer to Oracle Database Storage Administrator's Guide11g Release 2 (11.2) For configuring shared storage, refer to Configuring Storage for Grid Infrastructure for a Cluster and Oracle Real ApplicationClusters (Oracle RAC) (Linux) See also Oracle Database Administrator's Guide 11g Release 2 (11.2)

3.5 Convert 11g Database to Oracle RAC

There are three options for converting to Oracle RAC, all of which are detailed in Converting to Oracle Real Application Clusters fromSingle-Instance Oracle Databases.

DBCArconfigEnterprise Manager

All these will convert an Oracle E-Business Suite database to Oracle RAC. Which is preferred is a matter of customer choice.

Prerequisites for conversion are as follows:

A clustered Grid Infrastructure install with at least one Scan listener address (Section 3.1)The default listener running from the Grid Infrastructure home (Section 3.1)

The port can either be the default, or specified during the Grid Infrastructure install.11gR2 ORACLE_HOME installed on all nodes in the cluster (Section 3.2)Shared storage - the database files can already be on shared storage [ CFS or ASM ] or moved to ASM as part of the conversion(Section 3.4)

As an example, the steps involved for Admin Managed rconfig conversion are detailed below:

As the oracle user, navigate to the 11gR2 directory $11gR2_ORACLE_HOME/assistants/ rconfig/sampleXMLs, and open the

sample file ConvertToRAC_AdminManaged.xml using a text editor such as vi. This XML sample file contains comment lines thatprovide instructions on how to edit the file to suit your site's specific needs.

1.

Make a copy of the sample ConvertToRAC.xml file, and modify the parameters as required for your system. Keep a note of thename of your modified copy.

2.

Note: Study the example file (and associated notes) in Appendix A before you edit your own file and run rconfig.

Execute rconfig using the command convert verify="ONLY" before carrying out the actual conversion. This optional but

recommended step will perform a test run to validate parameters and identify any issues that need to be corrected beforeconversion takes place.

3.

Note: Specify the 'SourceDBHome' variable in ConvertToRAC_AdminManaged.xml as Non-RAC Oracle Home(<SOURCE_ORACLE_HOME>). If you wish to specify as NEW_ORACLE_HOME, start the database from new Oracle Home.

Shut down the database instance.4.

If you are not using an spfile for database startup, you must convert to spfile before running rconfig.

SQL>create spfile='<spfile location>' from pfile;

5.

Move the $SOURCE_ORACLE_HOME/dbs/spfile<ORACLE_SID>.ora for this instance to the shared location.6.

Take a backup of existing $SOURCE_ORACLE_HOME/dbs/init<ORACLE_SID>.ora, and create a new$SOURCE_ORACLE_HOME/dbs/init<ORACLE_SID>.ora with the following parameter:

spfile='<Path of spfile on shared disk>/spfile<ORACLE_SID>.ora'

7.

Start up the database instance.8.


7 of 17 08-Mar-2012 5:09 PM

Navigate to $11gR2_ORACLE_HOME/bin, and run rconfig:

./rconfig <path to rconfig XML file created in Step 2 of this list>

This rconfig command will perform the following tasks:Migrate the database to ASM storage (if ASM is specified as the storage option in the configuration XML file)1.Create database instances on all nodes in the cluster2.Configure listener and NetService entries3.Configure and register CRS resources4.Start the instances on all nodes in the cluster5.

9.

See Appendix D for known issues with database conversion.

3.6 Post-Migration Steps

If you have used the above tools to convert to Oracle RAC, they may change some configuration options. Most notably, your databasewill now be in archivelog mode, regardless of whether it was before conversion. If you do not want to use archivelog mode, perform thefollowing steps:

Mount but do not open the database, using the command startup mount1.Use the command alter database noarchivelog to disable archiving2.Shut down the database with the shutdown immediate command3.Start up the database with the startup command.4.

For further details of how to control archiving, see Oracle Database Administrator's Guide 11g Release 2 (11.2).

3.7 Enable AutoConfig on Applications Database Tier

3.7.1 Steps to Perform On All Oracle RAC Nodes

Ensure that you have applied the Oracle Applications patches listed in the prerequisites section above.1.

Execute $AD_TOP/bin/admkappsutil.pl on the applications tier to generate an appsutil.zip file for the database tier.2.

Copy (e.g. via ftp) the appsutil.zip file to the database tier in the 11gR2_ORACLE_HOME.3.

Unzip the appsutil.zip file to create the appsutil directory in the 11gR2_ORACLE_HOME.4.

Create a <CONTEXT_NAME> directory under <11gR2_ORACLE_HOME>/network/admin. Use the new instance name whilecreating the context directory. For example, if your database name is VISRAC, and you want to use "vis" as the instance prefix,create the <CONTEXT_NAME> directory as vis1_<hostname>.

5.

Set the following environment variables:

ORACLE_HOME =<11gR2_ORACLE_HOME>

LD_LIBRARY_PATH = <11gR2_ORACLE_HOME>/lib, <11gR2_ORACLE_HOME>/ctx/lib

ORACLE_SID = <instance name for current database node>

PATH= $PATH:$ORACLE_HOME/bin;

TNS_ADMIN = $ORACLE_HOME/network/admin/<context_name>

6.

Copy the tnsnames.ora file from $ORACLE_HOME/network/admin to the $TNS_ADMIN directory, and edit the aliases forSID=<new RAC instance name>.

7.

As the APPS user, run the following command on the primary node to de-register the current configuration:

SQL>exec fnd_conc_clone.setup_clean;

8.

From the 11gR2 ORACLE_HOME/appsutil/bin directory, create an instance-specific XML context file by executing the command:

adbldxml.pl tier=db appsuser=<APPSuser> appspasswd=<APPSpwd>

9.


8 of 17 08-Mar-2012 5:09 PM

Note: If you have applied the named db listener AutoConfig patch [ see Configuration Prerequisites ] and want to use anamed database listener, modify the s_db_listener context variable in the context file.

Set the value of s_virtual host_name to point to the virtual hostname for the database host, by editing the database context file$ORACLE_HOME/appsutil/<sid>_hostname.xml

10.

From the 11gR2 ORACLE_HOME/appsutil/bin directory, execute AutoConfig on the database tier by running the adconfig.pl

script.

11.

Check the AutoConfig log file located in the <11gR2 ORACLE_HOME>/appsutil/log/<CONTEXT_NAME>/<MMDDhhmm12.

(Optional) If you want to use SCAN Listener complete the steps under "Steps to perform on Database" section in Appendix E.13.

3.7.2 Shut Down Instances and Listeners

Use the following commands:

srvctl stop listener

srvctl stop database -d <database>

3.7.3 Update Server Parameter File Settings

After Oracle RAC conversion, you will have a central server parameter file (spfile).

It is important to understand the Oracle RAC specific changes brought in by AutoConfig, and to ensure that the context file is in syncwith the database initialization parameters. The 11gR2 changes will already be reflected in the initialization parameters (from Step3.2).

The affected parameters are listed in the RAC template under 11gR2_ORACLE_HOME/appsutil/template/afinit_db112RAC.ora. They arealso listed below. Many will have been set by the conversion, and others are likely to be set by customers for non-RAC related reasons.

service_namesOracle E-Business Suite customers may well have a variety of services already set. You must ensure that service_namesincludes %s_dbService% [ database name ] across all instances.

local_listenerIf you are using SRVCTL to manage your database, the installation guides recommend leaving this unset, as it isdynamically set during instance start up. However, using the AutoConfig <instance>_local alias will also work.

remote_listenerAs per 3.3 AutoConfig does not currently support the SCAN listener. To be able to connect using AutoConfig generated TNSAliases the remote_listener must be set to the <database>_remote AutoConfig alias. This is because AutoConfigconnection aliases [ e.g. <BALANCE>, <FAILOVER> ] use the VIP host name rather than the SCAN name in the TNSdescriptor. If you do not set the remote_listener as detailed here and instead use the SCAN listener, then althoughAutoConfig aliases will continue to function, server side load balancing will not be in effect as the database listeners willonly be aware of the local instance.

cluster_databasecluster_database_instancesundo_tablespaceinstance_nameinstance_numberthread

These six parameters will all have been set as part of the conversion. The context variables should be updated to be insync with the database.

3.7.4 Update SRVCTL for New listener.ora

As mentioned in Section 3.3, AutoConfig creates listeners of the form listener_<node_name>. If you intend to manage an OracleE-Business Suite database with SRVCTL, you must perform the following steps:

If you wish to use the port allocated to the default listener, stop and remove the default listener.1.

Add Oracle E-Business Suite listener:2.


9 of 17 08-Mar-2012 5:09 PM

srvctl add listener -l listener_<name> -o <11gR2 ORACLE_HOME> -p <port>

srvctl setenv listener -l listener_<name> -T TNS_ADMIN= $ORACLE_HOME/network

/admin

Edit AutoConfig listener.ora and change LISTENER_<node> to LISTENER_<name> (for example, LISTENER_EBS).3.

On each node, add the AutoConfig listener.ora as an ifile in the $ORACLE_HOME/network/admin/listener.ora.4.

On each node, add the Autoconfig tnsnames.ora file as an ifile in the $ORACLE_HOME/network/admin/tnsnames.ora5.

Add TNS_ADMIN to database:6.

srvctl setenv database -d <database_name> -T TNS_ADMIN= $ORACLE_HOME/network

/admin

Start up the database instances and listeners on all nodes. The database can now be managed via SRVCTL.7.

To ensure all AutoConfig TNS aliases are set up to recognize all available nodes, re-run AutoConfig on all nodes. For more details ofAutoConfig, see My Oracle Support Knowledge Document 165195.1 Using AutoConfig to Manage System Configurations with OracleE-Business Suite 11i.

3.8 Establish Applications Environment for Oracle RAC

3.8.1 Preparatory Steps

Carry out the following steps on all application tier nodes:

Source the Oracle Applications environment.1.

Edit SID=< Instance 1 > and PORT=<New listener port > in the $TNS_ADMIN/tnsnames.ora file to connect to one of theinstances in the RAC environment.

2.

Confirm you can connect to one of the instances in the Oracle RAC environment before running AutoConfig.3.

Execute AutoConfig by running the command:

$AD_TOP/bin/adconfig.sh contextfile=$APPL_TOP/admin/<context_file>.

For more information on AutoConfig, see My Oracle Support Knowledge Document 165195.1 , Using AutoConfig to ManageSystem Configurations with Oracle E-Business Suite 11i.

4.

Check the $APPL_TOP/admin/<context_name>/log/<MMDDhhmm> AutoConfig log file for errors.5.

Source the environment by using the latest environment file generated.6.

Validate the tnsnames.ora and listener.ora files located in the $ORACLE_HOME/network/admin and$IAS_ORACLE_HOME/network/admin. In particular, ensure that the correct TNS aliases have been generated for load balancingand failover, and that all the aliases are defined using the virtual hostnames.

7.

Verify the dbc file located at $FND_SECURE. Ensure that the parameter 'APPS_JDBC_URL' is configured with all instances in theenvironment, and 'load_balance' is set to 'YES'.

Note: If your database and application tiers are running on same node, and if your concurrent managers do not start, followthe relevant steps in My Oracle Support Knowledge Document 434613.1> .

8.

If you have configured SCAN Listener using step 13 under Section 3.7.1, perform the steps under "Steps to perform on ApplicationTier" in Appendix E

9.

3.8.2 Implement Load Balancing

Implement load balancing for the Oracle Applications database connections:


10 of 17 08-Mar-2012 5:09 PM

Follow the substeps (1) and (2) below to run the context editor (via the Oracle Applications Manager interface) and modify thevalue of "Tools OH TWO_TASK"(s_tools_twotask), "iAS OH TWO_TASK"(s_weboh_twotask), and "Apps JDBC Connect Alias"(s_apps_jdbc_connect_alias).

To load-balance the forms-based Applications database connections, set the value of "Tools OH TWO_TASK" to point tothe <alias>_806_balance alias generated in the tnsnames.ora file.

1.

To load-balance the Self-Service (HTML-based) Applications database connections, set the value of iAS OH TWO_TASK"and "Apps JDBC Connect Alias" to point to the <database_name>_balance alias generated in the tnsnames.ora file.

2.

1.

Execute AutoConfig by running the command:

$AD_TOP/bin/adconfig.sh contextfile=$APPL_TOP/admin/<context_file>

2.

Restart the Oracle Applications processes using the new scripts generated by AutoConfig.3.

Ensure that value of the profile option "Application Database ID" is set to dbcfile name generated in $FND_SECURE.4.

Note: If you are adding a new node to the application tier, repeat this sequence of steps to set up load balancing on the newapplication tier node.

3.9 Configure Parallel Concurrent Processing

3.9.1 Check Prerequisites for Parallel Concurrent Processing

Confirm that you have more than one Concurrent Processing node in your environment.1.

If you do not, refer to My Oracle Support Knowledge Document 230672.1 for steps needed to clone the application tier.2.

3.9.2 Set Up PCP

Execute AutoConfig by using $COMMON_TOP/admin/scripts/<context_name>/adautocfg.sh on all concurrent nodes.1.

Source the application environment by using $APPL_TOP/APPSORA.env.2.

Check the configuration files tnsnames.ora and listener.ora located under the 8.0.6 ORACLE_HOME at $ORACLE_HOME /network/admin/<context>. Ensure that you have information of all the other concurrent nodes for FNDSM and FNDFS entries.

3.

Restart the Applications listener processes on each application node.4.

Log in to Oracle E-Business Suite Release 11i as SYSADMIN and choose the System Administrator Responsibility. Navigate toInstall > Nodes screen, and ensure that each node in the cluster is registered.

5.

Verify that the Internal Monitor for each node is defined properly, with correct primary and secondary node specification and workshift details. Also confirm that the Internal Monitor manager is activated from Concurrent > Manager > Administrator, activatingthe manager as required. For example, Internal Monitor: Host2 must have the primary node as host2 and secondary node ashost3.

6.

On all Concurrent Processing nodes, set the $APPLCSF environment variable to point to a log directory on a shared file system.7.

On all Concurrent Processing nodes, set the $APPLPTMP environment variable to the value of the UTL_FILE_DIR entry in init.oraon the database nodes. This value should be a directory on a shared file system.

8.

Set profile option 'Concurrent: PCP Instance Check' to 'OFF' if instance-sensitive failover is not required. Setting it to 'ON' meansthat concurrent managers will fail over to a secondary application tier node if the database instance to which it is connected goesdown.

9.

3.9.3 Set Up Transaction Managers

Shut down application tier services on all nodes.1.

Shut down all the database instances cleanly in the RAC environment, using the command:2.


11 of 17 08-Mar-2012 5:09 PM

SQL>shutdown immediate;

Edit $ORACLE_HOME/dbs/<context_name>_ifile.ora and add these parameters:3.

_lm_global_posts=TRUE

_immediate_commit_propagation=TRUE

Start the instance on each database node, one by one.4.

Start up the Application tier services on all nodes.5.

Log on to Oracle E-Business Suite 11i as SYSADMIN, and choose the System Administrator Responsibility. Navigate to Profile >System and change the profile option ‘Concurrent: TM Transport Type' to ‘QUEUE', and verify that the transaction manager worksacross the RAC instance.

6.

Navigate to Concurrent > Manager > Define screen, and set up the primary and secondary node names for transactionmanagers.

7.

Restart the concurrent managers.8.

3.9.4 Set Up Load Balancing of Concurrent Processing Tiers

Edit the Applications context file (via Oracle Applications Manager), setting the value of Concurrent Manager TWO_TASK to theload balancing alias created in the previous step.

1.

On all concurrent processing nodes, run AutoConfig with the command:

$COMMON_TOP/admin/scripts/<context_name>/adautocfg.sh.

2.

Section 4: References

My Oracle Support Knowledge Document 745759.1 : Oracle E-Business Suite and Oracle Real Application Clusters DocumentationRoadmapMy Oracle Support Knowledge Document 165195.1 : Using AutoConfig to Manage System Configurations with Oracle E-BusinessSuite 11iMy Oracle Support Knowledge Document 230672.1 : Cloning Oracle Applications Release 11i with Rapid CloneMy Oracle Support Knowledge Document 240575.1 : RAC on Linux Best PracticesMy Oracle Support Knowledge Document 265633.1 : Automatic Storage Management Technical Best PracticesMy Oracle Support Knowledge Document 881505.1 : Oracle Applications Release 11i with Oracle 11g Release 2Oracle Applications System Administrator's Guide, Release 11iMigration to ASM Technical White Paper

Appendix A: Sample Config XML file

This appendix shows example contents of an rconfig XML input file.  have been added to the code, and

notes have been inserted between sections of code.

RConfig xsi:schemaLocation="http://www.oracle.com/rconfig">

-<n:ConvertToRAC>

-

-<n:Convert verify="YES">

Note: The Convert verify option in the ConvertToRAC.xml file can take one of three values YES/NO/ONLY:

1. YES: rconfig performs prerequisites check and then start conversion.

2. NO: rconfig does not perform prerequisites check, and start conversion.

3. Convert verify="ONLY" rconfig only performs prerequisites check; it does not start conversion after completing prerequisite


12 of 17 08-Mar-2012 5:09 PM

checks.

In order to validate, and test the settings specified for converting to RAC with rconfig, it is advisable to execute rconfig usingConvert verify="ONLY" prior to carrying out the actual conversion.



<n:SourceDBHome>/oracle/product/11.1.0/db_1</n:SourceDBHome>



<n:TargetDBHome>/oracle/product/11.1.0/db_1</n:TargetDBHome>

-

-<n:SourceDBInfo SID="sales">-

<n:Credentials>

<n:User>sys</n:User>

<n:Password>oracle</n:Password>

<n:Role>sysdba</n:Role></n:Credentials>

</n:SourceDBInfo>

-

<n:Credentials>

<n:User>sys</n:User>

<n:Password>welcome</n:Password>

<n:Role>sysdba</n:Role></n:Credentials>

</n:ASMInfo>

-

-<n:NodeList>

<n:Node name="node1"/>

<n:Node name="node2"/></n:NodeList>

-

<n:InstancePrefix>sales</n:InstancePrefix>

-





-

<n:SharedStorage type="ASM">

Note: rconfig can also migrate the single instance database to ASM storage. If you want to use this option, specify the ASMparameters as per your environment in the above xml file.

The ASM instance name specified above is only the current node ASM instance. Ensure that ASM instances on all the nodes arerunning and the required diskgroups are mounted on each of them.

The ASM disk groups can be identified by issuing the following statement when connected to the ASM instance:


13 of 17 08-Mar-2012 5:09 PM

select name, state, total_mb, free_mb from v$asm_diskgroup;



<n:TargetDatabaseArea>+ASMDG</n:TargetDatabaseArea>

Note: rconfig can also migrate the single instance database to ASM storage. If you want to use this path, specify the ASMparameters as per your environment in the above XML file.

If you are using CFS for your current database files then specify "NULL" to use the same location unless you want to switch to otherCFS location. If you specify the path for the TargetDatabaseArea, rconfig will convert the files to Oracle Managed Filesnomenclature.



<n:TargetFlashRecoveryArea>+ASMDG</n:TargetFlashRecoveryArea>

</n:SharedStorage>

</n:Convert>

</n:ConvertToRAC>

</n:RConfig>

Appendix B: Sample <context_name_ifile.ora> for concurrent processing nodes

<SID>_806_BALANCE=

(DESCRIPTION_LIST=

(DESCRIPTION=

(ADDRESS=(PROTOCOL=tcp)(HOST=<host2>)(PORT=<db_port>))

(CONNECT_DATA=

(SERVICE_NAME=<Database name>)

(INSTANCE_NAME=<SID>)

)

)

(DESCRIPTION=

(ADDRESS=(PROTOCOL=tcp)(HOST=<host3>)(PORT=<db_port>))

(CONNECT_DATA=

(SERVICE_NAME=<Database name>)

(INSTANCE_NAME=<SID>)

)

)

)

Appendix C: Example Grid Installation

The following assumes a fresh Grid install and is intended for those people less experienced with Clusterware, or who may be doing atest install.

Start the Installer.1.Choose "Install and Configure Grid Infrastructure for a Cluster". Click "Next".2.Choose "Advanced Configuration" - needed when specifying scan name different to cluster name. Click "Next".3.Choose Languages. Click "Next".4.Uncheck "Configure GNS" - this is for experienced users only.5.


14 of 17 08-Mar-2012 5:09 PM

Enter cluster name, scan name and scan port. Click "Next".6.Add Hostnames and Virtual IP names for nodes in the cluster.7.Click "SSH Connectivity". Click "Test". If SSH is not established, enter OS user and password and let the installer set uppasswordless connectivity. Click "Test" again, and if successful click "Next"

8.

Choose one interface as public, one as private. eth0 should be public; eth1 is usually set up as private. Click "Next".9.Choose Shared File System. Click "Next".10.Choose the required level of redundancy, and enter location for the OCR disk. This must be located on shared storage. Click"Next".

11.

Choose the required level of redundancy, and enter location for the voting disk. This must be located on shared storage. Click"Next".

12.

Choose the default of "Do not use" for IPMI. Click "Next".13.Select an operating system group for the operator and dba accounts. For the purposes of this example installation, choose thesame group, such as "dba", for both. Click "Yes" in the popup window that asks you to confirm that the same group should beused for both, then click "Next".

14.

Enter Oracle Base and Oracle Home. The Oracle Home should not be located under Oracle Base. Click "Next".15.System checks are now performed. Fix any errors by clicking on "Fix and Check Again", or check "Ignore All" and click "Next". Ifyou are not familiar with the possible effects of ignoring errors, it is advisable to fix them.

16.

Save the response file for possible future use, then click "Finish" to start the install.17.You will be required to run various scripts as root during the install. Follow the relevant on-screen instructions.18.

Appendix D: Database Conversion - Known Issues

Database Upgrade Assistant (DBUA)

If DBUA is used to upgrade an existing AutoConfig-enabled Oracle RAC database, you may encounter an error about a pre-11gR2listener existing in CRS. In such a case, copy the AutoConfig listener.ora to the <11gR2_ORACLE_HOME>/network/admindirectory, and merge the contents in with the existing listener.ora file.

Appendix E : Using SCAN Listener with E-Business Suite 11i

AutoConfig does not currently support the SCAN Listener. This section explains a customized solution to using the SCAN Listener withE-Business Suite 11i. Only follow these steps after successfully converting and configuring for RAC using the the local [VIP] listener.

Throughout these steps, the following example ports are used:

Local listener port [ VIP port ] - 1531SCAN listener port - 1521

It is assumed that if you're using SRVCTL to manage the local listener, you have followed the steps in Section 3.7 to create an EBSlistener.

Steps to perform Database Tier :

Ensure that Database listener is up and running. As part of section 3.7.1, the listener and tnsnames.ora files will have beencreated under the RAC Oracle Home.

1.

Set the local_listener initialization parameter to <sid>_LOCAL. This alias should exist in tnsnames.ora and point to port 1531.2.For each instance, set the remote_listener parameter to the SCAN Name/Port.

SQL> alter system set remote_listener='<SCAN NAME>:<port> scope=both

sid='<Instance>'

3.

Ensure that the SCAN Listener is running, and that all instances have registered with the listener. From Cluster Home find outclustner listener name and node name from which it is running then check for the listener status

#$CRS_HOME/bin/srvctl status scan_listener

SCAN Listener LISTENER_SCAN1 is enabled

SCAN listener LISTENER_SCAN1 is running on node <node name>

From Node on which the SCAN Listener is running issue the command

# lsnrctl status <SCAN Listener name from above command >

4.

Run AutoConfig on all nodes. Verify that tnsnames.ora file created with all instances on all nodes.5.Create <sid>_<node>_ifile.ora under TNS_ADMIN as a copy of tnsnames.ora, removing all _LOCAL references. Replace the VIPdescriptors with the SCAN descriptor.

6.


15 of 17 08-Mar-2012 5:09 PM

For Example : If the Database listener port is 1531 and SCAN listener port is

1521

<sid>=

(DESCRIPTION=

(ADDRESS=(PROTOCOL=tcp)(HOST=<VIP Host>.<DOMAIN>)(PORT=1531))

(CONNECT_DATA=

(SERVICE_NAME=<service name>)

(INSTANCE_NAME=<sid>)

)

)

SCAN Descriptor<sid>=

(DESCRIPTION=

(ADDRESS=(PROTOCOL=tcp)(HOST=<SCAN Host>.<DOMAIN>)(PORT=1521))(CONNECT_DATA=

(SERVICE_NAME=<service name>)

(INSTANCE_NAME=<sid>)

)

)

Ensure that all the aliases other than <SID>_LOCAL are connecting through the SCAN Listener.7.

Steps to perform on Applications Tier

Perform steps in Section 3.8 and run AutoConfig using the local [VIP] listener on 1531. The tnsnames and DBC files will be set touse the local [ VIP ] listener.

1.

Change s_dbport and s_dbhost to SCAN Port and SCAN host.2.Create <sid>_<node>_ifile.ora under TNS_ADMIN as a copy of tnsnames.ora, removing all FNDFS references. Replace the VIPdescriptors with the SCAN descriptor.

3.

Edit the context file and change s_apps_jdbc_connect_descriptor to use the SCAN host/port.4.Change s_jdbc_connect_descriptor_generation context value to FALSE.5.Rerun AutoConfig.6.Perform all the above on all application tier nodes.7.Ensure that all the aliases and DBC are connecting through the SCAN Listener.8.

To Revert SCAN configuration

To revert back AutoConfig to non-SCAN Listener solution.

On Database Tier

Remove the <sid>_<node>_ifile.ora under TNS_ADMIN.1.Set remote_listener to non-SCAN Listener on all nodes.

alter system set remote_listener=<service>_REMOTE scope=both sid='<sid>'

2.

Verify that database listener is listening all the instances.3.Run Autoconfig.4.

On Application Tier

Remove/Move the <sid>_<node>_ifile.ora under TNS_ADMIN.1.Change s_dbport and s_dbhost to database port and host.2.Change s_jdbc_connect_descriptor_generation context value to TRUE.3.Run AutoConfig.4.Verify that all the tnsnames.ora entries , dbc file and s_apps_jdbc_connect_descriptor with proper entries.5.

Change Log

Date Description


16 of 17 08-Mar-2012 5:09 PM

14 Nov, 2011 Update for 11.2.0.3, there are no specific configuration changes for 11.2.0.3 patchset.

01 Aug , 2011 SCAN Listener customization in Appendix E

24 Mar, 2011 Implemented remarks

17 Mar, 2011 Modified step under section 3.7.4 to link ifile for tnsnames.ora

15 Sep, 2010 Update for 11.2.0.2

30 Sep, 2009Initial creation. Deleted paragraph in 3.7.1 requiring removal of init.ora and added moredetail on setting remote_listener parameter.

16 Sep, 2009 Initial creation.

Knowledge Document 823586.1 by Oracle E-Business Suite DevelopmentCopyright © 2008, 2009, Oracle.


17 of 17 08-Mar-2012 5:09 PM

Documents

11gr2 RAC with 11.5.10.2