EBS On Exadata

Installing Oracle E-Business Suite
Release 12 with the Oracle

Exadata Database Machine
Oracle Maximum Availability Architecture White Paper
March 2011

Maximum
Availability
Architecture

Oracle Best Practices For High Availability

Oracle White PaperInstalling Oracle E-Business Suite Release 12 with the Oracle Exadata Database Machine

Executive Overview ........................................................................... 1
Document Conventions ..................................................................... 2
Introduction ....................................................................................... 2
Prerequisites ..................................................................................... 4
Prepare a Temporary File System ................................................. 4
Prepare for Oracle E-Business Suite Rapid Install ......................... 4
Use Rapid Install and Perform a Standard Installation ....................... 5
Upgrade Oracle Database ................................................................. 5
Upgrade Oracle E-Business Suite to use the SCAN (Optional) ...... 5
Apply Application Tier Prerequisite Patches .................................. 6
Prepare the Target Database ORACLE_HOME and Nodes .......... 6
Run the Pre-upgrade Information Tool ........................................... 8
Upgrade the Database................................................................... 9
Post Database Upgrade ................................................................ 9
Convert the Database to Oracle RAC with Oracle ASM ................... 10
Run Autoconfig on the Database Tier .............................................. 14
Prepare the Database Tier Nodes for Autoconfig......................... 14
Run Autoconfig on the First Database Node ................................ 17
Post Autoconfig Steps on First Database Node ........................... 17
Run Autoconfig on All Other Database Nodes ............................. 18
Run Autoconfig on Database Node One ...................................... 19
Run Autoconfig on the Application Tier ............................................ 19
Post autoconfig Configuration .......................................................... 21
Configure HugePages on Each Database Node .......................... 21
Gather Statistics for SYS Schema ............................................... 21


Re-Create Grants and Synonyms ................................................ 22
Recompile the APPS Schema ..................................................... 22
Start Applications Tier Processes ................................................ 22
Synchronize Workflow Views ....................................................... 22
Further Configuration ....................................................................... 23
Clone Application Nodes ............................................................. 23
Setup Parallel Concurrent Processing ......................................... 23
Set Up Load Balancing ................................................................ 23
Conclusion ...................................................................................... 24
Appendix ......................................................................................... 25
Test Environment Details ............................................................. 25
Create a Local File System .......................................................... 26
Rapid Install Standard Installation Database Parameter File ....... 27
Enable Maintenance Mode .......................................................... 38
Database Pre-upgrade Tool Output ............................................. 40
rconfig XML File........................................................................... 45
Post rconfig Database Parameter File ......................................... 46
Database Node Post Autoconfig Environment File ...................... 47
Applications Tier tnsnames.ora File ............................................. 48
References ...................................................................................... 50
Change Record ............................................................................... 51

1
Executive Overview
Oracle Maximum Availability Architecture (MAA) [1] is Oracle's best practices blueprint for
implementing Oracle high-availability technologies. Oracle Exadata Database Machine
provides an optimal platform for all database workloads.
This paper shows an example of installing a new Oracle E-Business Suite Release 12
system with the database on the Oracle Exadata Database Machine using Oracle Real
Application Clusters (Oracle RAC) and Oracle Automated Storage Management (Oracle
ASM). The objective is to show a complete example that merges various best practices
from different My Oracle Support (MOS) IDs. When the Oracle E-Business Suite rapid
install process is able to install directly to Oracle RAC and Oracle ASM then this paper
should no longer be necessary.
If you are migrating from an existing Oracle E-Business Suite system to the Oracle
Exadata Database Machine system then there are several migration techniques that are
outlined in MOS ID 1133355.1, A Roadmap for Migrating Oracle E-Business Suite to the
Oracle Exadata Database Machine.

2
Document Conventions
CONVENTION MEANING
Application Tier Machines running Forms, Web, Concurrent Processing and other servers. Sometimes called middle
tier.
Database Tier Machines running an Oracle E-Business Suite database.
oracle User account that owns the database file system (database ORACLE_HOME and files).
CONTEXT_NAME The CONTEXT_NAME variable specifies the name of the Applications context that is used by
Autoconfig. The default is <SID>_<short hostname>.
CONTEXT_FILE Full path to the Applications context file on the application tier or database tier. The default locations
are as follows.
Application tier context file:
<INST_TOP>/appl/admin/CONTEXT_NAME.xml
Database tier context file:
<Database ORACLE_HOME>/appsutil/<CONTEXT_NAME>.xml
Monospace Text Represents command line text. Type such a command exactly as shown, excluding prompts such
as '%'.
<> Text enclosed in angle brackets represents a variable. Substitute a value for the variable text. Do
not type the angle brackets.
\ On UNIX, the backslash character can be entered at the end of a command line to indicate
continuation of the command on the next line.
Introduction
This document is not intended to be a comprehensive step-by-step installation guide for
all Oracle E-Business Suite releases or configurations. It is intended to be an illustrative
guide that experienced EBS system administrators can use as a foundation for
developing installation procedures for a new install of the Oracle E-Business Suite
database on the Oracle Exadata Database Machine.
This paper is intended for an audience with a working knowledge of the following:
The Oracle E-Business Suite (If you have never used the Oracle E-Business
Suite, we suggest you attend one or more of the Oracle E-Business Suite training
classes available through Oracle University.)
Oracle RAC and Oracle ASM
This paper guides you through installing a new Oracle E-Business Suite Release 12.1
split configuration with the database on the Oracle Exadata Database Machine. The
focus is on the database aspects, including upgrading the release 11.1.0.7 database

3
created with Oracle E-Business Suite Rapid Install Oracle database 11g release 11.2 and
configuring the database to work on the Oracle Exadata Database Machine utilizing
Oracle RAC and Oracle ASM. This paper also includes the necessary Oracle E-
Business Suite autoconfig steps.
The high level steps are:
1. Complete prerequisites
2. Install Oracle E-Business Suite Release 12 using the Rapid Install Standard
Installation
3. Upgrade Oracle database to 11.2
4. Using rconfig, convert the database to Oracle RAC with Oracle ASM
5. Run autoconfig on the database tier
6. Run autoconfig on the application tier
7. Post autoconfig Configuration
8. Further Configuration
a. Clone Application Nodes (optional)
b. Setup parallel concurrent manager processing
c. Setup load balancing
The following sections provide the details of these steps and include an example.

4
Prerequisites
This paper assumes an Oracle Exadata Database Machine has already been set up following the
Oracle Exadata Database Machine Configuration best practices. The following preparation steps
are also required:
1. Prepare a Temporary File System
2. Preparing for the Oracle E-Business Suite Rapid Install
Prepare a Temporary File System
The Oracle E-Business Suite Rapid Install creates a file system based Oracle Database release
11.1.0.7 database, and it cannot install directly to a database that uses Oracle ASM. Therefore it
requires non-Exadata storage of about 55 GB and an additional 50 GB of storage for the install
staging area for a total of 105 GB. The file system to be used for the database node file system
and the stage area can either use the database machine local storage or an NFS mounted file
system. In this example an NFS mount, /ebs, was used. This is described in the appendix in the
Test Environment Details section.
For an example of using the database machine local storage and how to create that temporary file
system see Creating a Local File System in the appendix.
If a Vision database install option will be selected for initial testing purposes then the local file
system does not have enough space to accommodate the required 300 GB.
Prepare for Oracle E-Business Suite Rapid Install
The Oracle E-Business Suite Rapid Install automatically installs and configures the required
technology stack components for both the database node and the primary applications node.
Applications tier processing can be distributed across multiple Applications nodes. You can also
specify additional Applications nodes to scale up the Applications tier. Typically, the additional
nodes are located on their own machines, to help increase the availability and flexibility of your
system.
The Oracle E-Business Suite Rapid Install wizard is used to install a new Standard Installation
with a fresh production database (one that is fully configured but contains no transaction data).
In a new Standard installation, you define many aspects of the configuration. The database will
be installed on the /ebs file system as listed in the Test Environment Details section of the
appendix.
The following actions are also recommended:
Verify that all application tier nodes are at the same operating system patch level

5
Ensure the operating system kernel parameter settings match on all nodes of a particular tier
(either application or database). While this is not essential, it simplifies management and
maintenance by allowing the machines to be regarded as identical.
Review and verify that the requirements in support note 761566.1 Oracle E-Business Suite
Installation and Upgrade Notes Release 12 (12.1.1) for Linux x86-64.
Use Rapid Install and Perform a Standard Installation
To set up the initial Oracle E-Business Suite database and application node use the Rapid Install
wizard (rapidwiz). Rapidwiz guides you through the screens where you enter configuration
values for your system. The values are saved in the Oracle E-Business Suite database for later
use
1
This paper uses a Standard Installation. For help performing the installation:
.
See MOS Note:798258.1 for information about the latest rapidwiz version
See the Oracle E-Business Suite Installation Guide: Using Rapid Install, Release 12.1 (12.1.1)
6

documentation for detailed instructions
The high level steps for using the Rapid Install wizard are:
1. Use Rapid Install to install the database first. The database will be installed to the
temporary file system that was described earlier in the Prepare a Temporary File
System section
2. Use Rapid Install on each application node and reference the installed database in the
Configuration Choice screen as host:ORACLE_SID:Listener-port. For example,
dscgigdb03:FRESH:1521
Upgrade Oracle Database
Upgrade Oracle E-Business Suite to use the SCAN (Optional)
Single Client Access Name (SCAN) is s a new Oracle RAC 11g Release 2 feature that provides a
single name for clients to access Oracle Databases running in a cluster. See the SCAN paper at

1
The Rapid Install installs a file-system based database with Oracle Database Enterprise Edition
release 11.1.0.7. Rapid Install does not support installing directly to Oracle ASM.

6
http://www.oracle.com/technetwork/database/clustering/overview/scan-129069.pdf for a
complete description of this feature. Note that Oracle E-Business Suite does use pre-Oracle
Database 11g Release 2 clients and will not fully benefit from the advantages of SCAN. Reason:
The Oracle E-Business Suite client will not be able to handle a set of three IPs returned by the
DNS for SCAN. Hence, it will try to connect to only the first address returned in the list and will
more or less ignore the others. If the SCAN Listener listening on this specific IP is not available
or the IP itself is not available, the connection will fail. The chance of the first IP not being
available is small, but you should be aware of this risk if you choose to use the SCAN.
Starting with 12.1.3 AutoConfig supports the scan listener. See Configuration Prerequisites for
AutoConfig support for the scan listener Consult MOS ID 823587.1, section 1.2 Configuration
Prerequisites for any updates to these patch requirements.
Apply Application Tier Prerequisite Patches
Prior to executing the upgrade of the database to RDBMS 11.2, the steps in Interoperability Notes
Oracle E-Business Suite Release 12 with Oracle Database 11g Release 2 (11.2.0), ID 1058763.1 were
followed.
This MOS ID, Interoperability Notes Oracle E-Business Suite Release 12 with Oracle
Database 11g Release 2 (11.2.0), ID 1058763.1, should be consulted for any updates as
there may be new updates since the publishing of this paper.
The high level steps for applying the patches are:
1. Stop the Application server processes on each application server node
$I NST_TOP/ admi n/ scr i pt s/ adst pal l . sh
2. Enable Maintenance Mode on the administrative application server node
3. Apply each patch above using the adpat ch utility and following the README.txt for
each one
4. Disable Maintenance Mode
5. Start the Application Server processes
$I NST_TOP/ admi n/ scr i pt s/ adst r t al . sh
Prepare the Target Database ORACLE_HOME and Nodes
1. Oracle Exadata Database Machine Best Practices and Health Check
Review the Oracle Exadata Database Machine best practices in MOS ID 1187674.1,
Master Note for Oracle Database Machine and Exadata Storage Server.
If the Oracle Exadata Database Machine health has not been verified yet then follow
MOS ID 1070954.1, Database Machine Health Check.
Review the MAA paper, Oracle E-Business Suite on Exadata
2. Verify Oracle E-Business Suite Required Packages

7
For the latest list of required packages also see MOS ID 761566.1, Oracle Applications
Installation and Upgrade Notes Release 12 (12.1.1) for Linux x86-64.
3. Create the target database Oracle 11g Oracle home (optional)
Creating a new ORACLE_HOME is optional since you can use the existing
ORACLE_HOME that is installed with the Oracle Exadata Database Machine. Each
Oracle E-Business Suite database must have a dedicated ORACLE_HOME and sharing an
Oracle E-Business Suite ORACLE_HOME with any other application is not allowed
Starting with the first patch set for Oracle Database 11g Release 2 (11.2.0.2), Oracle
Database patch sets are full installations of the Oracle Database software. In past releases,
Oracle Database patch sets consisted of a set of files that replaced files in an existing Oracle
home. Beginning with Oracle Database 11g Release 2, patch sets are full installations that
replace existing installations. See Important Changes to Oracle Database Patch Sets
Starting With 11.2.0.2 [MOS ID 1189783.1] for more details on this.
The software can be downloaded from My Oracle support: patch 10098816, making sure to
select the Linux x86-64 platform.
Install the new 11.2.0.2 ORACLE_HOME set of software on the target Oracle Exadata
Database Machine and make sure to choose the following options:
Install Software Only
Real Application Clusters database installation and select all Oracle RAC nodes
4. Apply Prerequisite Exadata Database Machine Patches
a. Follow MOS ID 888828.1, Database Machine and Exadata Storage Server 11g Release
2 (11.2) Supported Versions to ensure the latest Sun Oracle Database machine patches
are applied.
b. Apply the additional database patches listed in MOS ID 1058763.1, Interoperability Notes
EBS R12 with Database 11gR2.
c. Apply the latest 11.2 database patch set updates and Exadata patches, see Oracle
Recommended Patches -- Oracle Database [ID 756671.1]. Patch Set Updates (PSU)
also include the latest Critical Patch Update (CPU). Note that some of the patches
listed in MOS ID 1058763.1 may already be part of the latest PSU or CPU.
5. Install the Database Examples
The examples CD install is needed because it contains all the localization files needed for
Oracle Text.
1. Download the software from
http://download.oracle.com/otn/linux/oracle11g/R2/linux.x64_11gR2_examples.zip

8
2. Follow the installation steps in the Database Examples Installation Guide in chapter 3
to install in the Oracle Database 11g Release 2 ORACLE_HOME.
6. Create the nls/data/9idata directory
In the target 11.2 ORACLE_HOME execute the following:
per l $ORACLE_HOME/ nl s/ dat a/ ol d/ cr 9i dat a. pl
Run the Pre-upgrade Information Tool
After you have installed the software for Oracle Database 11g Release 2 (11.2) and any required
patches, you should analyze your database before upgrading it to the new release. This is done by
running the Pre-Upgrade Information Tool from the environment of the database you are to
upgrade. This is a required step if you are upgrading manually; otherwise, the cat upgr d. sql
script terminates with errors. Running the Pre-Upgrade Information Tool is also recommended if
you are using the database upgrade assistant (DBUA) to perform the upgrade, so that you can
preview the items that DBUA checks.
For details see Run the Pre-Upgrade Information Tool in the Oracle Upgrade Guide
9
. For
example:
cd $ORACLE_HOME/ r dbms/ admi n
cp ut l u112i . sql / t mp
cd / t mp
SQL> SPOOL upgr ade_i nf o. l og
SQL> @ut l u112i . sql
SQL> SPOOL OFF
Check the output of the Pre-Upgrade Information Tool in upgrade_info.log. See the sample
output in the appendix at Database Preupgrade Tool Output / First Pass.
React to any Issues Identified by the Pre-upgrade Tool
SQL> al t er t abl espace sysaux add dat af i l e
' / ebs/ FRESH/ db/ apps_st / dat a/ sysaux03. dbf ' si ze 100M;
Tabl espace al t er ed.

SQL> show par amet er j ava_pool _si ze

NAME TYPE VALUE
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
j ava_pool _si ze bi g i nt eger 0

SQL> al t er syst emset j ava_pool _si ze=150M;

Syst emal t er ed.

SQL> EXEC DBMS_STATS. GATHER_DI CTI ONARY_STATS;
PL/ SQL pr ocedur e successf ul l y compl et ed.

SQL> PURGE DBA_RECYCLEBI N;

DBA Recycl ebi n pur ged.

9
Rerun the Pre-upgrade Information Tool
If there were any issues identified and repaired, then re-run the tool. Sample output from this
execution can be found at Database Preupgrade Tool Output / Second Pass.
Upgrade the Database
You should upgrade the database using the Database Upgrade Assistant (DBUA). You can
manually upgrade the database but more post-upgrade steps are required that are not
documented in this paper. Both options are detailed in the Upgrade Guide in chapter 3. This
white paper uses DBUA. DBUA is the recommended upgrade method and that is what was
followed for this paper.
During DBUA:
1. In Database Upgrade Assistant, Step 1 of 7 : Upgrade Options, select:
a. Recompile invalid objects at the end of upgrade
b. Upgrade the Time Zone Version and TIMESTAMP WITH TIME ZONE Data
c. Backup Database, this is optional and can be done before DBUA if desired with your
own backup procedures.
2. In Database Upgrade Assistant, Step 2 of 7 : Move Database Files, select Do Not Move
Database Files as Part of Upgrade. Do not opt to move the database files to Oracle
ASM. This will be taken care of during the Convert the Database to Oracle RAC
with Oracle ASM section.
3. Do not select specify a Fast Recovery Area in Database Upgrade Assistant, Step 3 of 6 :
Recovery and Diagnostic Locations. This will also be taken care of during the Convert
the Database to Oracle RAC with Oracle ASM section..
4. Do not select Configure the Database with Enterprise Manager in Database Upgrade
Assistant, Step 4 of 6 : Management Options.
Post Database Upgrade
Note that following DBUA the database is now using a server parameter file (spfile) under the
new $ORACLE_HOME/ dbs di r ect or y, $ORACLE_HOME/ dbs/ spf i l e${ORACLE_SI D}. or a.
Shutdown the Old Listener
The old 11.1.0.7 ORACLE_HOME listener is no longer needed at this point so it should be shut
down.
1. Set environment to the old 11.1.0.7 database environment.
2. lsnrctl stop FRESH
Set the new environment
expor t ORACLE_BASE=/ u01/ app/ or acl e
expor t ORACLE_HOME=$ORACLE_BASE/ pr oduct / 11. 2. 0/ dbhome_1
expor t ORACLE_SI D=FRESH
expor t PATH=$ORACLE_HOME/ bi n: $ORACLE_HOME/ per l / bi n: $PATH

10
Set the New Diagnostic Destination
The DI AGNOSTI C_DEST database parameter is derived from the value of the $ORACLE_BASE
environment variable. Since we have ORACLE_BASE set we can just reset this parameter and it will
default to ORACLE_BASE.
SQL> al t er syst emr eset di agnost i c_dest ;

Syst emal t er ed.

SQL> show par amet er di agnost i c_dest

NAME TYPE VALUE
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
di agnost i c_dest st r i ng / u01/ app/ or acl e
Convert the Database to Oracle RAC with Oracle ASM
This step converts the upgraded database to an Oracle RAC database and moves the datafiles to
Oracle ASM using the rconfig utility. There are other more manual methods for doing this
conversion that can be found in the Oracle documentation but those were not explored because
rconfig is the simplest method. For further rconfig references see:
Using Oracle 11g Release 2 Real Application Clusters with Oracle E-Business Suite
Release 12 [ID 823587.1]
RCONFIG : Frequently Asked Questions [ID 387046.1]
Oracle Real Application Clusters Installation Guide 11g Release 2 (11.2) for Linux and
UNIX - C.4 Converting Databases to Oracle RAC Using RCONFIG
Perform the following steps to use rconfig to convert the freshly installed and upgraded database
to use Oracle RAC and Oracle ASM:
1. Create and edit the rconfig XML File
a. cd $ORACLE_HOME/ assi st ant s/ r conf i g/ sampl eXMLs
b. cp Conver t ToRAC_Admi nManaged. xml Conver t ToRAC_Admi nManaged_FRESH. xml
c. Edit the ConvertToRAC_AdminManaged_FRESH.xml file changing appropriate
variables as highlighted in the rconfig XML file
2. Verify the compatible.rdbms ASM attribute setting.
Run this SQL script
SQL>
col umn di skgr oup f or mat a10
col umn name f or mat a20
col umn val ue f or mat a12
set pages 99
sel ect dg. name di skGr oup , a. name, a. val ue
f r omV$ASM_DI SKGROUP dg,
V$ASM_ATTRI BUTE a
wher e dg. gr oup_number = a. gr oup_number
and a. name = ' compat i bl e. r dbms ;

11
DI SKGROUP NAME VALUE
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
DATA compat i bl e. r dbms 11. 2. 0. 2
DBFS_DG compat i bl e. r dbms 11. 2. 0. 2
RECO compat i bl e. r dbms 11. 2. 0. 2

3. Change the COMPATIBLE database parameter
Change the database parameter, COMPATI BLE, to match the ASM compat i bl e. r dbms setting.

a. SQL> show par amet er compat i bl e
compat i bl e st r i ng 11. 1. 0
b. Edi t t he spf i l e
SQL> al t er syst emset compat i bl e="11. 2. 0. 2" scope=spf i l e;
c. SQL> shut down i mmedi at e
d. SQL> st ar t up
4. Configure RMAN Parallelism
Configure the Oracle Recovery Manager (RMAN) to use parallel channels for disk. Rconfig
uses RMAN when moving the datafiles from the file system to ASM and using RMAN
parallel channels will improve the performance of that step in rconfig.
a. r man t ar get /
b. RMAN> show al l ;
usi ng t ar get dat abase cont r ol f i l e i nst ead of r ecover y cat al og
RMAN conf i gur at i on par amet er s f or dat abase wi t h db_uni que_name FRESH ar e:
CONFI GURE RETENTI ON POLI CY TO REDUNDANCY 1; # def aul t
CONFI GURE BACKUP OPTI MI ZATI ON OFF; # def aul t
CONFI GURE DEFAULT DEVI CE TYPE TO DI SK; # def aul t
CONFI GURE CONTROLFI LE AUTOBACKUP OFF; # def aul t
CONFI GURE CONTROLFI LE AUTOBACKUP FORMAT FOR DEVI CE TYPE DI SK TO ' %F' ; # def aul t
CONFI GURE DEVI CE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # def aul t
. . .

c. RMAN> CONFI GURE devi ce t ype DI SK par al l el i sm8;
d. RMAN exi t
This will persistently set the RMAN parallelism for disk devices to 8 and rconfig will use
this.
5. Verify the rconfig config file
Verify the rconfig config file by running rconfig first with the convert verify="ONLY"
setting.
a. Change the <n: Conver t ver i f y="YES"> line in rconfig XML file to
(<n: Conver t ver i f y="ONLY">)
b. Run rconfig to verify parameters are correct
$ rconfig ConvertToRAC_AdminManaged_FRESH.xml
c. You should see:
<?xml ver si on="1. 0" ?>
<RConf i g ver si on="1. 1" >

12
<Conver t ToRAC>
<Conver t >
<Response>
<Resul t code="0" >
Operation Succeeded
</ Resul t >
</ Response>
<Ret ur nVal ue t ype="obj ect ">
Ther e i s no r et ur n val ue f or t hi s st ep </ Ret ur nVal ue>
</ Conver t >
</ Conver t ToRAC></ RConf i g>
d. If you do not see the Operation Succeeded, then fix any issues and rerun rconfig
with the ONLY option until the issues are resolved The log file will be located in the
$ORACLE_BASE/ cf gt ool l ogs/ r conf i g directory
6. Run rconfig
Once the verification is ok then change Conver t ver i f y=" back to YES and run rconfig
again to do the actual conversion. You should see an Oper at i on Succeeded line,
highlighted below in the sample output. To monitor rconfig, view the log file it creates at
$ORACLE_BASE/ cf gt ool l ogs/ r conf i g
$ rconfig ConvertToRAC_AdminManaged_FRESH.xml

Conver t i ng Dat abase "FRESH" t o Cl ust er Dat abase. Tar get Or acl e Home:
/ u01/ app/ or acl e/ pr oduct / 11. 2. 0/ dbhome_1. Dat abase Rol e: PR
I MARY.
Set t i ng Dat a Fi l es and Cont r ol Fi l es
Addi ng Dat abase I nst ances
Addi ng Redo Logs
Enabl i ng t hr eads f or al l Dat abase I nst ances
Set t i ng TEMP t abl espace
Addi ng UNDO t abl espaces
Addi ng Tr ace f i l es
Set t i ng Fl ash Recover y Ar ea
Updat i ng Or at ab
Cr eat i ng Passwor d f i l e( s)
Conf i gur i ng Li st ener s
Conf i gur i ng r el at ed CRS r esour ces
St ar t i ng Cl ust er Dat abase
<?xml ver si on="1. 0" ?>
<RConf i g ver si on="1. 1" >
<Conver t ToRAC>
<Conver t >
<Response>
<Resul t code="0" >
Operation Succeeded
</ Resul t >
</ Response>
<Ret ur nVal ue t ype="obj ect ">
<Or acl e_Home>
/ u01/ app/ or acl e/ pr oduct / 11. 2. 0/ dbhome_1
</ Or acl e_Home>
<Dat abase t ype="ADMI N_MANAGED" >






</ Dat abase> </ Ret ur nVal ue>

13
</ Conver t >
</ Conver t ToRAC></ RConf i g>
7. Post rconfig
Following rconfig, the SPFILE is now under Oracle ASM and has content similar to the
parameter list in the appendix at Post rconfig Database Parameter File.
Set the new environment on each node
dscgigdb03
expor t ORACLE_SI D=FRESH1
dscgigdb04
Note: do not set the ORA_NLS10 nor ORA_TZFILE environment variables at this
point.
Observe Database is Registered with the SCAN Listener
Also note that at this point the database is now registered with the SCAN listener and is not
using the EBS specific listener.
$ lsnrctl status

LSNRCTL f or Li nux: Ver si on 11. 2. 0. 2. 0 - Pr oduct i on on 02- J AN- 2011 14: 13: 20

Copyr i ght ( c) 1991, 2010, Or acl e. Al l r i ght s r eser ved.

Connect i ng t o ( ADDRESS=( PROTOCOL=t cp) ( HOST=) ( PORT=1521) )
STATUS of t he LI STENER
- - - - - - - - - - - - - - - - - - - - - - - -
Al i as LI STENER
Ver si on TNSLSNR f or Li nux: Ver si on 11. 2. 0. 2. 0 - Pr oduct i on
St ar t Dat e 01- J AN- 2011 16: 58: 13
Upt i me 2 days 21 hr . 15 mi n. 6 sec
Tr ace Level of f
Secur i t y ON: Local OS Aut hent i cat i on
SNMP OFF
Li st ener Par amet er Fi l e / u01/ app/ 11. 2. 0/ gr i d/ net wor k/ admi n/ l i st ener . or a
Li st ener Log Fi l e
/ u01/ app/ or acl e/ di ag/ t nsl snr / dscgi gdb03/ l i st ener / al er t / l og. xml
Li st eni ng Endpoi nt s Summar y. . .
( DESCRI PTI ON=( ADDRESS=( PROTOCOL=i pc) ( KEY=LI STENER) ) )
( DESCRI PTI ON=( ADDRESS=( PROTOCOL=t cp) ( HOST=10. 204. 74. 168) ( PORT=1521) ) )
( DESCRI PTI ON=( ADDRESS=( PROTOCOL=t cp) ( HOST=10. 204. 77. 181) ( PORT=1521) ) )
Ser vi ces Summar y. . .
Ser vi ce "+ASM" has 1 i nst ance( s) .
I nst ance "+ASM1", st at us READY, has 1 handl er ( s) f or t hi s ser vi ce. . .
Ser vi ce "FRESH" has 1 i nst ance( s) .
I nst ance "FRESH1", st at us READY, has 1 handl er ( s) f or t hi s ser vi ce. . .
The command compl et ed successf ul l y

14
$ srvctl config scan_listener
SCAN Li st ener LI STENER_SCAN1 exi st s. Por t : TCP: 1521
Remove the old SPFILE
The old spfile from the node where rconfig was run will still be under
$ORACLE_HOME/ dbs/ spf i l e${ORACLE_SI D}. or a. To eliminate any confusion,, remove that
file.
$ r m$ORACLE_HOME/ dbs/ spf i l e${ORACLE_SI D}. or a
Update the spfile
Refer to, Database Initialization Parameters for Oracle Applications Release 12 [MOS ID
396009.1] and update the spfile with any necessary changes.

For this example, DBUA removed the Oracle E-Business required underscore parameters,
so it is now necessary to restore them to the spfile. Execute the following in sqlplus:
alter system set "_b_tree_bitmap_plans"=FALSE scope=spfile;
alter system set "_disable_fast_validate"=TRUE scope=spfile;
alter system set "_fast_full_scan_enabled"=FALSE scope=spfile;
alter system set "_like_with_bind_as_equality"=TRUE scope=spfile;
alter system set "_optimizer_autostats_job"=FALSE scope=spfile;
alter system set "_sort_elimination_cost_ratio"=5 scope=spfile;
alter system set "_system_trig_enabled"=true scope=spfile;
alter system set "_trace_files_public"=TRUE scope=spfile;
Note that this is an example and you should still review Database Initialization
Parameters for Oracle Applications Release 12 [MOS ID 396009.1].
Restart the Database
$ sr vct l st op dat abase d FRESH
$ sr vct l st ar t dat abase d FRESH
Run Autoconfig on the Database Tier
Prepare the Database Tier Nodes for Autoconfig
Make sure the environment is set for the new ORACLE_HOME
expor t PATH=/ usr / ker ber os/ bi n: / usr / l ocal / bi n: / bi n: / usr / bi n: / home/ or acl e/ bi n
Set up the $ORACLE_HOME/appsutil directory tree.
On application administration node:
1. Generate the appsut i l . zi p for the database tier, run the following command:
per l $AD_TOP/ bi n/ admkappsut i l . pl

15
2. Copy the appsut i l . zi p file to each DB server node ORACLE_HOME
scp / ebs/ FRESH/ i nst / apps/ FRESH_haovm021/ admi n/ out / appsut i l . zi p
dscgi gdb03: / u01/ app/ or acl e/ pr oduct / 11. 2. 0/ dbhome_1
scp / ebs/ FRESH/ i nst / apps/ FRESH_haovm021/ admi n/ out / appsut i l . zi p
dscgi gdb04: / u01/ app/ or acl e/ pr oduct / 11. 2. 0/ dbhome_1
On each database node:
3. cd $ORACLE_HOME
4. unzip -o appsutil.zip
5. Copy the jre directory from the initial FRESH install ORACLE_HOME
cp - r / ebs/ FRESH/ db/ t ech_st / 11. 1. 0/ appsut i l / j r e .
6. Copy the jre directory to other database node(s) $ORACLE_HOME/appsutil
scp r appsut i l / j r e dscgi gdb04: `pwd`/ appsut i l
Deregister the current configuration
As the APPS user, run the following command on the primary database node to de-register the
current configuration:
sqlplus apps/apps
Connect ed.
SQL> exec fnd_conc_clone.setup_clean;

Prepare for use of the Single Client Access Name (SCAN)
As stated earlier under section, Upgrade Oracle E-Business Suite to use the SCAN (Optional),
the use of the SCAN is optional and there is a small availability risk. If this risk is not acceptable
and you choose not to use the SCAN listener then consult MOS ID 823587.1, Using Oracle 11g
Release 2 Real Application Clusters with Oracle E-Business Suite Release 12 and follow section 3.3.
Get SCAN Information
Continuing with this example and using the SCAN, when generating the database context file
you will be prompted for whether to enable the SCAN addresses for the Oracle E-Business Suite
database. You can get the necessary information with the following commands:
$ srvctl config scan_listener
$ srvctl config scan
SCAN name: dscgi g- scan, Net wor k: 1/ 10. 204. 77. 0/ 255. 255. 255. 0/
SCAN VI P name: scan1, I P: / dscgi g- scan. exampl e. com/ 10. 204. 77. 177
Add a Static SID to the Grid Infrastructure listener.ora
To run the initial database context file generation, the addition of a static Oracle System
Identifier (SID) to the grid infrastructure (GI) listener.ora is required to avoid a ORA- 12505,
TNS: l i st ener does not cur r ent l y know of SI D gi ven i n connect descr i pt or error. This

16
is only required on the first database node since the other database nodes will be able to utilize
the first database nodes newly defined network configuration.
1. Edit the GI listener.ora (/u01/app/11.2.0/grid/network/admin/listener.ora) and add the
following:
SI D_LI ST_LI STENER =
( SI D_LI ST =
( SI D_DESC =
( ORACLE_HOME= / u01/ app/ or acl e/ pr oduct / 11. 2. 0/ dbhome_1)
( SI D_NAME = FRESH1)
)
)

2. Reload the listener
$ l snr ct l r el oad
LSNRCTL f or Li nux: Ver si on 11. 2. 0. 2. 0 - Pr oduct i on on 02- J AN- 2011 07: 25: 34

Copyr i ght ( c) 1991, 2010, Or acl e. Al l r i ght s r eser ved.

Connect i ng t o ( ADDRESS=( PROTOCOL=t cp) ( HOST=) ( PORT=1521) )
The command compl et ed successf ul l y
Generate the Context File
Generate the context file on each database node (example steps and output are shown for only
dscgigdb03). Note that you need the SCAN information from Get SCAN Information above
to reply to some prompts.
1. generate the new context file
$ perl $ORACLE_HOME/appsutil/bin/adbldxml.pl
St ar t i ng cont ext f i l e gener at i on f or db t i er . .
Usi ng J VM f r om/ u01/ app/ or acl e/ pr oduct / 11. 2. 0/ dbhome_1/ j dk/ j r e/ bi n/ j ava t o
execut e j ava pr ogr ams. .
APPS Passwor d: apps

The l og f i l e f or t hi s adbl dxml sessi on i s l ocat ed at :
/ u01/ app/ or acl e/ pr oduct / 11. 2. 0/ dbhome_1/ appsut i l / l og/ adbl dxml _08170633. l og
AC- 20010: Er r or : Fi l e - l i st ener . or a coul d not be f ound at t he l ocat i on:

/ u01/ app/ or acl e/ pr oduct / 11. 2. 0/ dbhome_1/ net wor k/ admi n/ FRESH_dscgi gdb03/ l i st ene
r . or a
i ndi cat ed by TNS_ADMI N. Cont ext f i l e cannot be gener at ed.

Coul d not Connect t o t he Dat abase wi t h t he above par amet er s, Pl ease answer t he
Quest i ons bel ow

Ent er Host name of Dat abase ser ver : dscgigdb03

Ent er Por t of Dat abase ser ver : 1521

Ent er SI D of Dat abase ser ver : FRESH1

Do you want t o enabl e SCAN addr esses[ N] : Y

Speci f y val ue f or s_scan_name: dscgig-scan

Speci f y val ue f or s_scan_por t : 1521

17

Ent er t he val ue f or Di spl ay Var i abl e: dscgigdb03:1

The cont ext f i l e has been cr eat ed at :
/ u01/ app/ or acl e/ pr oduct / 11. 2. 0/ dbhome_1/ appsut i l / FRESH1_dscgi gdb03. xml
2. Review the log at $ORACLE_HOME/appsutil/log/adbldxml_<timestamp,
MMDDHHMI>.log

3. Edit the context file $ORACLE_HOME/ appsut i l / FRESH1_dscgi gdb03. xml
Set the value of s_virtual host_name to point to the virtual hostname for the database host
<host oa_var ="s_vi r t ual _host name">dscgig03-vip</ host >

Run Autoconfig on the First Database Node
1. Run autoconfig
$ $ORACLE_HOME/appsutil/bin/adconfig.sh
contextfile=/u01/app/oracle/product/11.2.0/dbhome_1/appsutil/FRESH1_dscgigdb03
.xml
Ent er t he APPS user passwor d:
The l og f i l e f or t hi s sessi on i s l ocat ed at :
/ u01/ app/ or acl e/ pr oduct / 11. 2. 0/ dbhome_1/ appsut i l / l og/ FRESH1_dscgi gdb03/ 0817063
5/ adconf i g. l og

Aut oConf i g i s conf i gur i ng t he Dat abase envi r onment . . .

Aut oConf i g wi l l consi der t he cust omt empl at es i f pr esent .
Usi ng ORACLE_HOME l ocat i on : / u01/ app/ or acl e/ pr oduct / 11. 2. 0/ dbhome_1
Cl asspat h :
: / u01/ app/ or acl e/ pr oduct / 11. 2. 0/ dbhome_1/ j dbc/ l i b/ oj dbc5. j ar : / u01/ app/ or acl e/ p
r oduct / 11. 2. 0/ dbhome_1/ appsut i l / j ava/ xml par ser v2. j ar : / u01/ app/ or acl e/ pr oduct / 1
1. 2. 0/ dbhome_1/ appsut i l / j ava: / u01/ app/ or acl e/ pr oduct / 11. 2. 0/ dbhome_1/ j l i b/ net c
f g. j ar : / u01/ app/ or acl e/ pr oduct / 11. 2. 0/ dbhome_1/ j l i b/ l dapj cl nt 11. j ar

Usi ng Cont ext f i l e :
/ u01/ app/ or acl e/ pr oduct / 11. 2. 0/ dbhome_1/ appsut i l / FRESH1_dscgi gdb03. xml

Cont ext Val ue Management wi l l now updat e t he Cont ext f i l e

Updat i ng Cont ext f i l e. . . COMPLETED

At t empt i ng upl oad of Cont ext f i l e and t empl at es t o
dat abase. . . COMPLETED

Updat i ng r dbms ver si on i n Cont ext f i l e t o db112
Updat i ng r dbms t ype i n Cont ext f i l e t o 64 bi t s
Conf i gur i ng t empl at es f r omORACLE_HOME . . .

Aut oConf i g compl et ed successf ul l y.
Post Autoconfig Steps on First Database Node
Setup to Use SRVCTL
This example does use the Real Applications Cluster server control utility (srvctl) to manage the
database cluster. To use srvctl to manage the database in conjunction with the database-side
autoconfig-generated network files requires the TNS_ADMIN directory path to be the same on

18
all nodes. This is accomplished by using the IFILE option in the generic network files under the
Grid Infrastructure ORACLE_HOME. As is recommended, we use the network files under the
Grid Infrastructure ORACLE_HOME, / u01/ app/ 11. 2. 0/ gr i d/ net wor k/ admi n and then
set the environment for the database in the Oracle Cluster Registry (OCR) with srvctl. Here are
the steps:
1. In the Grid Infrastructure ORACLE_HOME on each database node, set the default
network files to include (IFILE) the appropriate autoconfig generated network files under
t he $ORACLE_HOME/ net wor k/ admi n/ <CONTEXT_NAME> directory:
dscgigdb03
: : : : : : : : : : : : : :
l i st ener . or a
: : : : : : : : : : : : : :
i f i l e=/ u01/ app/ or acl e/ pr oduct / 11. 2. 0/ dbhome_1/ net wor k/ admi n/ FRESH1_dscgi gdb03/
l i st ener . or a
: : : : : : : : : : : : : :
sql net . or a
: : : : : : : : : : : : : :
I FI LE=/ u01/ app/ or acl e/ pr oduct / 11. 2. 0/ dbhome_1/ net wor k/ admi n/ FRESH1_dscgi gdb03/
sql net . or a
: : : : : : : : : : : : : :
t nsnames. or a
: : : : : : : : : : : : : :
I FI LE=u01/ app/ or acl e/ pr oduct / 11. 2. 0/ dbhome_1/ net wor k/ admi n/ FRESH1_dscgi gdb03/ t
nsnames. or a

2. Set the SDU in the sqlnet.ora ifile in the $ORACLE_HOME/ net wor k/ admi n/ <CONTEXT_NAME>
directory on each DB node:
: : : : : : : : : : : : : :
sql net _i f i l e. or a
: : : : : : : : : : : : : :
DEFAULT_SDU_SI ZE=32767
3. Set the database environment in OCR
sr vct l set env dat abase d FRESH T TNS_ADMI N=/ u01/ app/ 11. 2. 0/ gr i d/ net wor k/ admi n
4. Add the sourcing of the database applications environment file,
$ORACLE_HOME/ <CONTEXT_NAME>. env, to the database environment setup. For a sample
post-autoconfig environment file, see Database Node Post Autoconfig Environment File.
Run Autoconfig on All Other Database Nodes
Run AutoConfig on each database node. For more details of AutoConfig, see MOS ID
387859.1, Using AutoConfig to Manage System Configurations with Oracle E-Business Suite Release 12.
1. $ORACLE_HOME/ appsut i l / bi n/ adconf i g. sh
cont ext f i l e=/ u01/ app/ or acl e/ pr oduct / 11. 2. 0/ dbhome_1/ appsut i l / FRESH2_dscgi gdb04
. xml
2. Add the sourcing of the database applications environment file,
$ORACLE_HOME/ <CONTEXT_NAME>. env, to the database environment setup. For a sample
post-autoconfig environment file, see Database Node Post Autoconfig Environment File.
3. Update the GI network files to include the autoconfig generated network files.
dscgigdb04
: : : : : : : : : : : : : :

19
l i st ener . or a
: : : : : : : : : : : : : :
i f i l e=/ u01/ app/ or acl e/ pr oduct / 11. 2. 0/ dbhome_1/ net wor k/ admi n/ FRESH2_dscgi gdb04/
l i st ener . or a
: : : : : : : : : : : : : :
sql net . or a
: : : : : : : : : : : : : :
I FI LE=/ u01/ app/ or acl e/ pr oduct / 11. 2. 0/ dbhome_1/ net wor k/ admi n/ FRESH2_dscgi gdb04/
sql net . or a
: : : : : : : : : : : : : :
t nsnames. or a
: : : : : : : : : : : : : :
I FI LE=u01/ app/ or acl e/ pr oduct / 11. 2. 0/ dbhome_1/ net wor k/ admi n/ FRESH2_dscgi gdb04/ t
nsnames. or a
Run Autoconfig on Database Node One
To ensure all AutoConfig TNS aliases are set up to recognize all available nodes run autoconfig
once more on the initial database node, This is the second iteration on this node so that it has all
nodes as part of its known configuration now. For this example, run autoconfig once more on
node dscgigdb03.
$ $ORACLE_HOME/ appsut i l / bi n/ adconf i g. sh
cont ext f i l e=/ u01/ app/ or acl e/ pr oduct / 11. 2. 0/ dbhome_1/ appsut i l / FRESH1_dscgi gdb03
. xml
Run Autoconfig on the Application Tier
1. Run adgrants.sql
a. Copy $APPL_TOP/admin/adgrants.sql from the administration server node to the
database server node.
b. Use SQL*Plus to connect to the database as SYSDBA and run the script using the
following command:
$ sql pl us "/ as sysdba" @adgr ant s. sql [ APPS schema name]

2. Grant create procedure privilege on CTXSYS
a. Copy $AD_TOP/patch/115/sql/adctxprv.sql from the administration server node to
the database server node.
b. Use SQL*Plus to connect to the database as APPS and run the script using the
following command:
$ sql pl us apps/ [ APPS passwor d] @adct xpr v. sql [ SYSTEM passwor d] CTXSYS
3. Set CTXSYS parameter
Use SQL*Plus to connect to the database as SYSDBA and run the following command:
$ sql pl us "/ as sysdba"
SQL> exec ct xsys. ct x_adm. set _par amet er ( ' f i l e_access_r ol e' , ' publ i c' ) ;
On each application tier server node
4. Edit SI D= and PORT=<New l i st ener por t > in $TNS_ADMI N/ t nsnames. or a
file, to set up a connection to one of the instances in the Oracle RAC environment.
FRESH=

20
( DESCRI PTI ON=
( ADDRESS=( PROTOCOL=t cp) ( HOST=dscgi g03- vi p. us. or acl e. com) ( PORT=1521) )
( CONNECT_DATA=
( SERVI CE_NAME=FRESH)
( I NSTANCE_NAME=FRESH1)
)
)
5. Verify the connection from the applications tier node. This will use the TWO_TASK
setting.
sql pl us syst em/ wel come1
6. Validate Workflow Rules Set
On the administration server node, use SQL*Plus to connect to the database as APPS and
run the $FND_TOP/patch/115/sql/wfaqupfix.sql script using the following command:
$ sql pl us [ APPS user ] / [ APPS passwor d] @wf aqupf i x. sql [ APPLSYS user ] [ APPS
user ]
On each application tier server node
7. Edit the context variable j dbc_ur l in $CONTEXT_FI LE , changing the HOST, PORT,
SERVI CE_NAME and adding the I NSTANCE_NAME to the CONNECT_DATA parameter.
Before
<j dbc_ur l
oa_var ="s_apps_j dbc_connect _descr i pt or ">j dbc: or acl e: t hi n: @( DESCRI PTI ON=( ADDRES
S_LI ST=( LOAD_BALANCE=YES) ( FAI LOVER=YES) ( ADDRESS=( PROTOCOL=t cp) ( HOST=dscgi gdb03
. us. or acl e. com) ( PORT=1523) ) ) ( CONNECT_DATA=( SI D=FRESH) ) ) </ j dbc_ur l >
After
<j dbc_ur l
oa_var ="s_apps_j dbc_connect _descr i pt or ">j dbc: or acl e: t hi n: @( DESCRI PTI ON=( ADDRES
S_LI ST=( LOAD_BALANCE=YES) ( FAI LOVER=YES) ( ADDRESS=( PROTOCOL=t cp) ( HOST=dscgig-
scan.us.oracle.com) ( PORT=1521) ) ) ( CONNECT_DATA=( SERVI CE_NAME=FRESH)
(INSTANCE_NAME=FRESH1)) ) </ j dbc_ur l >
8. Run autoconfig
[ or acl e@haovm021 ~] $ $INST_TOP/admin/scripts/adautocfg.sh
Ent er t he APPS user passwor d:

The l og f i l e f or t hi s sessi on i s l ocat ed at :
/ ebs/ FRESH/ i nst / apps/ FRESH_haovm021
/ admi n/ l og/ 08160836/ adconf i g. l og

Aut oConf i g i s conf i gur i ng t he Appl i cat i ons envi r onment . . .

Aut oConf i g wi l l consi der t he cust omt empl at es i f pr esent .
Usi ng CONFI G_HOME l ocat i on : / ebs/ FRESH/ i nst / apps/ FRESH_haovm021
Cl asspat h :
/ ebs/ FRESH/ apps/ apps_st / comn/ j ava/ l i b/ apps
bor g2. zi p: / ebs/ FRESH/ apps/ apps_st / comn/ j ava/ cl asses

Usi ng Cont ext f i l e :
/ ebs/ FRESH/ i nst / apps/ FRESH_haovm021/ appl / admi n/ FRESH_haovm021. xml

Cont ext Val ue Management wi l l now updat e t he Cont ext f i l e

Updat i ng Cont ext f i l e. . . COMPLETED

21

At t empt i ng upl oad of Cont ext f i l e and t empl at es t o
dat abase. . . COMPLETED

Conf i gur i ng t empl at es f r omal l of t he pr oduct t ops. . .
Conf i gur i ng AD_TOP. . . . . . . . COMPLETED
Conf i gur i ng FND_TOP. . . . . . . COMPLETED
Conf i gur i ng I CX_TOP. . . . . . . COMPLETED
Conf i gur i ng MSC_TOP. . . . . . . COMPLETED
Conf i gur i ng I EO_TOP. . . . . . . COMPLETED
Conf i gur i ng BI S_TOP. . . . . . . COMPLETED
Conf i gur i ng AMS_TOP. . . . . . . COMPLETED
Conf i gur i ng CCT_TOP. . . . . . . COMPLETED
Conf i gur i ng WSH_TOP. . . . . . . COMPLETED
Conf i gur i ng CLN_TOP. . . . . . . COMPLETED
Conf i gur i ng OKE_TOP. . . . . . . COMPLETED
Conf i gur i ng OKL_TOP. . . . . . . COMPLETED
Conf i gur i ng OKS_TOP. . . . . . . COMPLETED
Conf i gur i ng CSF_TOP. . . . . . . COMPLETED
Conf i gur i ng I GS_TOP. . . . . . . COMPLETED
Conf i gur i ng I BY_TOP. . . . . . . COMPLETED
Conf i gur i ng J TF_TOP. . . . . . . COMPLETED
Conf i gur i ng MWA_TOP. . . . . . . COMPLETED
Conf i gur i ng CN_TOP. . . . . . . . COMPLETED
Conf i gur i ng CSI _TOP. . . . . . . COMPLETED
Conf i gur i ng WI P_TOP. . . . . . . COMPLETED
Conf i gur i ng CSE_TOP. . . . . . . COMPLETED
Conf i gur i ng EAM_TOP. . . . . . . COMPLETED
Conf i gur i ng FTE_TOP. . . . . . . COMPLETED
Conf i gur i ng ONT_TOP. . . . . . . COMPLETED
Conf i gur i ng AR_TOP. . . . . . . . COMPLETED
Conf i gur i ng AHL_TOP. . . . . . . COMPLETED
Conf i gur i ng OZF_TOP. . . . . . . COMPLETED
Conf i gur i ng I ES_TOP. . . . . . . COMPLETED
Conf i gur i ng CSD_TOP. . . . . . . COMPLETED
Conf i gur i ng I GC_TOP. . . . . . . COMPLETED

Aut oConf i g compl et ed successf ul l y.
Post autoconfig Configuration
Configure HugePages on Each Database Node
HugePages are not configured by default on the Oracle Exadata Database Machine.
Follow MOS ID 361468.1, HugePages on Oracle Linux 64-bit. Ensure that when running the
recommended script provided with MOS ID 401749.1 that the database is started.
For Oracle Database 11g release 11.2.0 there is an additional workaround required that is
described in MOS ID 983715.1, 11gR2 Grid Infrastructure Does not Use ULIMIT Setting
Appropriately.
Gather Statistics for SYS Schema
1. Copy $APPL_TOP/ admi n/ adst at s. sql from the administration server node to the database
server node work directory:
cp $APPL_TOP/ admi n/ adst at s. sql / ebs/ expi mp

22
2. Run the script.
sql pl us "/ as sysdba"
al t er syst emenabl e r est r i ct ed sessi on;
@adst at s. sql

sql pl us "/ as sysdba"
al t er syst emdi sabl e r est r i ct ed sessi on;
Re-Create Grants and Synonyms
On the APPS node: execute adadmi n and then select 4. Maintain Applications Database
Entities menu and then select 2. Re-create grants and synonyms for APPS schema
Recompile the APPS Schema
On the APPS node: execute adadmin and then select Compile/Reload Applications Database
Entities and then select 1. Compile APPS schema
Start Applications Tier Processes
$I NST_TOP/ admi n/ scr i pt s/ adst r t al . sh
Synchronize Workflow Views
1. Log on to Oracle E-Business Suite with the "System Administrator" responsibility.
1. Select Requests > Run > Single Request and click the OK button. Enter the following
parameters:
Request Name = Workflow Directory Services User/Role Validation
Batch size = 10000
Fix Dangling Users = Yes
Add missing user/role assignments = Yes
Update WHO columns in WF tables = No
2. Click OK and Submit.
3. View the log file. A successful run should contain the following:
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - +
Appl i cat i on Obj ect Li br ar y: Ver si on : 12. 0. 0

Copyr i ght ( c) 1979, 1999, Or acl e Cor por at i on. Al l r i ght s r eser ved.

FNDWFDSURV modul e: Wor kf l ow Di r ect or y Ser vi ces User / Rol e Val i dat i on
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - +

Cur r ent syst emt i me i s 02- J AN- 2011 11: 27: 34

+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - +

**St ar t s**02- J AN- 2011 11: 27: 34
**Ends**02- J AN- 2011 11: 28: 07

+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - +
Execut i ng r equest compl et i on opt i ons. . .

Out put f i l e si ze:

23
0

+- - - - - - - - - - - - - 1) PRI NT - - - - - - - - - - - - - +
Di sabl i ng r equest ed Out put Post Pr ocessi ng. Not hi ng t o pr ocess. The out put
of t he r equest i s zer o byt e.
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - +

Fi ni shed execut i ng r equest compl et i on opt i ons.

+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - +
Concur r ent r equest compl et ed successf ul l y
Cur r ent syst emt i me i s 02- J AN- 2011 11: 28: 07

+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - +
Further Configuration
The following steps are beyond the scope of this paper but are well documented in the
references listed. To complete the full high availability install for the Oracle E-Business Suite
you should also follow these documented processes:
Clone Application Nodes
Cloning application tier nodes adds redundancy to the Oracle E-Business system for improved
availability and scalability to handle increasing workloads. The steps for cloning are detailed in
Cloning Oracle Applications Release 12 with Rapid Clone [MOS ID 406982.1].
Setup Parallel Concurrent Processing
To set up Parallel Concurrent Processing (PCP), you must have more than one Concurrent
Processing node in your environment. If you do not have this, follow the appropriate
instructions in MOS ID 406982.1, Cloning Oracle Applications Release 12 with Rapid Clone.
The steps for setting up PCP are documented in section 3.9 Configure Parallel Concurrent
Processing of Using Oracle 11g Release 2 Real Application Clusters with Oracle E-Business Suite Release
12, [MOS ID 823587.1].
Set Up Load Balancing
Load balancing can be defined as the technology and associated processes that distribute a
website's traffic among several machines in a cluster using a network-based device called a server
load balancer. Cluster architectures allow all members of a group of machines to run the same web
application, appearing to the outside world as a single machine.
A server load balancer intercepts traffic destined for a site, and redirects it to various machines in
the cluster according to the particular load-balancing method chosen. This optimizes use of
system resources, resulting in higher performance, availability and scalability. Load balancers are
recommended for mission-critical enterprise deployments of web-based applications such as
Oracle E-Business Suite. For details on configuring a load balancer with the Oracle E-Business
Suite see the following references:

24
MOS ID 727171.1 - Implementing Load Balancing On Oracle E-Business Suite - Documentation
For Specific Load Balancer Hardware
MOS ID 380489.1 - Using Load-Balancers with Oracle E-Business Suite Release 12. (this is
linked to in MOS ID 727171.1)
Oracle E-Business Suite 12 (BIG-IP LTM, WebAccelerator, FirePass)
Conclusion
A successful installation of the Oracle E-Business Suite database on the Oracle Exadata Database
Machine is dependent upon thorough preparation that includes planning, testing, and review of
all the steps involved. The intent of this paper was to illustrate the steps to install Oracle E-
Business Suite R12 with Oracle Database 11g release 11.2 using Oracle RAC and Oracle ASM on
the Oracle Exadata Database Machine. The process entails referring to multiple Oracle MOS
IDs that are referenced herein with explicit examples included. Any improvements to this
process will be updated in this paper and reposted to the Maximum Availability Architecture
website at http://www.oracle.com/goto/maa.

25
Appendix
Test Environment Details
The hardware and software details for the test environment are as follows:
Application Tier Node
Name: haovm021.us.oracle.com
Oracle Enterprise Linux 2.6.18-194.3.1.0.2.el5 x86_64
E_Business Suite Version 12.1.1
ORACLE_HOME /ebs/FRESH/apps/tech_st/10.1.2
$APPL_TOP /ebs/FRESH/apps/apps_st/appl
$INST_TOP /ebs/FRESH/inst/apps/FRESH_haovm021
NFS mounted storage from dscbbg03: / expor t 2/ on / ebs
Target Database System
Oracle Exadata Database Machine quarter rack
Compute Nodes
Names: dscgigdb03 and dscgigdb04
IP Addresses
- dscgigdb03 10.204.74.168
- dscgig03-vip 10.204.77.181
- dscgigdb04 10.204.74.169
- dscgig04-vip 10.204.77.182
- dscgig-scan 10.204.77.177, 10.204.77.178, 10.204.77.179
$ nslookup dscgig-scan
Server: 144.20.190.70
Address: 144.20.190.70#53

Name: dscgig-scan.us.oracle.com
Address: 10.204.77.177
Address: 10.204.77.178
Address: 10.204.77.179
See http://www.oracle.com/technetwork/database/clustering/overview/scan-
129069.pdf for understanding the Oracle RAC Single Client Access Name
(SCAN) configuration.
Initial Database Rapid Install ORACLE_HOME
- /ebs/FRESH/db/tech_st/11.1.0

26
- ORACLE_SID=FRESH
- DB_NAME=FRESH
- Listener name = FRESH
Target Database ORACLE_HOME
- 11.2.0.2
/u01/app/oracle/product/11.2.0/dbhome_1
- ORACLE_SID=FRESH1 and FRESH2 respectively
- DB_NAME=FRESH
Grid ORACLE_HOME 11.2.0.2
/u01/app/11.2.0/grid
ASM ORACLE_SID=+ASM1 and +ASM2 respectively
ASM Diskgroups: +DATA and +RECO
DB_NAME=FRESH Each with:
Oracle Enterprise Linux 2.6.18-194.3.1.0.2.el5 x86_64
Oracle Enterprise Edition 11.2.0.2
2 Quad-Core Intel Xeon E5540 Processors (2.53 GHz)
72 GB memory
Disk Controller HBA with 512MB Battery Backed Write Cache
4 x 146 GB SAS 10,000 RPM disks
Dual-Port QDR InfiniBand Host Channel Adapter
4 Embedded Gigabit Ethernet Ports
Storage:
NFS mounted storage from dscbbg03:/export2/ on /ebs
mount dscbbg03: / expor t 2/ ebs / ebs - o r w, bg, har d, noi nt r , \
r si ze=32768, wsi ze=32768, t cp, noac, ver s=3, t i meo=600, nol ock
See How to Optimize NFS Performance with NFS options. [ID 397194.1] for NFS mount
option details
3 Exadata Cells (dscgigcel05-07)
Each cell with:
2 Quad-core Intel Xeon E5540 (2.53GHz) processors
Exadata Smart Flash Cache 384 GB
12 x 1TB 7,200 RPM SATA drives
Create a Local File System
These are the steps for creating a local file system on the database machine.
1. Display the logical volume group:
[ r oot @dscgi gdb03 ~] # vgdisplay
- - - Vol ume gr oup - - -

27
VG Name VGExaDb
Syst emI D
For mat l vm2
Met adat a Ar eas 1
Met adat a Sequence No 4
VG Access r ead/ wr i t e
VG St at us r esi zabl e
MAX LV 0
Cur LV 3
Open LV 3
Max PV 0
Cur PV 1
Act PV 1
VG Si ze 278. 34 GB
PE Si ze 4. 00 MB
Tot al PE 71255
Al l oc PE / Si ze 39424 / 154. 00 GB
Fr ee PE / Si ze 31831 / 124. 34 GB
VG UUI D Lvh7nE- o6z1- Tl oU- 5APF- SKYz- U8nL- sZMvf X
2. Create a logical volume in an existing volume group:
[ r oot @dscgi gdb03 ~] # lvcreate -L 110G -n /dev/VGExaDb/EBSpar
Logi cal vol ume "EBSpar " cr eat ed
3. Create the file system:
[ r oot @dscgi gdb03 ~] # mkfs.ext3 -m 0 -b 4096 /dev/VGExaDb/EBSpar
mke2f s 1. 39 ( 29- May- 2006)
Fi l esyst eml abel =
OS t ype: Li nux
Bl ock si ze=4096 ( l og=2)
Fr agment si ze=4096 ( l og=2)
14417920 i nodes, 28835840 bl ocks
0 bl ocks ( 0. 00%) r eser ved f or t he super user
Fi r st dat a bl ock=0
Maxi mumf i l esyst embl ocks=4294967296
880 bl ock gr oups
32768 bl ocks per gr oup, 32768 f r agment s per gr oup
16384 i nodes per gr oup
Super bl ock backups st or ed on bl ocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632,
2654208,
4096000, 7962624, 11239424, 20480000, 23887872

Wr i t i ng i node t abl es: done
Cr eat i ng j our nal ( 32768 bl ocks) : done
Wr i t i ng super bl ocks and f i l esyst emaccount i ng i nf or mat i on: done

Thi s f i l esyst emwi l l be aut omat i cal l y checked ever y 31 mount s or
180 days, whi chever comes f i r st . Use t une2f s - c or - i t o over r i de.
4. Mount the file system:
[ r oot @dscgi gdb03 ~] # mkdir p /ebs/stage
[ r oot @dscgi gdb03 ~] # mount /dev/VGExaDb/EBSpar /ebs/stage
Rapid Install Standard Installation Database Parameter File
This file was the initial single-instance Rapid Install Standard Installation database parameter file
that is Oracle Database 11g release 11.1.0.7.
###########################################################################

28
# $Header : af i ni t _db111. or a 120. 4 2008/ 07/ 03 07: 12: 03 upi nj ar k noshi p $
#
# Or acl e Appl i cat i ons 11i - i ni t . or a
#
# Thi s f i l e cont ai ns a l i st i ng of i ni t . or a par amet er s f or 11. 1.
#
# Thi s i s a r ef er ence f i l e and cont ai ns t he maj or i ni t i al i zat i on
# par amet er s used i n Or acl e Appl i cat i ons.
#
# I t i s di vi ded i nt o t wo mai n sect i ons:
#
# Gener al Par amet er s
# Opt i mi zer Par amet er s
#
# Gener al Par amet er s
#
# Some of t he gener al par amet er s ar e mandat or y and ar e not ed
# as such. Al l ot her s pr ovi de good i ni t i al val ues but may need
# t o be i ncr eased dependi ng on t he number of user s.
#
# Opt i mi zer Par amet er s
#
# Al l opt i mi zer par amet er s ar e mandat or y. Par amet er s st ar t i ng
# wi t h a l eadi ng under scor e ar e def i ned as undocument ed. No
# undocument ed opt i mi zer par amet er must be set ot her t han t hose
# l i st ed i n t hi s sect i on.
#
###########################################################################

#########
#
# Dat abase par amet er s
#
# The dat abase par amet er s def i ne t he name of t he dat abase and t he names
# of t he cont r ol f i l es.
#
# The dat abase name i s est abl i shed when t he dat abase i s bui l t , and f or
# most cust omer s mat ches t he i nst ance name. I t shoul d not nor mal l y be
# necessar y t o change t he dat abase name, except f or t he pur poses of
# dat abase cl oni ng.
#
# Ther e shoul d be at l east t wo cont r ol f i l es, pr ef er abl y t hr ee,
# l ocat ed on di f f er ent di sks. The cont r ol f i l es can dynami cal l y gr ow,
# so al l ow at l east 20M per f i l e f or gr owt h.
#
#########

db_name = FRESH
cont r ol _f i l es =
/ ebs/ FRESH/ db/ apps_st / dat a/ cnt r l 01. dbf , / ebs/ FRESH/ db/ apps_st / dat a/ cnt r l 02. dbf ,
/ ebs/ FRESH/ db/ apps_st / dat a/ cnt r l 03. dbf

#########
#
# Dat abase bl ock si ze
#
# The r equi r ed bl ock si ze f or Or acl e Appl i cat i ons i s 8K.
#
#########

db_bl ock_si ze = 8192

#########

29
#
# Compat i bl e
#
# Compat i bi l i t y shoul d be set t o t he cur r ent r el ease.
#
#########

compat i bl e = 11. 1. 0

#########
#
# _syst em_t r i g_enabl ed
#
# The _syst em_t r i g_enabl ed shoul d nor mal l y be set t o TRUE.
# I f t he _syst em_t r i g_enabl ed par amet er i s set t o FALSE i t wi l l
# di sabl e syst emt r i gger s f r ombei ng execut ed.
#
#########

_syst em_t r i g_enabl ed = t r ue

#########
#
# O7_DI CTI ONARY_ACCESSI BI LI TY
#
# O7_DI CTI ONARY_ACCESSI BI LI TY shoul d be l ef t t o i t s def aul t val ue
# of FALSE i n 10g Dat abase. ( Bug 4768492) .
#
#########

#########
#
# Requi r ed par amet er s.
#
# These par amet er s ar e r equi r ed f or Or acl e Appl i cat i ons and MUST NOT
# be changed.
#
#########

#########
# NLS par amet er s
#
# Some NLS par amet er val ues ar e mar ked as bei ng r equi r ed 11i set t i ngs.
# These ar e t he onl y suppor t ed set t i ngs f or t hese par amet er s f or
# Appl i cat i ons 11i and must not be modi f i ed t o ot her val ues.
# Ot her NLS par amet er s have been gi ven def aul t val ues.
#########
nl s_l anguage = amer i can
nl s_t er r i t or y = amer i ca
nl s_dat e_f or mat = DD- MON- RR
nl s_numer i c_char act er s = ". , "
nl s_sor t = bi nar y # Requi r ed 11i set t i ng
nl s_comp = bi nar y # Requi r ed 11i set t i ng
nl s_l engt h_semant i cs = BYTE # Requi r ed 11i set t i ng

#########
#
# Mul t i - t hr eaded Ser ver ( MTS)
#
# Most Or acl e Appl i cat i ons cust omer s DO NOT need t o use MTS, and t he
# def aul t i s t o l eave i t di sabl ed.
#

30
# I f MTS i s used, i t can have a dr amat i c ef f ect on t he SGA, as sessi on
# memor y, i ncl udi ng sor t and cur sor ar eas, i s t aken f r omt he SGA.
#
# Conf i gur i ng MTS r equi r es t he l ar ge pool t o be al l ocat ed. The
# mi ni mumsi ze f or t he l ar ge pool i s 50M.
#
#########

#########
#
# Audi t i ng and Secur i t y
#
# Logon audi t i ng i s ver y usef ul i n det er mi ni ng t he I / O pr of i l e of
# bat ch ( concur r ent manager ) pr ocesses. Thi s i nf or mat i on wi l l be
# avai l abl e i n FND_CONCURRENT_REQUESTS i n a l at er r el ease of Or acl e
# Appl i cat i ons.
#
# The cost of l og on audi t i ng i s mi ni mal , and t he onl y addi t i onal
# r equi r ement i s f or a housekeepi ng pr ocedur e t o per i odi cal l y
# pur ge t he SYS. AUD$ t abl e. St at ement l evel audi t i ng i s not r ecommended.
#
# Some pr oduct s r equi r e max_enabl ed_r ol es t o be set . Thi s shoul d be set
# t o a mi ni mumof 40, al t hough hi gher val ues ar e qui t e accept abl e.
#
#########

#audi t _t r ai l = t r ue # i f you want audi t i ng

########
#
# Dump par amet er s
#
# These speci f y t he dest i nat i on of t he t r ace and cor e f i l es, and woul d
# nor mal l y poi nt i nt o t he appr opr i at e OFA t r ace di r ect or i es.
# The maxi mumsi ze of a dump f i l e can be changed at t he sessi on l evel ,
# and pr event s a t r ace f i l e usi ng an excessi ve amount of di sk space.
#
########

#user _dump_dest =
/ ebs/ FRESH/ db/ t ech_st / 11. 1. 0/ admi n/ FRESH_dscgi gdb03/ udump
#backgr ound_dump_dest =
/ ebs/ FRESH/ db/ t ech_st / 11. 1. 0/ admi n/ FRESH_dscgi gdb03/ bdump
#cor e_dump_dest =
/ ebs/ FRESH/ db/ t ech_st / 11. 1. 0/ admi n/ FRESH_dscgi gdb03/ cdump
di agnost i c_dest =
/ ebs/ FRESH/ db/ t ech_st / 11. 1. 0/ admi n/ FRESH_dscgi gdb03

max_dump_f i l e_si ze = 20480 # t r ace f i l e si ze

########
#
# Ti med st at i st i cs
#
# On most pl at f or ms, enabl i ng t i med st at i st i cs has mi ni mal ef f ect on
# per f or mance. Ther e ar e a handf ul of except i ons. I t can be
# enabl ed/ di sabl ed dynami cal l y at bot h t he syst emand sessi on l evel .
#
# Thi s i nf or mat i on i s used by many opt i ons, i ncl udi ng SQL_TRACE,
# Or acl e Tr ace, st at spack and Or acl e Ent er pr i se Manager .
#
########

31
t i med_st at i st i cs = t r ue

########
#
# Tr ace par amet er s
#
########

# _t r ace_f i l es_publ i c
#
# As t he dat a ser ver machi ne shoul d be i n a secur e envi r onment ,
# set t i ng t o t r ue enabl es t r ace f i l e anal ysi s.

_t r ace_f i l es_publ i c = TRUE

########
#
# Fi xed SGA
#
# The f i xed SGA par amet er s r epr esent r esour ces t hat have t hei r si ze
# f i xed on st ar t up. I f t he maxi mumsi ze i s r eached ( e. g. no of
# sessi ons ) , t hen t he r esour ce i s unavai l abl e unt i l f r eed by t he
# i nst ance.
#
########

# Pr ocesses/ sessi ons
#
# A dat abase pr ocess can be associ at ed wi t h one or mor e dat abase
# sessi ons. For al l t echnol ogi es ot her t han FORMS, you can assume
# a 1- t o- 1 mappi ng bet ween sessi ons and pr ocesess.
#
# For FORMS pr ocesses, t her e wi l l be one dat abase sessi on per open f or m,
# wi t h a mi ni mumof t wo open f or ms( sessi ons) .
#
# Ei t her expl i ci t y set sessi ons accor di ngl y or j ust doubl e t he
# number of pr ocesses.
#
# The ot her par amet er s wi l l depend on t he speci f i c i nst al l at i on, but t he
# val ues gi ven ar e not unt ypi cal of many Or acl e Appl i cat i ons cust omer s.

pr ocesses = 200 # Max. no. of user s x 2
sessi ons = 400 # 2 X pr ocesses
db_f i l es = 512 # Max. no. of dat abase f i l es
dml _l ocks = 10000
cur sor _shar i ng = EXACT # Requi r ed 11i set t t i ng
open_cur sor s = 600 # Consumes pr ocess memor y, unl ess usi ng
MTS.
sessi on_cached_cur sor s = 500

########
#
# Cache Si zes
#
# For 10g, t he aut omat i c SGA t uni ng opt i on i s r equi r ed.
# Thi s avoi ds t he need t o i ndi vi dual l y t une t he di f f er ent
# SGA caches such as t he buf f er cache, shar ed pool , l ar ge
# pool , et c. . The aut omat i c SGA t uni ng opt i on i mpr oves
# over al l per f or mance and i mpr oves manageabi l i t y.
#
# SGA t ar get r ef er s t o t he t ot al si ze of t he SGA i ncl udi ng
# al l t he sub- caches such as t he buf f er cache, l og buf f er ,
# shar ed pool , l ar ge pool , et c. . Ref er t o t he si zi ng t abl e

32
# i n t he sect i on Dat abase I ni t i al i zat i on Par amet er Si zi ng f or
# si zi ng r ecommendat i ons f or sga_t ar get .
#
# Al so, i t i s r ecommended t o use a Ser ver Par amet er f i l e
# ( i . e. SPFI LE) t o st or e t he i ni t i al i zat i on par amet er
# val ues when sga_t ar get i s bei ng used. The Aut omat i c
# SGA t uni ng opt i on ( sga_t ar get ) dynami cal l y si zes t he
# i ndi vi dual caches such as t he buf f er cache and shar ed pool .
# Usi ng an SPFI LE al l ows t he dynami cal l y adj ust ed val ues t o
# per si st acr oss r est ar t s. Pl ease r ef er t o t he
# Dat abase Admi ni st r at or ' s Gui de f or i nf or mat i on on how
# t o cr eat e and mai nt ai n an SPFI LE.
#
#
########

sga_t ar get = 1G

########
#
# Shar ed Pool
#
# I t i s i mpor t ant t o t une t he shar ed pool so as t o mi ni mi ze
# cont ent i on f or SQL and PL/ SQL obj ect s. A val ue of 400M i s a
# r easonabl e st ar t i ng poi nt f or 11i , and aut omat i c SGA
# t uni ng wi l l adj ust t he caches as per t he wor kl oad.
# The val ues bel ow f or t he shar ed pool r el at ed caches
# ar e si mpl y mi ni mumval ues ( i . e. st ar t i ng val ues) .
#
########

shar ed_pool _si ze = 400M
shar ed_pool _r eser ved_si ze = 40M

########
#
#
# Db Bl ock Checki ng
#
#
#
########

db_bl ock_checki ng = FALSE
db_bl ock_checksum = TRUE

########
#
# Log Wr i t er
#
# The l og wr i t er par amet er s cont r ol t he si ze of t he l og buf f er
# wi t hi n t he SGA and how f r equent l y t he r edo l ogs ar e check
# poi nt ed ( al l di r t y buf f er s wr i t t en t o di sk t o cr eat e a new
# r ecover y poi nt ) .
#
# The checkpoi nt i nt er val and t i meout cont r ol t he f r equency of
# checkpoi nt s.
#
########

l og_checkpoi nt _t i meout = 1200 # Checkpoi nt at l east ever y 20 mi ns.
l og_checkpoi nt _i nt er val = 100000
l og_checkpoi nt s_t o_al er t = TRUE

33
l og_buf f er = 10485760

########
#
# Rol l back segment s
#
# As of 9i R2, Or acl e Appl i cat i ons r equi r es t he use of Syst emManaged Undo.
# Syst emManaged Undo i s much mor e ef f i ci ent , and r educes t he chances
# of snapshot t oo ol d er r or s. I n addi t i on, i t i s much easi er t o
# manage and admi ni st er syst emmanaged undo t han manual l y managi ng
# r ol l back segment s.
#
# Not e:
#
# Or acl e Appl i cat i ons wi l l f unct i on cor r ect l y usi ng r ol l back segment s
# but Or acl e r ecommends t hat cust omer s move t o Syst emManaged Undo.
#
# To use Syst emManaged Undo, you must cr eat e an UNDO t abl espace.
#
########

#r ol l back_segment s = ( _syssmu16_1232623801$, _syssmu17_1232623801$,
_syssmu18_1232623801$, _syssmu19_1232623801$, _syssmu20_1232623801$,
_syssmu27_1232623801$, _syssmu28_1232623801$, _syssmu29_1232623801$)

# undo_management
#
# Set t o AUTO t o enabl e Syst emManaged Undo

undo_management =AUTO # Requi r ed 11i set t i ng

#
# undo_t abl espace
#
# The name of t he Syst emManaged Undo t abl espace.
#

undo_t abl espace=APPS_UNDOTS1 # Requi r ed 11i set t i ng

########
#
# Sor t Ar ea / Hash Ar ea Si ze
#
# As of 9i R2, t he aut o. memor y manager i s bei ng used. Thi s avoi ds t he
# need t o manual l y t une sor t _ar ea_si ze and hash_ar ea_si ze.
# Aut o. Memor y Manager al so i mpr oves per f or mance and scal abi l i t y
# as t he memor y i s r el eased t o t he OS af t er t he cal l .
#
# Al t hough manual t uni ng vi a sor t _ar ea_si ze/ hash_ar ea_si ze i s st i l l
# suppor t ed, i t i s st r ongl y r ecommended t hat cust omer s conver t t o
# aut omat i c wor kar ea management .
#
########

#
# wor kar ea_si ze_pol i cy
#
# Set t o AUTO t o enabl e aut omat i c wor kar ea management .
#

wor kar ea_si ze_pol i cy=AUTO # Requi r ed 11i set t i ng

34

ol ap_page_pool _si ze = 4194304

#
# pga_aggr egat e_t ar get
#
# pga_aggr egat e_t ar get i s t he t ot al memor y avai l abl e f or wor k ar ea
# oper at i ons ( pr edomi nant l y sor t s ) . The avai l abl e memor y wi l l gr ow
# and shr i nk as t he wor kl oad changes.
#
# Set t o l ow, i t wi l l have a dr amat i c ef f ect on per f or mance, as
# sor t oper at i ons wi l l be f or ced t o di sk. The r ecommended mi ni mum
# i s 1G, al t hough f or smal l t est or demo syst ems, 500M i s accept abl e.
#
# The upper bound i s det er mi ned by t he avai l abl e memor y al l ocat ed t o
# t he i nst ance. Once you' ve subt r act ed O/ S over head, and memor y used
# by ot her syst ems, 95%of i nst ance memor y i s account ed f or by:
#
# SGA Pool s - shar ed_pool , j ava_pool and l ar ge_pool
# db_bl ock_buf f er s
# pga_aggr egat e_t ar get
#
# Never set pga_aggr egat e_t ar get such t hat t ot al al l ocat ed memor y wi l l be
# gr eat er t han physi cal memor y, or t he ser ver wi l l swap and cause
# sever e per f or mance pr obl ems.
#
# Use st at spack t o det er mi ne t he opt i mumt ar get . However , a si mpl e r ul e
# of t humb woul d be 2M per dat abase sessi on.

pga_aggr egat e_t ar get =1G

# cur sor _space_f or _t i me
#
# Reduces cont ent i on wi t hi n t he shar ed pool but r equi r es at l east a 50%
# i ncr ease i n t he shar ed pool . Onl y set on t he advi ce of Or acl e Suppor t
# or Devel opment .

#########
#
# PL/ SQL Par amet er s
#
# The f ol l owi ng par amet er s ar e used t o enabl e t he PL/ SQL
# gl obal opt i mi zer as wel l as nat i ve compi l at i on.
#
# Or acl e Appl i cat i ons uses PL/ SQL I nt er pr et ed
# compi l at i on as def aul t f or 10g based Apps envi r onment s.
# To use PL/ SQL Nat i ve compi l at i on set pl sql _code_t ype t o
# NATI VE and t he par amet er ( pl sql _nat i ve_l i br ar y_di r ) shoul d
# be set t o t he di r ect or y pat h whi ch wi l l be used t o st or e
# t he shar ed l i br ar i es gener at ed as par t of nat i ve
# compi l at i on. Or acl e Cor por at i on r ecommends t hat you
# cr eat e t he shar ed l i br ar y di r ect or y as a subdi r ect or y
# wher e t he dat a f i l es ar e l ocat ed.
#
#
# The ut l _f i l e_di r must be set as per t he i nst al l at i on manual s.
# ut l _f i l e_di r = <di r 1>, <di r 2> . . .
#
#
#########

pl sql _opt i mi ze_l evel = 2 # Requi r ed 11i set t i ng

35

pl sql _code_t ype = I NTERPRETED # Def aul t 11i set t i ng

pl sql _nat i ve_l i br ar y_di r = / ebs/ FRESH/ db/ t ech_st / 11. 1. 0/ pl sql / nat i vel i b

pl sql _nat i ve_l i br ar y_subdi r _count = 149

ut l _f i l e_di r =
/ usr / t mp, / usr / t mp, / ebs/ FRESH/ db/ t ech_st / 11. 1. 0/ appsut i l / out bound/ FRESH_dscgi gd
b03, / usr / t mp

########
#
# Advanced Queui ng ( AQ) and J ob Queues
#
# AQ r equi r es t he TM pr ocess t o handl e del ayed messages. A number
# of Appl i cat i on modul es use AQ, i ncl udi ng wor kf l ow. J ob Queues
# enabl e advanced queue t o submi t backgr ound j obs.
#
# j ob_queue_i nt er val i s obsol et e and shoul d no l onger be r equi r ed.
# I t i s now an undocument ed par amet er ( _j ob_queue_i nt er val ) .
########

aq_t m_pr ocesses = 1
j ob_queue_pr ocesses = 2

########
#
# Ar chi vi ng
#
# Ar chi vi ng par amet er s, i ncl udi ng dest i nat i on ( opt i onal l y mul t i pl e
# dest i nat i ons i n 9i ) need t o be speci f i ed.
#
########

# l og_ar chi ve_st ar t = t r ue # i f you want aut omat i c ar chi vi ng

########
#
# Par al l el Quer y
#
# Not nor mal l y r equi r ed f or OLTP syst ems. I f enabl ed, t abl es/ i ndexes
# MUST NOT have degr ee set . Use hi nt s t o enabl e par al l el quer y.
#
# To use t he par al l el opt i on wi t h DBMS_STATS ( FND_STATS ) i n 11i ,
# par al l el _max_ser ver s must be set - i t i s not a dynami c par amet er . I t
# shoul d be set based on t he number of avai l abl e CPUs. Exampl es ar e
# gi ven bel ow but may need t o be al t er ed. These ar e r easonabl e val ues
# f or DBMS_STATS.
#
# Par al l el Quer y uses t he l ar ge_pool f or message buf f er s and t he
# l ar ge_pool _si ze may t her ef or e need t o be speci f i ed
# - see above f or gui del i nes.
#
########

par al l el _max_ser ver s = 8
par al l el _mi n_ser ver s = 0

########
#
# Event s
#

36
# Event s ar e used by Or acl e Suppor t and Devel opment . They shoul d onl y be
# set as r equest ed.
#
# The f ol l owi ng event s ( i f any) shoul d be set .
#
########

########
#
# Pl at f or mspeci f i c par amet er s
#
########

#
# spi n_count
#
# Thi s par amet er i s used on SMP pl at f or ms. I t det er mi nes how l ong t o
# spi n t r yi ng t o acqui r e excl usi ve access t o l ow- l evel SGA dat a
# st r uct ur es.
#
# Wi t h 8i , t hi s par amet er i s undocument ed and SHOULD NEVER be set except
# at t he r equest of Or acl e Suppor t .

#########
#
# Dat abase Passwor ds - Case Sensi t i vi t y ( 11g f eat ur e)
#
# Dat abase passwor d case sensi t i vi t y i s a new f eat ur e avai l abl e wi t h 11g
# But as Appl i cat i ons t i er do not suppor t case sensi t i ve dat abase passwor ds,
# t i l l t hen t hi s f eat ur e cannot be used by def aul t and set t o FALSE.
#
# To Enabl e/ Di sabl e set SEC_CASE_SENSI TI VE_LOGON t o TRUE/ FALSE
#
#########

sec_case_sensi t i ve_l ogon = FALSE

# - - - - - - - - - - - - - - - - - - - MANDATORY OPTI MI ZER PARAMETERS - - - - - - - - - - - - - - - - - - - - - -

###########################################################################
# CBO par amet er s
###########################################################################

#########
#
# Opt i mi zer
#
# Rel ease 11i uses t he Cost Based Opt i mi zer ( CBO) . The
# f ol l owi ng opt i mi zer par amet er s MUST be set as bel ow, and shoul d not
# be changed.
#
#########

_b_t r ee_bi t map_pl ans = FALSE # Requi r ed 11i set t i ng

_i ndex_j oi n_enabl ed = FALSE # Requi r ed 11i set t i ng

#########
# _l i ke_wi t h_bi nd_as_equal i t y

37
#
# Thi s par amet er f or ces t he opt i mi zer t o t r eat expr essi ons of t he f or m
# [ i ndexed- col umn l i ke : b1] si mi l ar t o [ i ndex- col umn = : b1] .
# Or acl e Apps has many quer i es whi ch use t he LI KE oper at or on i ndexed
# col umns wi t h bi nds. Si nce bi nds ar e i nvol ved, t he CBO assi gns
# i nt er nal def aul t sel ect i vi t y est i mat es f or t he LI KE oper at or ( 5%) ,
# and hence does not consi der t he i ndex sel ect i ve.
#########

_l i ke_wi t h_bi nd_as_equal i t y = TRUE

#########
# _sor t _el i mi nat i on_cost _r at i o
#
# Set t i ng i t t o f i ve f or ces t he opt i mi zer t o onl y el i mi nat e t he
# sor t when i t i s 1/ 5t h t he cost of t he i ndex pr obe ( or conver sel y t he
# i ndex pr obe i s 5 t i mes as cost l y as t he sor t ) .
#########

_sor t _el i mi nat i on_cost _r at i o=5

#########
# _f ast _f ul l _scan_enabl ed
#
# Thi s par amet er i s used t o di sabl e f ast f ul l scans.
#########

_f ast _f ul l _scan_enabl ed = FALSE

#########
# quer y_r ewr i t e_enabl ed
#
# Requi r ed f or mat er i al i sed vi ews and f unct i on based i ndexes, whi ch ar e
# used i n some 11i pr oduct s. The r ecommended val ue i s t r ue.
#########

quer y_r ewr i t e_enabl ed = t r ue

#########
# _sql exec_pr ogr essi on_cost
#
# Thi s par amet er speci f i es t he cost t hr eshol d f or t he
# pr ogr ess met er . Non- zer o val ues can pr event cur sor s
# f r ombei ng shar ed when t i med_st at i st i cs=TRUE.
#
#########

_sql exec_pr ogr essi on_cost =2147483647

opt i mi zer _secur e_vi ew_mer gi ng=f al se

_opt i mi zer _aut ost at s_j ob=f al se # Tur ni ng of f aut o st at i st i cs

#############################################################################
#
# END OF CBO PARAMETERS SECTI ON
#
#############################################################################

# - - - - - - - - - - - - - - - - - END OF MANDATORY OPTI MI ZER PARAMETERS - - - - - - - - - - - - - - - - - - -

#

38
# Cust omer Set t i ngs.
#

I FI LE=/ ebs/ FRESH/ db/ t ech_st / 11. 1. 0/ dbs/ FRESH_dscgi gdb03_i f i l e. or a

Enable Maintenance Mode
1. Start the Oracle Application Administration utility, adadmin:
[ ebs@haovm021 ~] $ adadmin
Copyr i ght ( c) 2002 Or acl e Cor por at i on
Redwood Shor es, Cal i f or ni a, USA

Or acl e Appl i cat i ons AD Admi ni st r at i on

Ver si on 12. 0. 0

NOTE: You may not use t hi s ut i l i t y f or cust omdevel opment
unl ess you have wr i t t en per mi ssi on f r omOr acl e Cor por at i on.

Your def aul t di r ect or y i s ' / ebs/ app/ or acl e/ apps/ apps_st / appl ' .
I s t hi s t he cor r ect APPL_TOP [ Yes] ?
AD Admi ni st r at i on r ecor ds your AD Admi ni st r at i on sessi on i n a t ext f i l e
you speci f y. Ent er your AD Admi ni st r at i on l og f i l e name or pr ess [ Ret ur n]
t o accept t he def aul t f i l e name shown i n br acket s.

Fi l ename [ adadmi n. l og] :
************* St ar t of AD Admi ni st r at i on sessi on *************
AD Admi ni st r at i on ver si on: 12. 0. 0
AD Admi ni st r at i on st ar t ed at : Thu Apr 29 2010 12: 17: 09

APPL_TOP i s set t o / ebs/ app/ or acl e/ apps/ apps_st / appl

Backi ng up r est ar t f i l es, i f any. . . . . . Done.

Your pr evi ous AD Admi ni st r at i on sessi on di d not r un t o compl et i on.
Do you wi sh t o cont i nue wi t h your pr evi ous AD Admi ni st r at i on sessi on [ Yes] ?

You ar e about t o use or modi f y Or acl e Appl i cat i ons pr oduct t abl es
i n your ORACLE dat abase ' FRESH'
usi ng ORACLE execut abl es i n ' / ebs/ app/ or acl e/ apps/ t ech_st / 10. 1. 2' .

I s t hi s t he cor r ect dat abase [ Yes] ?
AD Admi ni st r at i on needs t he passwor d f or your ' SYSTEM' ORACLE schema
i n or der t o det er mi ne your i nst al l at i on conf i gur at i on.

Ent er t he passwor d f or your ' SYSTEM' ORACLE schema:

The ORACLE user name speci f i ed bel ow f or Appl i cat i on Obj ect Li br ar y
uni quel y i dent i f i es your exi st i ng pr oduct gr oup: APPLSYS

Ent er t he ORACLE passwor d of Appl i cat i on Obj ect Li br ar y [ APPS] :

AD Admi ni st r at i on i s ver i f yi ng your user name/ passwor d.
The st at us of var i ous f eat ur es i n t hi s r un of AD Admi ni st r at i on i s:

<- Feat ur e ver si on i n- >
Feat ur e Act i ve? APPLTOP Dat a model Fl ags
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CHECKFI LE Yes 1 1 Y N N Y N Y
PREREQ Yes 6 6 Y N N Y N Y
CONCURRENT_SESSI ONS No 2 2 Y Y N Y Y N
PATCH_TI MI NG Yes 2 2 Y N N Y N Y
PATCH_HI ST_I N_DB Yes 6 6 Y N N Y N Y

39
SCHEMA_SWAP Yes 1 1 Y N N Y Y Y
J AVA_WORKER Yes 1 1 Y N N Y N Y
CODELEVEL Yes 1 1 Y N N Y N Y

I dent i f i er f or t he cur r ent sessi on i s 540204

Readi ng pr oduct i nf or mat i on f r omf i l e. . .

Readi ng l anguage and t er r i t or y i nf or mat i on f r omf i l e. . .

Readi ng l anguage i nf or mat i on f r omappl US. t xt . . .

AD Admi ni st r at i on war ni ng:
Pr oduct Dat a Fi l e
/ ebs/ app/ or acl e/ apps/ apps_st / appl / admi n/ zf apr od. t xt
does not exi st f or pr oduct " zf a" .
Thi s pr oduct i s r egi st er ed i n t he dat abase but t he
above f i l e does not exi st i n APPL_TOP. The pr oduct
wi l l be i gnor ed wi t hout er r or .

/ ebs/ app/ or acl e/ apps/ apps_st / appl / admi n/ zsapr od. t xt
does not exi st f or pr oduct " zsa" .

/ ebs/ app/ or acl e/ apps/ apps_st / appl / admi n/ j t spr od. t xt
does not exi st f or pr oduct " j t s" .

Readi ng dat abase t o see what i ndust r y i s cur r ent l y i nst al l ed.

Readi ng FND_LANGUAGES t o see what i s cur r ent l y i nst al l ed.
Cur r ent l y, t he f ol l owi ng l anguage i s i nst al l ed:

Code Language St at us
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
US Amer i can Engl i sh Base

Your base l anguage wi l l be AMERI CAN.

Set t i ng up modul e i nf or mat i on.
Readi ng dat abase f or i nf or mat i on about t he modul es.
Savi ng modul e i nf or mat i on.
Readi ng dat abase f or i nf or mat i on about t he pr oduct s.
Readi ng dat abase f or i nf or mat i on about how pr oduct s depend on each ot her .
Readi ng t opf i l e. t xt . . .

Savi ng pr oduct i nf or mat i on.

AD code l evel : [ B. 1]

AD Admi ni st r at i on Mai n Menu
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

1. Gener at e Appl i cat i ons Fi l es menu

2. Mai nt ai n Appl i cat i ons Fi l es menu

3. Compi l e/ Rel oad Appl i cat i ons Dat abase Ent i t i es menu

40
4. Mai nt ai n Appl i cat i ons Dat abase Ent i t i es menu

5. Change Maintenance Mode

6. Exi t AD Admi ni st r at i on

Ent er your choi ce [ 6] : 5

2. Select option 5, Change Maintenance Mode

Change Mai nt enance Mode
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Mai nt enance Mode i s cur r ent l y: [ Di sabl ed] .

Mai nt enance mode shoul d nor mal l y be enabl ed when pat chi ng
Or acl e Appl i cat i ons and di sabl ed when user s ar e l ogged on
t o t he syst em. See t he Or acl e Appl i cat i ons Mai nt enance
Ut i l i t i es manual f or mor e i nf or mat i on about mai nt enance mode.

Pl ease sel ect an opt i on:

1. Enable Maintenance Mode

2. Di sabl e Mai nt enance Mode

3. Ret ur n t o Mai n Menu

Ent er your choi ce [ 3] : 1

3. Select option 1, Enable Maintenance Mode

sql pl us - s &un_apps/ *****
@/ ebs/ FRESH/ apps/ apps_st / appl / ad/ 12. 0. 0/ pat ch/ 115/ sql /
adset mmd. sql ENABLE

Successf ul l y enabl ed Mai nt enance Mode.

Revi ew t he messages above, t hen pr ess [ Ret ur n] t o cont i nue.

Backi ng up r est ar t f i l es, i f any. . . . . . Done.

Change Mai nt enance Mode
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Mai nt enance Mode i s cur r ent l y: [ Enabl ed] .

Mai nt enance mode shoul d nor mal l y be enabl ed when pat chi ng
Or acl e Appl i cat i ons and di sabl ed when user s ar e l ogged on
t o t he syst em. See t he Or acl e Appl i cat i ons Mai nt enance
Ut i l i t i es manual f or mor e i nf or mat i on about mai nt enance mode.
Database Pre-upgrade Tool Output
First Pass
SQL> @ut l u112i
Or acl e Dat abase 11. 2 Pr e- Upgr ade I nf or mat i on Tool 08- 05- 2010 05: 03: 26

41
.
**********************************************************************
Dat abase:
**********************************************************************
- - > name: FRESH
- - > ver si on: 11. 1. 0. 7. 0
- - > compat i bl e: 11. 1. 0
- - > bl ocksi ze: 8192
- - > pl at f or m: Li nux x86 64- bi t
- - > t i mezone f i l e: V10
.
**********************************************************************
Tabl espaces: [ make adj ust ment s i n t he cur r ent envi r onment ]
**********************************************************************
- - > SYSTEM t abl espace i s adequat e f or t he upgr ade.
. . . . mi ni mumr equi r ed si ze: 11011 MB
- - > CTXD t abl espace i s adequat e f or t he upgr ade.
- - > ODM t abl espace i s adequat e f or t he upgr ade.
- - > APPS_UNDOTS1 t abl espace i s adequat e f or t he upgr ade.
- - > APPS_TS_TX_DATA t abl espace i s adequat e f or t he upgr ade.
- - > APPS_TS_QUEUES t abl espace i s adequat e f or t he upgr ade.
WARNI NG: - - > SYSAUX t abl espace i s not l ar ge enough f or t he upgr ade.
. . . . cur r ent l y al l ocat ed si ze: 446 MB
. . . . i ncr ease cur r ent si ze by: 48 MB
. . . . t abl espace i s NOT AUTOEXTEND ENABLED.
.
**********************************************************************
Fl ashback: OFF
**********************************************************************
**********************************************************************
Updat e Par amet er s: [ Updat e Or acl e Dat abase 11. 2 i ni t . or a or spf i l e]
**********************************************************************
WARNI NG: - - > "j ava_pool _si ze" needs t o be i ncr eased t o at l east 128 MB
.
**********************************************************************
Renamed Par amet er s: [ Updat e Or acl e Dat abase 11. 2 i ni t . or a or spf i l e]
**********************************************************************
- - No r enamed par amet er s f ound. No changes ar e r equi r ed.
.
**********************************************************************
Obsol et e/ Depr ecat ed Par amet er s: [ Updat e Or acl e Dat abase 11. 2 i ni t . or a or
spf i l e]
**********************************************************************
- - > pl sql _nat i ve_l i br ar y_di r 11. 2 OBSOLETE
- - > pl sql _nat i ve_l i br ar y_subdi r _ 11. 2 OBSOLETE
.
**********************************************************************
Component s: [ The f ol l owi ng dat abase component s wi l l be upgr aded or i nst al l ed]
**********************************************************************
- - > Or acl e Cat al og Vi ews [ upgr ade] VALI D
- - > Or acl e Packages and Types [ upgr ade] VALI D
- - > J Ser ver J AVA Vi r t ual Machi ne [ upgr ade] VALI D
- - > Or acl e XDK f or J ava [ upgr ade] VALI D
- - > Real Appl i cat i on Cl ust er s [ upgr ade] I NVALI D
- - > OLAP Anal yt i c Wor kspace [ upgr ade] VALI D
- - > OLAP Cat al og [ upgr ade] VALI D
- - > Or acl e Text [ upgr ade] VALI D

42
- - > Or acl e XML Dat abase [ upgr ade] VALI D
- - > Or acl e J ava Packages [ upgr ade] VALI D
- - > Or acl e i nt er Medi a [ upgr ade] VALI D
- - > Spat i al [ upgr ade] VALI D
- - > Dat a Mi ni ng [ upgr ade] VALI D
- - > Or acl e OLAP API [ upgr ade] VALI D
.
**********************************************************************
Mi scel l aneous War ni ngs
**********************************************************************
WARNI NG: - - > Dat abase i s usi ng a t i mezone f i l e ol der t han ver si on 11.
. . . . Af t er t he r el ease mi gr at i on, i t i s r ecommended t hat DBMS_DST package
. . . . be used t o upgr ade t he 11. 1. 0. 7. 0 dat abase t i mezone ver si on
. . . . t o t he l at est ver si on whi ch comes wi t h t he new r el ease.
WARNI NG: - - > Dat abase cont ai ns schemas wi t h st al e opt i mi zer st at i st i cs.
. . . . Ref er t o t he Upgr ade Gui de f or i nst r uct i ons t o updat e
. . . . schema st at i st i cs pr i or t o upgr adi ng t he dat abase.
. . . . Component Schemas wi t h st al e st at i st i cs:
. . . . SYS
. . . . OLAPSYS
. . . . CTXSYS
. . . . XDB
. . . . ORDSYS
. . . . MDSYS
WARNI NG: - - > r ecycl e bi n i n use.
. . . . Your r ecycl e bi n i s t ur ned on and i t cont ai ns
. . . . 2 obj ect ( s) . I t i s REQUI RED
. . . . t hat t he r ecycl e bi n i s empt y pr i or t o upgr adi ng
. . . . your dat abase.
. . . . The command: PURGE DBA_RECYCLEBI N
. . . . must be execut ed i mmedi at el y pr i or t o execut i ng your upgr ade.
.

Second Pass
This is the output after fixing the items highlighted above under First Pass.
SQL> @ut l u112i
Or acl e Dat abase 11. 2 Pr e- Upgr ade I nf or mat i on Tool 08- 09- 2010 06: 41: 20
.
**********************************************************************
Dat abase:
**********************************************************************
- - > name: FRESH
- - > ver si on: 11. 1. 0. 7. 0
- - > compat i bl e: 11. 1. 0
- - > bl ocksi ze: 8192
- - > pl at f or m: Li nux x86 64- bi t
- - > t i mezone f i l e: V10
.
**********************************************************************
Tabl espaces: [ make adj ust ment s i n t he cur r ent envi r onment ]
**********************************************************************
- - > SYSTEM t abl espace i s adequat e f or t he upgr ade.
- - > CTXD t abl espace i s adequat e f or t he upgr ade.
- - > ODM t abl espace i s adequat e f or t he upgr ade.
- - > APPS_UNDOTS1 t abl espace i s adequat e f or t he upgr ade.

43
- - > APPS_TS_TX_DATA t abl espace i s adequat e f or t he upgr ade.
- - > APPS_TS_QUEUES t abl espace i s adequat e f or t he upgr ade.
- - > SYSAUX t abl espace i s adequat e f or t he upgr ade.
.
**********************************************************************
Fl ashback: OFF
**********************************************************************
**********************************************************************
Updat e Par amet er s: [ Updat e Or acl e Dat abase 11. 2 i ni t . or a or spf i l e]
**********************************************************************
- - No updat e par amet er changes ar e r equi r ed.
.
**********************************************************************
Renamed Par amet er s: [ Updat e Or acl e Dat abase 11. 2 i ni t . or a or spf i l e]
**********************************************************************
- - No r enamed par amet er s f ound. No changes ar e r equi r ed.
.
**********************************************************************
Obsol et e/ Depr ecat ed Par amet er s: [ Updat e Or acl e Dat abase 11. 2 i ni t . or a or
spf i l e]
**********************************************************************
- - No obsol et e par amet er s f ound. No changes ar e r equi r ed
.
**********************************************************************
Component s: [ The f ol l owi ng dat abase component s wi l l be upgr aded or i nst al l ed]
**********************************************************************
- - > Or acl e Cat al og Vi ews [ upgr ade] VALI D
- - > Or acl e Packages and Types [ upgr ade] VALI D
- - > J Ser ver J AVA Vi r t ual Machi ne [ upgr ade] VALI D
- - > Or acl e XDK f or J ava [ upgr ade] VALI D
- - > Real Appl i cat i on Cl ust er s [ upgr ade] I NVALI D
- - > OLAP Anal yt i c Wor kspace [ upgr ade] VALI D
- - > OLAP Cat al og [ upgr ade] VALI D
- - > Or acl e Text [ upgr ade] VALI D
- - > Or acl e XML Dat abase [ upgr ade] VALI D
- - > Or acl e J ava Packages [ upgr ade] VALI D
- - > Or acl e i nt er Medi a [ upgr ade] VALI D
- - > Spat i al [ upgr ade] VALI D
- - > Dat a Mi ni ng [ upgr ade] VALI D
- - > Or acl e OLAP API [ upgr ade] VALI D
.
**********************************************************************
Mi scel l aneous War ni ngs
**********************************************************************
WARNI NG: - - > Dat abase i s usi ng a t i mezone f i l e ol der t han ver si on 11.
. . . . Af t er t he r el ease mi gr at i on, i t i s r ecommended t hat DBMS_DST package
. . . . be used t o upgr ade t he 11. 1. 0. 7. 0 dat abase t i mezone ver si on
. . . . t o t he l at est ver si on whi ch comes wi t h t he new r el ease.
WARNI NG: - - > Dat abase cont ai ns schemas wi t h st al e opt i mi zer st at i st i cs.
. . . . Ref er t o t he Upgr ade Gui de f or i nst r uct i ons t o updat e
. . . . schema st at i st i cs pr i or t o upgr adi ng t he dat abase.
. . . . Component Schemas wi t h st al e st at i st i cs:
. . . . SYS
WARNI NG: - - > r ecycl e bi n i n use.
. . . . Your r ecycl e bi n t ur ned on.
. . . . I t i s REQUI RED
. . . . t hat t he r ecycl e bi n i s empt y pr i or t o upgr adi ng
. . . . your dat abase.
. . . . The command: PURGE DBA_RECYCLEBI N
. . . . must be execut ed i mmedi at el y pr i or t o execut i ng your upgr ade.

44
.


45
rconfig XML File
The changes from the original file are highlighted in red typeface in the following output.

Conver t ToRAC_Admi nManaged_FRESH. xml
<?xml ver si on="1. 0" encodi ng="UTF- 8"?>
<n: RConf i g xml ns: n="ht t p: / / www. or acl e. com/ r conf i g"
xml ns: xsi ="ht t p: / / www. w3. or g/ 2001/ XMLSchema- i nst ance"
xsi : schemaLocat i on="ht t p: / / www. or acl e. com/ r conf i g">
<n: Conver t ToRAC>
<! - - Ver i f y does a pr echeck t o ensur e al l pr e- r equi si t es ar e met , bef or e t he
conver si on i s at t empt ed. Al l owabl e val ues ar e: YES| NO| ONLY - - >
<n: Conver t ver i f y="YES">
<! - - Speci f y cur r ent Or acl eHome of non- r ac dat abase f or Sour ceDBHome - - >

<n: Sour ceDBHome>/u01/app/oracle/product/11.2.0/dbhome_1</ n: Sour ceDBHome>
<! - - Speci f y Or acl eHome wher e t he r ac dat abase shoul d be conf i gur ed. I t can be same
as Sour ceDBHome - - >

<n: Tar get DBHome>/u01/app/oracle/product/11.2.0/dbhome_1</ n: Tar get DBHome>
<! - - Speci f y SI D of non- r ac dat abase and cr edent i al . User wi t h sysdba r ol e i s
r equi r ed t o per f or mconver si on - - >
<n: Sour ceDBI nf o SI D="FRESH">
<n: Cr edent i al s>
<n: User >sys</ n: User >
<n: Passwor d>welcome1</ n: Passwor d>
<n: Rol e>sysdba</ n: Rol e>
</ n: Cr edent i al s>
</ n: Sour ceDBI nf o>
<! - - Speci f y t he l i st of nodes t hat shoul d have r ac i nst ances r unni ng f or t he Admi n
Managed Cl ust er Dat abase. Local Node shoul d be t he f i r st node i n t hi s nodel i st . - - >
<n: NodeLi st >
<n: Node name="dscgigdb03"/ >
<n: Node name="dscgigdb04"/ >
</ n: NodeLi st >
<! - - I nst ance Pr ef i x t ag i s opt i onal st ar t i ng wi t h 11. 2. I f l ef t empt y, i t i s
der i ved f r omdb_uni que_name. - - >
<n: I nst ancePr ef i x>FRESH</ n: I nst ancePr ef i x>
<! - - Li st ener det ai l s ar e no l onger needed st ar t i ng 11. 2. Dat abase i s r egi st er ed
wi t h def aul t l i st ener and SCAN l i st ener r unni ng f r omOr acl e Gr i d I nf r ast r uct ur e
home. - - >
<! - - Speci f y t he t ype of st or age t o be used by r ac dat abase. Al l owabl e val ues ar e
CFS| ASM. The non- r ac dat abase shoul d have same st or age t ype. ASM cr edent i al s ar e
no needed f or conver si on. - - >
<n: Shar edSt or age t ype="ASM">
<! - - Speci f y Dat abase Ar ea Locat i on t o be conf i gur ed f or r ac dat abase. I f t hi s
f i el d i s l ef t empt y, cur r ent st or age wi l l be used f or r ac dat abase. For CFS, t hi s
f i el d wi l l have di r ect or y pat h. - - >
<n: Tar get Dat abaseAr ea>+DATA</ n: Tar get Dat abaseAr ea>
<! - - Speci f y Fl ash Recover y Ar ea t o be conf i gur ed f or r ac dat abase. I f t hi s f i el d
i s l ef t empt y, cur r ent r ecover y ar ea of non- r ac dat abase wi l l be conf i gur ed f or
r ac dat abase. I f cur r ent dat abase i s not usi ng r ecover y Ar ea, t he r esul t i ng r ac
dat abase wi l l not have a r ecover y ar ea. - - >
<n: Tar get Fl ashRecover yAr ea>+RECO</ n: Tar get Fl ashRecover yAr ea>
</ n: Shar edSt or age>
</ n: Conver t >
</ n: Conver t ToRAC>
</ n: RConf i g>

46
Post rconfig Database Parameter File
This file was derived from a copy of the initial single-instance Rapid Install Standard Installation
database parameter file except the COMPATIBLE parameter was changed to 11.2.0.2. The file
was then modified automatically by rconfig to accommodate the new Oracle ASM and Oracle
RAC setup. The changes from the original file are highlighted in red typeface and also have a
comment for the Old setting and the New target. Consult, Database Initialization Parameters
for Oracle Applications Release 12, MOS ID 396009.1 to review any other changes or sizing
guidelines.
Note that the Automatic Memory Management feature, enabled by the MEMORY_TARGET /
MEMORY_MAX_TARGET database parameters, is incompatible with the use of HugePages.
DO NOT SET THESE PARAMETERS. The Automatic Shared Memory Management
feature, enabled by setting SGA_TARGET, is compatible with HugePages and there are sizing
recommendations for SGA_TARGET in MOS ID 396009.1.

*. aq_t m_pr ocesses=1
*. compat i bl e=' 11. 2. 0. 2'
# Ol d set t i ng
#*. cont r ol _f i l es=' / ebs/ FRESH/ db/ apps_st / dat a/ cnt r l 01. dbf , / ebs/ FRESH/ db/ apps_st
/ dat a/ cnt r l 02. dbf , / ebs/ FRESH/ db/ apps_st / dat a/ cnt r l 03. dbf '
# New t ar get
*. cont r ol _f i l es=' +DATA/ FRESH/ CONTROLFI LE/ cnt r l 01. dbf ' , ' +DATA/ FRESH/ CONTROLFI LE
/ cnt r l 02. dbf ' , ' +RECO/ FRESH/ CONTROLFI LE/ cnt r l 03. dbf '
*. cur sor _shar i ng=' EXACT'
*. db_bl ock_checki ng=' FALSE'
*. db_bl ock_checksum=' TRUE'
*. db_bl ock_si ze=8192
*. db_f i l es=512
*. db_name=' FRESH'
*. di agnost i c_dest =' / u01/ app/ or acl e'
*. dml _l ocks=10000
*. event =' '
*. j ava_pool _si ze=209715200
*. j ob_queue_pr ocesses=2
*. l og_buf f er =10485760
*. l og_checkpoi nt _i nt er val =100000
*. l og_checkpoi nt _t i meout =1200
*. l og_checkpoi nt s_t o_al er t =TRUE
*. max_dump_f i l e_si ze=' 20480'
*. nl s_comp=' bi nar y'
*. nl s_dat e_f or mat =' DD- MON- RR'
*. nl s_l anguage=' amer i can'
*. nl s_l engt h_semant i cs=' BYTE'
*. nl s_numer i c_char act er s=' . , '
*. nl s_sor t =' bi nar y'
*. nl s_t er r i t or y=' amer i ca'
*. ol ap_page_pool _si ze=4194304
*. open_cur sor s=600
*. opt i mi zer _secur e_vi ew_mer gi ng=FALSE
*. par al l el _max_ser ver s=8
*. par al l el _mi n_ser ver s=0
*. pga_aggr egat e_t ar get =1073741824
*. pl sql _code_t ype=' I NTERPRETED'
*. pl sql _opt i mi ze_l evel =2

47
*. pr ocesses=200
*. quer y_r ewr i t e_enabl ed=' t r ue'
*. r ecycl ebi n=' OFF'
*. sec_case_sensi t i ve_l ogon=FALSE
*. sessi on_cached_cur sor s=500
*. sessi ons=400
*. sga_t ar get =1073741824
*. shar ed_pool _r eser ved_si ze=41943040
*. shar ed_pool _si ze=419430400
*. t i med_st at i st i cs=TRUE
*. undo_management =' AUTO'
# Ol d set t i ng
# ut l _f i l e_di r = ' / usr / t mp, / usr / t mp ,
' / ebs/ FRESH/ db/ t ech_st / 11. 1. 0/ appsut i l / out bound/ FRESH_dscgi gdb03 , ' / usr / t mp
# New t ar get
FRESH1. ut l _f i l e_di r =' / usr / t mp' , ' / usr / t mp' , ' / u01/ app/ or acl e/ pr oduct / 11. 2. 0/ ebsm
i g/ appsut i l / out bound/ FRESH_dscgi gdb03' , ' / usr / t mp'
FRESH2. ut l _f i l e_di r =' / usr / t mp' , ' / usr / t mp' , ' / u01/ app/ or acl e/ pr oduct / 11. 2. 0/ ebsm
i g/ appsut i l / out bound/ FRESH_dscgi gdb04' , ' / usr / t mp'
*. wor kar ea_si ze_pol i cy=' AUTO'
#
# Added f or Or acl e ASM and Or acl e Managed Fi l es
*. db_r ecover y_f i l e_dest =' +RECO'
*. db_r ecover y_f i l e_dest _si ze=500G
*. db_cr eat e_f i l e_dest =' +DATA'
# RAC Addi t i ons
#*. cl ust er _dat abase=t r ue
FRESH1. i nst ance_number =1
FRESH2. i nst ance_number =2
*. r emot e_l i st ener =dscgi g- scan: 1521
FRESH1. t hr ead=1
FRESH2. t hr ead=2
# Ol d set t i ng
#undo_t abl espace=APPS_UNDOTS1
FRESH1. undo_t abl espace= APPS_UNDOTS1'
FRESH2. undo_t abl espace=' UNDO_TBS2'
# Added f or i ssues wi t h NFS f or i mpor t , MOS I D 739570. 1
*. event ="10298 t r ace name cont ext f or ever , l evel 32"
Database Node Post Autoconfig Environment File
dscgigdb03

expor t PATH$ORACLE_HOME/ bi n: $ORACLE_HOME/ per l / bi n: $PATH
# Set up EBS DB env
sour ce $ORACLE_HOME/ FRESH1_dscgi gdb03. env
dscgigdb04

expor t PATH$ORACLE_HOME/ bi n: $ORACLE_HOME/ per l / bi n: $PATH
# Set up EBS DB env
sour ce $ORACLE_HOME/ FRESH2_dscgi gdb04. env

48
Applications Tier tnsnames.ora File
FRESH=
( DESCRI PTI ON=
( ADDRESS=( PROTOCOL=t cp) ( HOST=dscgi g- scan. us. or acl e. com) ( PORT=1521) )
( CONNECT_DATA=
)
)

FRESH1=
( DESCRI PTI ON=
( CONNECT_DATA=
)
)

FRESH1_FO=
( DESCRI PTI ON=
( CONNECT_DATA=
)
)

FRESH2=
( DESCRI PTI ON=
( CONNECT_DATA=
)
)

FRESH2_FO=
( DESCRI PTI ON=
( CONNECT_DATA=
)
)

FRESH_FO=
( DESCRI PTI ON=
( CONNECT_DATA=
)
)

FRESH_BALANCE=
( DESCRI PTI ON=
( ADDRESS_LI ST=
( LOAD_BALANCE=YES)
( FAI LOVER=YES)
( FAI LOVER=YES)

49
)
( CONNECT_DATA=
)
)

50
References
1. Oracle Maximum Availability Architecture Web site
http://www.otn.oracle.com/goto/maa
2. Oracle Applications Installation and Upgrade Notes Release 12 (12.1.1) for Linux x86-64
[MOS ID 761566.1]
3. Interoperability Notes EBS R12 with Database 11gR2
[MOS ID 1058763.1]
4. Oracle Database High Availability Overview
http://otn.oracle.com/pls/db111/db111.to_toc?partno=b28281
5. Oracle Database High Availability Best Practices
http://otn.oracle.com/pls/db111/db111.to_toc?partno=b28282
6. Oracle E-Business Suite Installation Guide: Using Rapid Install,, Release 12.1 (12.1.1)
http://download.oracle.com/docs/cd/B53825_04/current/acrobat/121oaig.pdf
7. Using Oracle 11g Release 2 Real Application Clusters with Oracle E-Business Suite Release 12
Support Article [MOS ID 823587.1]
8. Database Initialization Parameters for Oracle Applications Release 12[ MOS ID 396009.1]
9. Oracle Upgrade Guide
http://download.oracle.com/docs/cd/E11882_01/server.112/e17222/toc.htm
10. Single Client Access Name (SCAN)
http://www.oracle.com/technetwork/database/clustering/overview/scan-129069.pdf

51
Change Record

Date Summary of Changes
1/2011 Published
2/9/2011
Added the rationale for installing the Database Examples CD
Added a pointer to the MAA paper, Oracle E-Business Suite on Exadata
Revised the Executive Overview
3/24/11
Updated the Hugepages MOS note to 361468.1

Installing Oracle E-Business Suite Release 12
with the Oracle Exadata Database Machine
March 2011
Author: Ray Dutcher
Contributing Authors: Richard J obin, MAA team
Editor: Viv Schupmann

Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores, CA 94065
U.S.A.

Worldwide Inquiries:
Phone: +1.650.506.7000
Fax: +1.650.506.7200
oracle.com

Copyright 2010, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only and
the contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other
warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or
fitness for a particular purpose. We specifically disclaimany liability with respect to this document and no contractual obligations are
formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any formor by any
means, electronic or mechanical, for any purpose, without our prior written permission.
Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective
owners.
0109

EBS On Exadata

Cargado por

Información del documento

Título original

Derechos de autor

Formatos disponibles

Compartir este documento

Compartir o incrustar documentos

Opciones para compartir

¿Le pareció útil este documento?

¿Este contenido es inapropiado?

Copyright:

Formatos disponibles

EBS On Exadata

Cargado por

Copyright:

Formatos disponibles

Installing Oracle E-Business Suite

Release 12 with the Oracle

También podría gustarte