MOA_823587_1_Using Oracle 11g Release 2 Real Application Clusters With Oracle E-Business Suite Release 12

Using Oracle 11g Release 2 Real Application Clusters with Oracle E-Business Suite Release 12 (Doc ID823587.1)

Modified: Nov 14, 2013 Type: WHITE PAPER

Document 823587.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state...

1 of 20 1/15/2014 4:21 PM

Oracle E-Business Suite Release 12 has numerous configuration options that can be chosen to suit particular business scenarios, uptimerequirements, hardware capability, and availability requirements. This document describes how to migrate Oracle E-Business SuiteRelease 12 running on a single database instance to an Oracle Real Application Clusters (Oracle RAC) environment running OracleDatabase 11g Release 2 (11gR2).

Note: This document applies to UNIX and Linux platforms only. If you are using Windows and want to migrate to Oracle RAC orASM, follow the procedures described in the Oracle Real Application Clusters Administration and Deployment Guide 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 (MOS) Knowledge Document 823587.1.

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

Note: Most documentation links are to the generic Oracle Database 11gR2 documentation. As installation documentation isplatform-specific, the links provided are for Linux. You should refer to the installation documentation for your platform.

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. The default

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>.xml

Database tier context file: <RDBMS ORACLE_HOME>/appsutil/<CONTEXT_NAME>.xml

APPSpwd Oracle E-Business Suite 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: References

Appendix A: Sample rconfig XML fileAppendix B: Example Grid InstallationAppendix C: Database Conversion - Known IssuesAppendix D: Enabling/Disabling SCAN Listener Support in AutoconfigAppendix E: Instance and Listener InteractionAppendix F: Shared ORACLE_HOME and TNS_ADMIN

Section 1: Overview

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.


2 of 20 1/15/2014 4:21 PM

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 replaces the

Clusterware Install in Oracle Database 11gR2. For further information refer to Oracle Grid Infrastructure Installation Guide 11gRelease 2 (11.2) for Linux.

1.2 Configuration Prerequisites

The prerequisites for using Oracle RAC with Oracle E-Business Suite Release R12 are:

If you do not already have an existing single instance environment, install Oracle E-Business Suite 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.

Before proceeding further, check that you meet the following prerequisites and apply the relevant patches if not:

For Oracle E-Business Suite 12.0.x, you must be on Oracle E-Business Suite 12.0.2 Release Update Pack (RUP2 - Patch5484000 ), or a higher RUP such as Oracle E-Business Suite Release 12.0.4 Release Update Pack (RUP4 - Patch 6435000.

Ensure you have applied the latest AutoConfig patches, following the relevant instructions in MOS Knowledge <Document387859.1>, Using AutoConfig to Manage System Configurations with Oracle E-Business Suite Release 12. In particular,refer to Section 6 of that document.To use the named db listener feature of AutoConfig, you must apply R12.TXK.A.delta.7 [ Patch 9386653 ] or higher.

Note: Patch 6636108 will need to be applied on the application tier. This patch delivers the adbldxml utility that is

used to generate the context file on the database tier.

For Oracle E-Business Suite Release 12.1, apply the Oracle E-Business Suite Release 12.1.1 Maintenance Pack ( Patch7303030, which is also delivered by Release 12.1.1 Rapid Install).

To use the named db listener feature of AutoConfig, apply R12.TXK.B.delta 3 [ Patch 8919489 ] or higher.To use the SCAN listener feature of AutoConfig, apply either R12.TXK.B.delta 3 [ Patch 8919489 ] and R12.ATG_PF.B.delta.3 [ Patch 8919491 ] , or 12.1.3 [ Patch 9239090 ]. In addition apply [ Patch 9926448 ] to fix knownissue with FND_FS/SM alias generation with SCAN enabled.

Note: Although the SCAN listener is supported, if scan_name resolves in DNS to IP1 and IP2 , the client side 10.1.2 network codedoes not use round robin on the underlying IPs if the first IP fails. An AutoConfig solution for this is being tracked through Bug10427234. The only existing workaround is to create custom TNS aliases configured with multiple SCAN IP addresses.

Section 2: Environment


3 of 20 1/15/2014 4:21 PM

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

Oracle E-Business Suite Release R12 12.0.4+

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 E-Business Suite Release R12. 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 Oracle Database 11gR2 Cluster Ready Services (Infrastructure home).

OracleAS 10.1.2 ORACLE_HOME ORACLE_HOME installed on Application Tier for forms and reports

OracleAS 10.1.3 ORACLE_HOME ORACLE_HOME installed on Application Tier for HTTP server

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 11gR2 and Upgrade the Oracle E-Business Suite Database to 11gR23.3 Listener Configuration in Oracle Database 11gR23.4 Configure Shared Storage3.5 Convert the Oracle Database 11gR2 to Oracle RAC3.6 Post- Migration Steps3.7 Enable AutoConfig on the Applications Database Tier3.8 Establish the Applications Environment for Oracle RAC3.9 Configure Parallel Concurrent Processing

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

3.1 Install Oracle Clusterware 11gR2


4 of 20 1/15/2014 4:21 PM

Note: Installation of Oracle Clusterware 11gR2 is now part of the Infrastructure install. This task requires an understanding of thetype 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 11gR2, the Infrastructure install can be configured to specify address management via node addresses or names (asper older releases), or via Grid Naming Services. Regardless of the choice here, nodes must satisfy the following requirements:

Each node must have at least two network adapters: one for the public network interface, and one for the private networkinterface (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 configured:

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, refer to 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. For further information refer to the Network Time Protocol Setting sectionin the Oracle Grid Infrastructure Installation 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 the Advanced Installation Oracle Grid Infrastructure for a Cluster PreinstallationTasks section of the Oracle Grid Infrastructure Installation Guide 11g Release 2 (11.2) for 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 described in the Configuring Storage for Oracle Grid Infrastructure for a Cluster and

Oracle RAC section of Oracle Grid Infrastructure Installation Guide 11g Release 2 (11.2) for Linux.

3.1.4 Check Account Setup

Configure the oracle account's environment for Oracle Clusterware and Oracle Database 11gR2, as per the Oracle Grid

Infrastructure Installation Guide 11g Release 2 (11.2) for 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 Oracle Database 11gR2 installer now provides the option to automatically set up passwordless ssh


5 of 20 1/15/2014 4:21 PM

connectivity, so unlike previous releases manual set up of Secure Shell is not necessary.

For further details on manual set up of passwordless ssh, refer to Appenix E in Oracle Grid Infrastructure Installation Guide 11g Release2 (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 the Installing the cvuqdisk Package for Linux section in the Oracle Grid Infrastructure

Installation Guide 11g Release 2 (11.2) for Linux).

1.

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. To fix up issues at this stage

rather than during install you can optionally add the following options to the above command: -fixup -verbose

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 11gR2

Use the same oraInventory location that was created during the installation of Oracle E-Business Suite Release 12, 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. For furtherinformation refer to Oracle Grid Infrastructure 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 B 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 is

running 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.

3.

3.2 Install Oracle Database Software 11gR2 and Upgrade the Oracle E-Business Suite Database to

11gR2

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 perform an Oracle Database Installation with Oracle RAC. In the Cluster Nodes


6 of 20 1/15/2014 4:21 PM

Window, verify the cluster nodes shown for the installation. Select all nodes included in your Oracle RAC cluster.

Note: If you are using Oracle Database 11g Release 2 (11.2.0.4.0), then apply Patch 17429475 using Opatch utility.

To install Oracle Database 11gR2 software and upgrade an existing database to 11gR2, refer to the interoperability note,Document 1058763.1.

Follow all the instructions and steps listed there except for the following: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 Oracle Database 11gR2

The 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 Oracle Database 11gR2 Clusterware: the Scan listener and general database listeners. The Scanlistener provides a single named access point for clients, and replaces the use of Virtual IP addresses (VIP) in client connection requests(tnsnames.ora aliases). However, connection requests can still be routed via the VIP name, as both access methods are fully supported.

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

An Oracle Home from which to run lsncrtl

The listener.ora file under the TNS_ADMIN network directory

The 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 Deployment

Guide 11g Release 2 (11.2).

There are three issues to be considered:

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

For a more detailed explanation of how instances interact with listeners, refer to Appendix E.

3.3.1 Listener requirements for converting to Oracle RAC

Tools such as rconfig, dbca, dbua 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 above would

need to be changed to:

$ srvctl modify listener -l LISTENER -p <EBS Database port> [ if default LISTENER exists ]

or

$ srvctl add listener -p <EBS Database port>

After conversion, you can reconfigure the listener as required.

3.3.2 Listener requirements for AutoConfig

3.3.2.1 General Database Listener

Prior to named db listener support (see Configuration Prerequisites) , AutoConfig created listener names of the formlistener_<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 as described in section 3.7.4.


7 of 20 1/15/2014 4:21 PM

3.3.2.2 Scan Listener

Starting with Oracle E-Business Suite 12.1.3, AutoConfig supports the scan listener. Refer to Configuration Prerequisites for AutoConfigsupport for the scan listener

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 the Configuring Storage for Oracle Grid Infrastructure for a Cluster and Oracle RACsection of Oracle Grid Infrastructure Installation Guide 11g Release 2 (11.2) for Linux).Also refer to Oracle Database Administrator's Guide 11g Release 2 (11.2).

3.5 Convert the Oracle Database 11gR2 to Oracle RAC

There are three options for converting to Oracle RAC, all of which are detailed in the Converting to Oracle RAC and Oracle RAC OneNode from Single-Instance Oracle Databases section of the Oracle Real Application Clusters Installation Guide 11g Release 2 (11.2) forLinux. These are as follows:

DBCA

rconfig

Enterprise Manager

All these will convert an Oracle E-Business Suite database to Oracle RAC. Which is preferred is a matter of personal 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.Oracle Database 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)

Note: If you are using rconfig for RAC conversion make sure that you have applied Patch 17429475.

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

As the oracle user, navigate to the Oracle Database 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 that provide 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 the

name 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.5.


8 of 20 1/15/2014 4:21 PM

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

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.

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 C 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, refer to Oracle Database Administrator's Guide 11g Release 2 (11.2).

Adjust Listener Settings

The applications tier connects to the RAC instances via the port specified in the applications tier context file. If a different listener portwas chosen during the conversion, either directly or indirectly, then either change the database ports to match the applications tiercontext files, or alternatively in 3.8.1, ensure that s_dbport is updated. The value of s_dbport depends on whether the SCAN listener

is chosen in 3.7.1 If SCAN is chosen, then set to the SCAN port; otherwise, the local listener port.

3.7 Enable AutoConfig on the Applications Database Tier

3.7.1 Steps to Perform On All Oracle RAC Nodes

Ensure that you have applied the Oracle E-Business Suite 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.

Copy the jre directory from SOURCE_ORACLE_HOME>/appsutil to 11gR2_ORACLE_HOME>/appsutil.5.

Create a <CONTEXT_NAME> directory under <11gR2_ORACLE_HOME>/network/admin. Use the new instance name while

creating 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>.

6.

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>

7.


9 of 20 1/15/2014 4:21 PM

Copy the listener.ora file from SOURCE_ORACLE_HOME to the $TNS_ADMIN directory, and modify the ORACLE_HOME to11gR2_ORACLE_HOME.

8.

Copy the tnsnames.ora file from $ORACLE_HOME/network/admin to the $TNS_ADMIN directory, and edit the aliases for

SID=<new RAC instance name> and <SID>_local.

9.

IIf you have modified or created a listener with EBS database port using as per 3.3.1 stop that listener from the grid home.

$ cd $GRID_HOME

$ lsnrctl stop listener

10.

Start the listener from $TNS_ADMIN.11.

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;

12.

Set the local_listener parameter to <SID>_local and verify that the instances are registered in EBS database listener.

SQL> alter system set local_listener='<SID>_local' sid='<SID>';

13.

From the Oracle Database 11gR2 ORACLE_HOME/appsutil/bin directory, create an instance-specific XML context file by

executing the command:

$ adbldxml.pl appsuser=<APPSuser> appspass=<APPSpwd>

Note: adbldxml.pl connects to the database to collect instance and database settings. If <host/port/sid> cannot be

determined from the TNS_ADMIN/listener.ora, the script will prompt for these values. Enter the correct values to allow

the script to connect to the instance. The <host> is the current host, <sid> the value set in Step 7 above, and the port is

the listener port for the listener used during the RAC conversion.

Note: If you have applied the named db listener AutoConfig patch as listed in the Configuration Prerequisites and want touse a named database listener, modify the s_db_listener context variable in the context file.

Note: If you have applied the AutoConfig SCAN listener patches listed in the Configuration Prerequisites, then you will beprompted for the scan listener name and port. If you have configured the scan listener, supply the required name and port. See also Appendix D for switching to/from the scan listener.

14.

Set the value of s_virtual_hostname to point to the virtual hostname for the database host, by editing the database context

file $ORACLE_HOME/appsutil/<sid>_hostname.xml.

15.

Modify the s_db_listener context variable in the context file to the listener name created in step 8.16.

From the Oracle Database 11gR2 ORACLE_HOME/appsutil/bin directory, execute AutoConfig on the database tier by running

the adconfig.pl script.

17.

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

If you prefer to manage the listener using srvctl, follow the steps in step 3.7.4.19.

Note: To ensure all AutoConfig TNS aliases are set up to recognize all available nodes, re-run AutoConfig on all nodes. For moredetails of AutoConfig, refer to MOS Knowledge Document 387859.1, Using AutoConfig to Manage System Configurations with OracleE-Business Suite Release 12.

3.7.2 Shut Down Instances and Listeners

Use the following commands:

$ srvctl stop listener

$ srvctl stop database -d <database>


10 of 20 1/15/2014 4:21 PM

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 Oracle Database 11gR2 changes will already be reflected in the initializationparameters (from Step 3.2).

The affected parameters are listed in the RAC template under 11gR2_ORACLE_HOME/appsutil/template/afinit_db112RAC.ora.

They are also listed below. Many will have been set by the conversion, and others are likely to be set by customers for non-RAC relatedreasons.

service_names

Oracle E-Business Suite customers may well have a variety of services already set. You must ensure that service_names

includes %s_dbService% ( database name) across all instances.

local_listener

If you are using SRVCTL to manage your database, the installation guides recommend leaving this unset, as it is

dynamically set during instance start up. However, using the AutoConfig <instance>_local alias will also work. If you

are using a non-default listener, then this parameter must be set to <instance>_local.

remote_listener

If you are using AutoConfig to manage your connections, then the remote_listener must be set to the

<database>_remote AutoConfig alias.

cluster_database

cluster_database_instances

undo_tablespace

instance_name

instance_number

thread

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

If you intend to manage an Oracle E-Business Suite database with SRVCTL, you must perform the following additional steps:

Note: If you are using shared Oracle Home then TNS_ADMIN cannot be shared as the directory path must be same on all nodes.See

Appendix F for an example of how to use SRVCTL to manage listeners in a shared Oracle Home.

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

Add the Oracle E-Business Suite listener:2.

$ 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

Note: If registering the listener with the Cluster Services failed with CRS-0254 authorization failure error, refer to the KnownIssues section

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

Note: This step is not required if you have applied the named db listener AutoConfig patch as listed in the ConfigurationPrerequisites section.

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 as an ifile in the $ORACLE_HOME/network/admin/tnsnames.ora.5.

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

Add TNS_ADMIN to the database:7.


11 of 20 1/15/2014 4:21 PM

$ 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.8.

3.8 Establish the Applications Environment for Oracle RAC

3.8.1 Preparatory Steps

Perform the following steps on all application tier nodes:

Source the Oracle E-Business Suite environment.1.

Edit SID=<Instance 1> and PORT=<New listener port > in $TNS_ADMIN/tnsnames.ora file, to set up connection one of the

instances in the Oracle RAC environment.

2.

Confirm you are able to connect to one of the instances in the Oracle RAC environment.3.

Edit the context variable jdbc_url, adding the instance name to the connect_data parameter.4.

Run AutoConfig using the command:5.

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

For more information on AutoConfig, refer to My Oracle Support Knowledge Document 387859.1, Using AutoConfig to ManageSystem Configurations with Oracle E-Business Suite Release 12.

Check the $INST_TOP/admin/log/<MMDDhhmm> AutoConfig log file for errors.6.

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

Verify the tnsnames.ora and listener.ora files. Copies of both are located in the $INST_TOP/ora/10.1.2/network/admin

directory and $INST_TOP/ora/10.1.3/network/admin directory. In these files, ensure that the correct TNS aliases have been

generated for load balance and failover, and that all the aliases are defined using the virtual hostnames.

8.

Verify the dbc file located at $FND_SECURE. Ensure that the parameter APPS_JDBC_URL is configured with all instances in the

environment, and that load_balance is set to YES.

9.

3.8.2 Set Up Load Balancing

Implement load balancing for the Oracle E-Business Suite database connections:

Run the Context Editor (through the Oracle Applications Manager interface) and set the value 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).

1.

To load balance the forms based applications database connections, set the value of "Tools OH TWO_TASK" to point to the

<database_name>_balance alias generated in the tnsnames.ora file.

2.

To load balance the self-service 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.

3.

Execute AutoConfig by running the command:

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

4.

Restart the Applications processes, using the new scripts generated by AutoConfig.5.

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

Note: If you are adding a new node to the application tier, repeat the above steps 1-6 for setting up load balancing on thenew application tier node.

6.

3.9 Configure Parallel Concurrent Processing


12 of 20 1/15/2014 4:21 PM

3.9.1 Check prerequisites for setting up Parallel Concurrent Processing

To set up Parallel Concurrent Processing (PCP), you must have more than one Concurrent Processing node in your environment. If youdo not have this, follow the appropriate instructions in MOS Knowledge Document 406982.1, Cloning Oracle Applications Release 12with Rapid Clone.

Note: If you are planning to implement a shared Application tier file system, refer to MOS Knowledge Document 384248.1, Sharingthe Application Tier File System in Oracle E-Business Suite Release 12, for configuration steps. If you are adding a new ConcurrentProcessing node to the application tier, you will need to set up load balancing on the new application by repeating steps 1-6 inSection 3.10.

3.9.2 Set Up PCP

Edit the applications context file via Oracle Applications Manager, and set the value of the variable APPLDCP to ON.1.

Execute AutoConfig by running the following command on all concurrent processing nodes:

$ $INST_TOP/admin/scripts/adautocfg.sh

2.

Source the Applications environment.3.

Check the tnsnames.ora and listener.ora configuration files, located in $INST_TOP/ora/10.1.2/network/admin. Ensure

that the required FNDSM and FNDFS entries are present for all other concurrent nodes.

4.

Restart the Applications listener processes on each application tier node.5.

Log on to Oracle E-Business Suite Release 12 using the SYSADMIN account, and choose the System Administrator Responsibility.

Navigate to Install > Nodes screen, and ensure that each node in the cluster is registered.

6.

Verify that the Internal Monitor for each node is defined properly, with correct primary node specification, and work shift details.For example, Internal Monitor: Host1 must have primary node as host1. Also ensure that the Internal Monitor manager isactivated: this can be done from Concurrent > Manager > Administrator.

7.

Set the $APPLCSF environment variable on all the Concurrent Processing nodes to point to a log directory on a shared file

system.

8.

Set the $APPLPTMP environment variable on all the CP nodes to the value of the UTL_FILE_DIR entry in init.ora on the

database nodes. (This value should be pointing to a directory on a shared file system.)

9.

Set profile option 'Concurrent: PCP Instance Check' to OFF if database instance-sensitive failover is not required. By

setting it to 'ON', a concurrent manager will fail over to a secondary Application tier node if the database instance to which it is

connected becomes unavailable for some reason.

10.

3.9.3 Set Up Transaction Managers

Shut down the application services (servers) on all nodes1.

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

SQL>shutdown immediate;

2.

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

_lm_global_posts=TRUE

_immediate_commit_propagation=TRUE

Start the instances on all database nodes.4.

Start up the application services (servers) on all nodes.5.

Log on to Oracle E-Business Suite Release 12 using the SYSADMIN account, and choose the System Administrator responsibility.

Navigate to Profile > System, change the profile option ‘Concurrent: TM Transport Type' to ‘QUEUE', and verify that the

transaction manager works across the Oracle RAC instance.

6.

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

7.


13 of 20 1/15/2014 4:21 PM

Restart the concurrent managers.8.

If any of the transaction managers are in a deactivated status, activate them from Concurrent > Manager > Administrator.9.

3.9.4 Set Up Load Balancing on Concurrent Processing Nodes

Edit the applications context file through the Oracle Applications Manager interface, and set the value of Concurrent ManagerTWO_TASK (s_cp_twotask) to the load balancing alias (<service_name>_balance>).

1.

Execute AutoConfig by running $INST_TOP/admin/scripts/adautocfg.sh on all concurrent nodes.2.

Note: For further details on PCP configuaration, refer to MOS Knowledge Document 1525233.1.

Section 4: References

MOS Knowledge Document 745759.1, Oracle E-Business Suite and Oracle Real Application Clusters Documentation Roadmap.MOS Knowledge Document 384248.1, Sharing The Application Tier file system in Oracle E-Business Suite Release 12.MOS Knowledge Document 387859.1, Using AutoConfig to Manage System Configurations with Oracle E-Business Suite Release12.MOS Knowledge Document 406982.1, Cloning Oracle Applications Release 12 with Rapid Clone.MOS Knowledge Document 240575.1, RAC on Linux Best Practices.MOS Knowledge Document 265633.1, Automatic Storage Management Technical Best Practices.MOS Knowledge <Document 1058763.1>, Oracle Applications Release R12 with Oracle 11g Release 2.Oracle Applications System Administrator's Guide, Release 12

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

checks.

In order to validate, and test the settings specified for converting to RAC with rconfig, it is advisable to execute rconfig using

Convert 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">


14 of 20 1/15/2014 4:21 PM

-

<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 ASM

parameters 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:SQL> 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 ASM

parameters 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 other

CFS location. If you specify the path for the TargetDatabaseArea, rconfig will convert the files to Oracle Managed Files

nomenclature.



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


15 of 20 1/15/2014 4:21 PM

</n:SharedStorage>

</n:Convert>

</n:ConvertToRAC>

</n:RConfig>

Appendix B: 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.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 the

same group, such as "dba", for both. Click "Yes" in the popup window that asks you to confirm that the same group should be

used 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". If you 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 C: 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-11gR2

listener existing in CRS. In such a case, copy the AutoConfig listener.ora to the <11gR2_ORACLE_HOME>/network/admin

directory, and merge the contents in with the existing listener.ora file.

Appendix D: Enabling/Disabling SCAN Listener Support in Autoconfig

Managing the scan listener is handled on the database server. All that is required for the middle tier is for AutoConfig to be re-run, topick up the updated connection strings.

Switching from SCAN to non-SCAN

s_scan_name=null , s_scan_port=null and s_update_scan=TRUE

local_listener should be <sid>_local and remote listener <service>_remote [To allow failover aliases]

Run AutoConfig , it creates non SCAN aliases in the tnsnames.ora

Run AutoConfig on middle tier , it creates non SCAN aliases in the tnsnames.ora

Re-enabling SCAN

s_scan_name=<scan_name>,s_scan_port=<scan_port> and s_update_scan=TRUE

Modify the remote_listener to "<scan_name>:<scan_port>" using the commane alter system set

remote_listener='...' for all instances.

Run AutoConfig , it creates SCAN aliases in tnsnames.ora

Run AutoConfig on middle tier , it creates SCAN aliases in tnsnames.ora


16 of 20 1/15/2014 4:21 PM

Appendix E: Instance and Listener Interaction

Understanding how instances and listeners interact is best done with a worked example.

Consider a 2-node RAC cluster, with nodes C1 and C2.

In this example, two local listeners are used, the default listener and an EBS listener. There is nothing special about the EBS listener -it could equally have been called the ABC listener.

Listener Configuration

Listener Type Node SCAN Name Host Name VIP Name Listener Host Listener Port Listener Address

EBS listener C1 N/A C1 C1-VIP C1 1531 C1 and C1-VIP

C2 N/A C2 C2-VIP C2 1531 C2 and C2-VIP

Default listener C1 N/A C1 C1-VIP C1 1521 C1 and C1-VIP

C2 N/A C2 C2-VIP C2 1521 C2 and C2-VIP

SCAN Either C1 or C2 C-SCAN N/A N/A Either C1 or C2 1521 C-SCAN

Note the following:

The SCAN and local listener can listener on the same port as they listen on different addresses.The SCAN listener can run on either C1 or C2.Listeners have no built in relationship with instances.

SRVCTL configuration

Listener Type Listener Name Listener Port Listener Host Listener Address

General [Local] listener 1521 C1 C1 and C1-VIP

1521 C2 C2 and C2-VIP

ebs_listener 1531 C1 C1 and C1-VIP

1531 C2 C2 and C2-VIP

SCAN SCAN [ name doesn't matter and can be default ] 1521 Either C1 or C2 C-SCAN

Instance to Listener Assignment

The relationship between instances and listeners is established by the local_listener and remote_listener init.ora

parameters.

Local_Listener

The instance broadcasts to the address list, informing the listeners that the instance is now available. The local listener must berunning on the same node as the instance, as the listener spawns the oracle processes. The default value comes from thecluster.

Remote_Listener

The instances broadcasts to the address list, informing the listeners that the instance is now available for accepting requests,and that the requests are to be handled by the local_listener address. The remote hosts can be on any machine. There is nodefault value for this parameter.

Database Instance Node Local_Listener Remote_Listener DefaultListener

EBS ListenerStatus

SCAN ListenerStatus


17 of 20 1/15/2014 4:21 PM

Status

D1 I1 C1 Set to C1 & C1-VIP on 1531 C-SCAN/1521 I1 isunavailable

I1 is available I1 is available viaredirect to EBSListener for C1

Set to C1 & C1-VIP on 1531 C1/C1-VIP on1531,C2/C2-VIP on 1531

I1& I2 areunavailable

I1 is available.I2 is available viaredirect to EBSListener for C2.

I1 not available

Not set. Instance usescluster default listener - i.e.C1 & C1-VIP on 1521

C-SCAN/1521 I1 is available I1 is unavailable. I1 is available viaredirect toDefault Listenerfor C1

I2 C2 Set to C2 & C2-VIP on 1531 C-SCAN/1521 I2 isunavailable

I2 is available I2 is available viaredirect to EBSListener for C2

Set to C2 & C2-VIP on 1531 C1/C1-VIP on1531,C2/C2-VIP on 1531

I2 & I1 areunavailable

I2 is available.I1 is available viaredirect to EBSListener for C1

I2 not available

Not set. Instance usescluster default listener - i.e.C2 & C2-VIP on 1521

C-SCAN/1521 I2 is available I2 is unavailable I2 is available viaredirect toDefault Listenerfor C2

Appendix F

Shared ORACLE_HOME and TNS_ADMIN

In Oracle Database 11gR2, listeners are configured at the cluster level, and all nodes inherit the port and environment settings. Thismeans that the TNS_ADMIN directory path will be the same on all nodes. In a shared ORACLE_HOME configuration, the TNS_ADMIN

directory must be a local, non-shared directory, in order to be able to use AutoConfig generated network files. These network files willbe included as ifiles.

The following is an example for setting up TNS_ADMIN for a shared <ORACLE_HOME> in a two node cluster, C1 and C2, with respective

instances I1 and I2.

Modify the s_db_listener context parameter to a common listener name - e.g. <listener_ebs>. Repeat this for all instance

context files. If you do not have the AutoConfig db listener patch as listed in the Configuration Prerequisites section see step 3below.

1.

Run AutoConfig on both nodes. This will create listener.ora and tnsnames.ora under the node network directories - i.e.

<ORACLE_HOME>/network/admin/<i1_c1> and <i2_c2>.

2.

Edit AutoConfig listener.ora files and change LISTENER_<c1|c2> to the listener common name - <listener_ebs>. Skip this step ifyou have applied the db listener patch.

3.

Create a <local_network_dir>. For example, /etc/local/network_admin.4.

Create a listener.ora under <local_network_dir> on each node

<C1> node

ifile=<ORACLE_HOME/network/admin/<i1_c1>/listener.ora

<C2> node

ifile=<ORACLE_HOME/network/admin/<i2_c2>/listener.ora

5.

Create a tnsnames.ora under the <local_network_dir> on each node.

<C1> node

ifile=<ORACLE_HOME/network/admin/<i1_c1>/tnsnames.ora

<C2> node

6.


18 of 20 1/15/2014 4:21 PM

ifile=<ORACLE_HOME/network/admin/<i2_c2>/tnsnames.ora

Add the common listener name to the cluster and set TNS_ADMIN to the non shared directory:

$ srvctl add listener -l <listener_ebs> -o <ORACLE_HOME> -p <port>

$ srvctl setenv listener -l <listener_dbs> -t TNS_ADMIN= <local_network_dir>

7.

Known Issues

After adding new node verify the oracle software user and group has permissions rwx using crs_getperm for vip,ons and gsd

resources. (This needs to be performed if you are unable to add listener resource with permission errors). For example:

1.

$ $CRS_HOME/bin/crs_getperm ora. hostname .vip -u oracle software user

If the user does not have rwx privileges then set them using crs_setperm as follows:

$ $CRS_HOME/bin/crs_setperm ora. hostname .vip -u user: oracle software user :rwx

Remove the "<scan_name>:<scan_port>" tns alias from the tnsnames.ora files manually after running AutoConfig.2.

Change Log

Date Description

14-Nov-2013 Documented rconfig patch 17429475.

20-Sep-2013 Update for 11.2.0.4 , there are no specific configuration changes.

26-Apr-2013 Implemented remarks regarding listener configuration and s_tools_twotask etc

28-Mar-2012 Section 3.9.2 Set Up PCP , step 7 secondary node is removed for Internal Monitor

14-Nov-2011Update for 11.2.0.3, there are no specific configuration changes. In Step 3.3.1.1 , port usage detailschanged to <EBS Database Port>

08-Aug-2011 Implemented Remarks

14-Apr-2011 Modified to implement the remarks

22-Mar-2011 Added Appendix F in Table of contents

18-Mar-2011 Modified to include the bug 10427234 and setting TNS_ADMIN when shared ORACLE_HOME is used.

21-Oct-2010 Replaced R12.FND.B.delta.3 with R12.ATG_PF.B.Delta.3 in pre-reqs for SCAN listener - 1.2

5-Oct-2010 Added Appendix E.

12-Sep-2010 Update for 11.2.0.2.


19 of 20 1/15/2014 4:21 PM

30-Jun-2010 Revert to HTML markup for <,> due to script tag not working.

22-Dec-2009 Edited in readiness for publication.

5-Dec-2009Minor updates

Updated linksAdded notebox for adbldxml.pl connection requirements.

18-Nov-2009

Minor updates from review.-fixup in 3.1.6.2Copy jre in 3.7.1adbldxml.sh typing errors.

30-Sep-2009Deleted paragraph in 3.7.1 requiring removal of init.ora and added more detail on setting remote_listenerparameter.

16-Sep- 2009 Initial creation.

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

REFERENCES

NOTE:881506.1 - Oracle Applications Release 12 with Oracle 11g Release 2

BUG:14506728 - CORRECTION TO NOTE 823587.1

BUG:10427234 - AUTOCONFIG TO OPTIONALLY GENERATE ADDITIONAL ALIASES FOR SCAN LISTENERNOTE:240575.1 - RAC 9i on Linux Best PracticesNOTE:265633.1 - ASM Technical Best Practices For 10g and 11gR1 ReleaseNOTE:384248.1 - Sharing The Application Tier File System in Oracle E-Business Suite Release 12NOTE:1058763.1 - Interoperability Notes EBS 12.0 and 12.1 with Database 11gR2NOTE:387859.1 - Using AutoConfig to Manage System Configurations in Oracle E-Business Suite Release 12NOTE:406982.1 - Cloning Oracle Applications Release 12 with Rapid CloneNOTE:745759.1 - Oracle E-Business Suite and Oracle Real Application Clusters Documentation RoadmapNOTE:823587.1 - Using Oracle 11g Release 2 Real Application Clusters with Oracle E-Business Suite Release 12


20 of 20 1/15/2014 4:21 PM

Documents

MOA_823587_1_Using Oracle 11g Release 2 Real Application Clusters With Oracle E-Business Suite Release 12