Professional Documents
Culture Documents
Oracle EBS 11i RAC PDF
Oracle EBS 11i RAC PDF
Oracle EBS 11i RAC PDF
This document describe the steps required to install and setup an Oracle Applications Release 11i (11.5.10) environment with Oracle database 9i Release
2 (9.2.0.8) Real Application Cluster (RAC).
This document is divided into the following sections:
Section 1: Overview
Section 2: Environment
Section 3: Pre-requisites For RAC conversion.
Section 4: Installation/Configuration
Section 5: References
Section 1: Overview
The Oracle E-Business Suite 11i (Release 11.5.10) can be configured in a number of ways depending on varied business scenarios like uptime
requirements, hardware sizing and availability. This documents outlines instructions for installation and setup of Oracle E-Business Suite 11i (Release
11.5.10.2) with Oracle Database 9i(9.2.0.8) Real Application Clusters on RedHat Linux platform.
In this document instructions outlined are specific for Oracle E-Business Suite 11i and generic for all Unix platforms. For Windows platform, substitute the
appropriate syntax whenever necessary.
It is assumed that the reader of this document has knowledge of Oracle Database 9i, Real Application Clusters (RAC), and Oracle E-Business Suite
Release 11i.
Concurrent Processing (CP) requires configuration with 11i RAC environment. Please see Section 4.6 in this document for more details about configuring
CP.
System administrators are strongly advised to make complete environment backups before executing these procedures, and to make frequent backups at
multiple stages of this migration. System administrators should test these procedures in test bed environments before executing them in production
environments. Users must be asked to log off your system while applying these changes.
Section 2: Environment
The logical configuration used for creating this document is illustrated in the figure below. Oracle E-Business Suite 11i (11.5.10.2) with
9.2.0.6 version was deployed using Rapid Install.
Software Component
Version
Release 11.5.10.2 (Production release) with Consolidated Update
2( CU2)
Oracle9i
Linux
Purpose
Database ORACLE_HOME installed by Rapid Install
Database ORACLE_HOME installed for 9i RAC
Database
ORACLE_HOME installed by Rapid Install on
Application Tier
Complete Rapid Install of Oracle E-Business Suite Release 11i(Release 11.5.10.2) if you don't have an existing single instance
environment.
Migrate all the data files to shared storage configured in the previous step.
Apply the following patches on your environment before executing this conversion.
Oracle Applications patches:
Patch Number
Description
3453499
11i.ADX.F
4712852
Minipack 11i.AD.I.4
4676589
11i.ATG_PF.H RUP4
4022732
5225940
Note: Download the above patches specific to your operating system. Ensure that you have read the "README" files associated with each of these
patches for any pre-requisite patches and special instructions. Execute Autoconfig on all the tiers in your environment after application of these patches.
Section 4: Installation/Configuration
Here are the steps that need to be followed for converting E-Business Suite 11i to 9iRAC.
on all the other nodes in the cluster. Ensure that the file contains your public/private aliases.
Upgrade the Oracle Cluster Manager (ORACM) to 9.2.0.8
Download the Oracle Database 9.2.0.8 patch from Oracle Metalink.
Unzip and untar the patch.
Set ORACLE_HOME to NEW_ORACLE_HOME and LD_LIBRARY_PATH=$NEW_ORACLE_HOME/lib
Run Oracle Universal Installer from Disk1/oracm.
On "File Locations Screen", make sure that the source location is pointing to the products.xml file in the 9.2.0.8 patch set location under
Disk1/stage. Also verify that the "Destination"listed on screen is the NEW_ORACLE_HOME (9.2.0.8) directory.
On "Available Products Screen", select "Oracle9iR2 Cluster Manager 9.2.0.8.0"
On the "Public Node Information Screen", enter the public node names.
On the "Private Node Information Screen", enter the interconnect node names.
Click Install at the summary screen and complete the installation.
Note: For more details refer to Oracle Database 9.2.0.8 patch set release notes.
Verify Oracle Cluster Manager configuration files For Hangcheck-timer
Verify the NEW_ORACLE_HOME/oracm/admin/cmcfg.ora file as per sample file
Sample cmcfg.ora file
HeartBeat=15000
KernelModuleName=hangcheck-timer
ClusterName=Oracle Cluster Manager, version 9i
PollInterval=1000
MissCount=210
PrivateNodeNames= host2 host3
PublicNodeNames= int-host2 int-host3
ServicePort=9998
CmDiskFile=<path to shared drive>cmDiskFile
HostName=<Private hostname>
Note: If the cmcfg.ora file on your environment is not as per the sample file above, add the missing parameters as per the sample file shown
above. For more information on these parameters refer to RAC on Linux Best Practices.
Start the ORACM (Oracle Cluster Manager) on all nodes in the cluster
Change directory to the NEW_ORACLE_HOME/oracm/bin directory; change to the root user and start the ORACM using following
commands
$ cd $ORACLE_HOME/oracm/bin
$ su root
$ ./ocmstart.sh
Verify that ORACM is running using following command:
Note: Oracle 9i(9.2.0.4) installation needs to be done on database nodes. In our example we have installed Oracle9i (9.2.0.4) on host4 and host5 as per
the figure1-1 above.
Install 9.2.0.4 Database (Software only) -- For Unix Platforms only
Set ORACLE_HOME to NEW_ORACLE_HOME (9.2.0.4) used in cluster manager install, otherwise Oracle Universal Installer will not
detect that the cluster manager is running
Set ORACLE_BASE to a valid directory with privileges matching the user and group of the user that is installing the software.
Start runInstaller from ORACLE_HOME/bin - i.e. use Oracle Universal Installer 2.2.0.18
After the Welcome screen, press "Next" button.This should take you to the "Cluster Node Selection" screen.
Note: If you do not see "Cluster Node Selection" screen, either ORACLE_HOME is not set or the cluster manager is not running. Unless
you see the "Cluster Node Selection" screen, do not continue as Oracle Universal Installer will not install RAC option.
The "Cluster Node Selection" screen should show all your public aliases. Make sure to select all nodes. By default local node will be
selected.
Select products.jar from the 9204 Disk1/stage directory.
Choose "Oracle Database 9.2.0.4 Enterprise Edition".
On "Database Configuration Screen", check "Software Only".
Summary should include Real Applications Clusters.
Install the software.
Run root.sh when prompted.
Complete the installation.
Install 9.2.0.1 Database (Software only) -- For Windows Platforms only
Set ORACLE_HOME to NEW_ORACLE_HOME (9.2.0.1) used in cluster manager install, otherwise Oracle Universal Installer will not
detect that the cluster manager is running
Set ORACLE_BASE to a valid directory with privileges matching the user and group of the user that is installing the software.
Start runInstaller from ORACLE_HOME/bin - i.e. use Oracle Universal Installer 2.2.0.19
After the Welcome screen, press "Next" button.This should take you to the "Cluster Node Selection" screen.
Note: If you do not see "Cluster Node Selection" screen, either ORACLE_HOME is not set or the cluster manager is not running. Unless
you see the "Cluster Node Selection" screen, do not continue, as Oracle Universal Installer will not install RAC option.
The "Cluster Node Selection" screen should show all your public aliases. Make sure to select all nodes. By default local node will be
selected.
Select products.jar from the 9201 Disk1/stage directory.
Choose "Oracle Database 9.2.0.1 Enterprise Edition".
On "Database Configuration Screen", check "Custom Installation"
Select the "Oracle Real Application Cluster Component" from the custom list.
Complete the installation.
Upgrade the 9.2.0.4 software installation to Oracle9iR2 Patch Set 9.2.0.8 -- For Unix Platforms only
Download the Oracle Database 9.2.0.8 patchset 4547809 from Oracle Metalink.
Set ORACLE_HOME to NEW_ORACLE_HOME and LD_LIBRARY_PATH=$NEW_ORACLE_HOME/lib:$NEW_ORACLE_HOME/lib32
Start runInstaller from NEW_ORACLE_HOME/oui/bin.
On "Cluster Node Selection" screen, make sure that all RAC nodes are selected.
On "File Locations Screen", make sure that the source location is pointing to the products.xml file in the 9.2.0.8 patch set location under
Disk1/stage. Also verify that the "Destination" listed on screen is the NEW_ORACLE_HOME directory.
On "Available Products Screen", select "Oracle9iR2 Patch Set 9.2.0.8". Click "Next".
Click "Install" at the summary screen.
Run root.sh when prompted.
Complete the installation.
Upgrade the 9.2.0.1 software installation to Oracle9iR2 Patch Set 9.2.0.7 -- For Windows Platforms only
Note: Windows platform customers needs to upgrade the 9.2.0.1 database software installed in previous step.
Download the Oracle Database 9.2.0.7 patchset 4163445 from Oracle Metalink.
Set ORACLE_HOME to NEW_ORACLE_HOME and LD_LIBRARY_PATH=$NEW_ORACLE_HOME/lib:$NEW_ORACLE_HOME/lib32
Start runInstaller from NEW_ORACLE_HOME/oui/bin.
On "Cluster Node Selection" screen, make sure that all RAC nodes are selected.
On "File Locations Screen", make sure that the source location is pointing to the products.xml file in the 9.2.0.7 patch set location under
Disk1/stage. Also verify that the "Destination" listed on screen is the NEW_ORACLE_HOME directory.
On "Available Products Screen", select "Oracle9iR2 Patch Set 9.2.0.7". Click "Next".
Click "Install" at the summary screen.
Run root.sh when prompted.
Complete the installation.
4.3 Enable AutoConfig on Database Tier for Oracle E-Business suite 11i
Copy the appsutil, appsoui and oui22 directories from the OLD_ORACLE_HOME to the NEW_ ORACLE_HOME.
Set environment variables ORACLE_HOME, LD_LIBRARY_PATH and TNS_ADMIN to point to NEW_ ORACLE_HOME.Set ORACLE_SID
variable to point to instance name running on this database node.
Shutdown the instance and database listener.
Start the instance by using parameter file as init<sid.ora>. Start the database listener.
Generate instance specific xml file using NEW_ORACLE_HOME/appsutil/bin
NEW_ORACLE_HOME>/appsutil/log/<context_name>/<MMDDhhmm
$APPL_TOP/admin/<context_name>/log/<MMDDhhmm>.
Note :For more information on AutoConfig see Using AutoConfig to Manage System Configurations with Oracle E-Business Suite
11i.
Execute $AD_TOP/bin/admkappsutil.pl to generate appsutil.zip for the database tier.
Transfer this appsutil.zip to database tier in the NEW_ORACLE_HOME.
Unzip this file to create appsutil directory in the NEW_ORACLE_HOME.
Execute the AutoConfig on database tier from NEW_ORACLE_HOME/appsutil/<context_name>/scripts by using adautocfg.sh
Verify the AutoConfig log file located in the NEW_ORACLE_HOME
NEW_ORACLE_HOME>/appsutil/log/<context_name>/<MMDDhhmm.
Execute the following command to accumulate all the information about the instance
NOTE The next two parameters will be prompted for as many times as there are instances in the cluster.
$AD_TOP/bin/adconfig.sh contextfile=$APPL_TOP/admin/<context_file>.
Note: For more information on AutoConfig execution see Using AutoConfig to Manage System Configurations with Oracle
E-Business Suite 11i.
Verify the AutoConfig log located at $APPL_TOP/admin/<context_name>/log/<MMDDhhmm>for errors.
Source the environment by using the latest environment file generated.
Verify the tnsnames.ora, listener.ora files located in the 8.0.6 ORACLE_HOME at $ORACLE_HOME/network/admin and
$IAS_ORACLE_HOME/network/admin. Ensure that the correct tns aliases are generated for load balance and fail over.
Verify the dbc file located at $FND_SECURE. Ensure that the parameter APPS_JDBC_URL is configured with all instances in the
environment and load_balance is set to ON.
$AD_TOP/bin/adconfig.sh contextfile=$APPL_TOP/admin/<context_file>
Restart the applications processes by using the latest scripts generated after AutoConfig execution.
Ensure that value of the profile option "Application Database Id" is set to dbc file name generated at
$FND_TOP/secure/<context_name>.
Set the $APPLCSF environment variable on all the CP nodes pointing to a log directory on a shared file system.
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.
Set profile option ' Concurrent: PCP Instance Check' to OFF if DB instance sensitive failover is not required. By setting it to 'ON'
Concurrent Managers will failover to a secondary middle-tier node when database instance it is connected goes down.
Setup Transaction Managers
Shutdown the application tiers on all the nodes.
Shutdown all the database instances cleanly in RAC environment using
SQL>shutdown immediate;
Edit $ORACLE_HOME/dbs/<context_name>_ifile.ora. Add following
parameters as shown below:
_lm_global_posts=TRUE
max_commit_propagation_delay=0
Carry oout following steps If you want to load balance the database connection from concurrent processing tier.
Section 5:References
Installing Oracle Applications Release 11i documentation (Part No:B13583-01)
Interoperability Notes - Oracle Applications Release 11i with Oracle Database 9i Release 2
Oracle9i Installation Guide Release 2 (Part No: A96167-01)
Oracle9i Release Notes Release 2 (9.2.0.4.0) for Linux (Part No: B13670-01)
Using AutoConfig to Manage System Configurations with Oracle E-Business Suite 11i.
Create partitions
From one of the nodes of the cluster, run the Windows disk Administration tool as follows: On Windows NT start Disk Administrator using
the path:Start>Programs>Administrative Tools>Disk Administrator. On Windows 2000 start Disk Management using the
path:Start>Programs>Administrative Tools>Computer Management.Expand the Storage folder to Disk Management. For Windows 2000
only, use a basic disk as an extended partition for creating partitions.
Click inside an unallocated part of an extended partition. For Windows NT choose Create Partition. For Windows 2000 choose Create
Logical Drive. A wizard presents pages for configuring the logical drive.
Note: Do not use Windows disk administration tools to assign drive letters to partitions in this procedure. ClusterSetup Wizard does this
when you create the cluster. For more details check Chapter 2 in Oracle9i Real Application ClustersSetup and Configuration, Release 2
(9.2), Part NumberA96600-02 and Appendix B in Oracle9i Database Installation Guide, Release 2 (9.2.0.1.0) for Windows, Part
NumberA95493-01
Enter the size that you want for the partition. In general, this should be 100 MB or more .Ensure that a drive letter is not assigned. Cluster
Setup Wizard will do this later.
Note: Windows NT automatically assigns a drive letter. Remove this drive letter by right-clicking on the new drive and selecting Do not
assign a drive letter for the Assign Drive Letter option. Do this for any Oracle partitions. For Windows 2000 choose the option 'Do not
assign a drive letter' and then choose the option 'Do not format this partition'. Click Finish on the last page of the wizard.
Choose Commit Changes Now from the Partition menu to save the new partition information. Alternatively, close the Disk Administrator
and reboot the machine.
Repeat above steps for the second and any additional partitions. An optimal configuration is one partition for the Oracle home on a local
drive and one CFS partition for Oracle database files.
Note: For an entire Oracle Applications Vision database, create a partition of at least 65GB. This is usually the easiest method to install
Oracle Applications onto a CFS partition and then move the datafiles to other CFS Partitions after the entire Oracle Applications setup is
complete to take advantage of fast disks, RAID, etc.
Check all nodes in the cluster to ensure that the partitions are visible on all the nodes and to ensure that none of the Oracle partitions have
drive letters assigned. If any partitions have drive letters assigned, then remove them as described in earlier step.
Install Cluster File system
To prepare for this procedure, perform the tasks described in "ClusterFile System Preinstallation Steps" in this document if you have not already
done so.
Download the 9206 Cluster patch 3973928.
2. The Welcome page for the Oracle Cluster Setup Wizard appears.Click Next.
Note: It is not supported to install remotely via Terminal Server to Windows NT or 2000.However, one can do a remote install via Terminal
Server to Windows 2003 by connecting to the console of the remote server from the client by starting the Terminal Server Client as
MSTSC /V:RemoteServer /console
Note: If you need further assistance in using Terminal Server Client, please contact Microsoft Product Support.
3. Choose Create a cluster and click Next. The Network Selection page appears.
4. Choose Use private network for interconnect and click Next. The Private Network Configuration page appears.
Note: If the nodes have a high speed private network connecting them, it should be used as the cluster interconnect. Otherwise, the public
network can be selected. If you choose Use public network for interconnect, then the Public Network Configuration page appears.
5. Enter the name for the cluster you are creating, and enter the names of the nodes. If a private network interconnect was selected in
previous step , enter the public and private names for the nodes; otherwise, enter the public names and click Next. The Cluster File System
Options page appears.
6. Choose the option CFS for Datafiles. Click Next. The CFS for Data files page appears.
7. Choose a partition of the required size from the list of available partitions and then choose a drive letter from the Drive Letterdrop-down list.
For the CFS option that you choose in previous step , the partition and drive letter combination will be assigned to the CFS drive letter for
all of the volumes in the cluster.
Note: Use the longest common prefix of the node names for the cluster name. For example, if nodes aredeptclust1, deptclust2, deptclust3
then the cluster name will be deptclust. The clustername and each node name must be globally unique to your network. Do not change
node names once they have been assigned and used in a clusterdatabase.
8. Repeat the previous step for each CFS volume and click Next.
9. Click Next. The wizard checks your cluster interconnect to see if Virtual Interface Architecture (VIA) hardware is detected. If VIA is not
detected, then the VIA Detection page appears telling you VIA was not detected and TCP will be used for the clusterwareinterconnect.
Click Next and skip to step 13. If VIA is detected, then the VIA Selection page appears. Continue to step 11.
10. Choose Yes to use VIA for the interconnect and click Next. The VIA Configuration page appears. If you choose No, then TCP will be used.
11. Enter the name of the VIA connection and click Next.
12. The Install Location page is the last page that appears. The default location is %windir%\system32\osd9i. Click Browse to navigate to a
different location if needed.
13. Click Finish. A progress page displays the actions being performed.
14. When complete, reboot both nodes. Logon and make sure the new CFS partition can be seen from both nodes and has the same drive
letter assigned to it from both nodes.
Ensure that all External/Public and Internal/Private Hostname's are defined in the HOSTS file on all nodes of the cluster. This file is located
in the WINDOWS_HOME\System32\drivers\etc directory.
Ensure that the TEMP and TMP folders be the same across all nodes in the cluster. By default these settings are defined as
%USERPROFILE%\Local Settings\Temp and %USERPROFILE%\Local Settings\Tmp in the Environment Settings of My Computer. It is
recommended to explicitly redefine these as WIN_DRIVE:\temp and WIN_DRIVE:\tmp; for example: C:\temp and C:\tmp for all nodes.
Ensure that each node has administrative access to all these directories within the Windows environment by running the following at the
command prompt:
NET USE \\host_name\C$
where host_name is the public network name for the other nodes. If you plan to install the ORACLE_HOME onto another drive location
than C, check that command prompt on node 1 of a four-node cluster:
NET USE \\node2\C$
NET USE \\node3\C$
repeat these commands on all nodes within the cluster.
Run the clustercheck.exe program located in the staged directory of unzipped patch 3973928. This tool will prompt for the public and
private host names and have you verify the IP address resolution. If that passes, then it will perform a check of the health of the shared disk
array and other environment variables and permissions necessary for proper cluster installation and operation. It will create a subdirectory
called opsm in the temporary directory specified by your environment settings (WIN_DRIVE:\Temp by default if you have changed it as
recommended) and log file called OraInfoCoord.log. This log will contain any errors encountered in the check. You should see the following
at the bottom of the log file and within the command prompt window when you run the clustercheck.exe program:
ORACLE CLUSTER CHECK WAS SUCCESSFUL
Note: You must correct any errors that occur before proceeding. Please contact your Cluster Hardware Vendor if you need assistance.If
you have any issues with Clustercheck, please see Note 186130.1 Clustercheck.exe Fails with Windows Error 183 .
Note: If at any time in the installation of the software you do not see all nodes in the cluster within the Cluster Node Selection screen, there
is something wrong with your cluster configuration. You will have to go back and troubleshoot your cluster install. You can perform
clusterware diagnostics by executing the ORACLE_HOME\bin\lsnodes -v command and analyzing its output. Use Metalink to search for
any errors. Refer to your vendor's clusterware documentation if the output indicates that your clusterware is not properly installed. Resolve
the problem, and then rerun the checks.
Run Oracle Cluster Setup Wizard ckquote>
Note: For 3-or-more nodes: Since the OUI is not used, you can run this only on node 1 and the software will be correctly transferred to the other
nodes in the cluster.
1. Download Patch number 3973928 Windows CFS and Clusterware Patch for 9.2.0.6
2. Expand the patch into the staged directory, such as E:\installs\osd9206 . This will create another subdirectory such as
E:\installs\osd9206\3973928. This clusterware patch contains a full clustersetup release.
3. Within a command prompt window, navigate to the <E:\installs\osd9206\3973928\preinstall_rac\clustersetup directory in the OCFS staged
directory
4.
5.
6.
7.
8.
Launch the Oracle Cluster Setup Wizard by typing clustersetup at the command line.
The Cluster Wizard program should launch with a Welcome page. Click Next.
The first time the Wizard is run, the only option will be to Create a cluster. Click Next.
Choose "Use private network for interconnect" and click Next.
The Network Configuration page appears. Enter the cluster name. Then enter the public hostnames for all nodes. The private hostnames
will be automatically entered as public_names. Accept the default or change as appropriate for your cluster configuration. Click Next.
9. The Cluster File System Options page appears. Choose CFS for Datafiles only. Click Next.
10. The CFS for Datafiles page appears. Choose a drive letter, and then choose one of the partition you prepared earlier with a minimum 4.0
11. The VIA Detection screen appears stating whether Virtual Interface Architecture (VIA) hardware was detected. Choose yes or no
depending on your configuration. Please contact your cluster hardware vendor if you are unsure. Click Next.
12. The Install Location screen appears. It will default to the WIN_HOME\system32\osd9i directory. Accept the default and click Finish.
13. The Cluster Setup window will appear. This will show the progress with installing the cluster files, creating the cluster services on all nodes,
and formatting the OCFS drives. If no errors occur, the Oracle Cluster Setup Wizard application will complete and close automatically.
14. Check the Clusterware setup. You should have an OCFS drive visible from both nodes. Also, the following 3 services should be running on
each of the nodes in the cluster:
OracleClusterVolumeService
Oracle Object Service
OracleCMService9i
Note:If the clustersetup doesn't run properly, check for errors in the log files under WIN_HOME\system32\osd9i.
Appendix C
Sample <context_name_ifile.ora> for CP Tiers
CP_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>)
)
)
)
Change Log
Date
13 Oct 2004
Description
First Posted
23 Mar 2005
28 Apr 2005
Changed format
Changed the 9.2.0.6 cluster manager installation section ,removed the manual copy steps from this section
11-Nov-2005
19-Dec-2005
23-Mar-2006
Moved OUI 10.1.0.3 installation section ahead of 9.2.0.6 cluster manager install section.
Added one step for adding any environment specific intialization parameters into Ifile .
31-Aug-2006
20-Nov-2006
06-Feb-07