Document 1566935.

Page 1 of 14

Implementing Oracle E-Business Suite 12.1 Databases on Oracle Database Appliance

(Doc ID 1566935.1)
Modified: Aug 13, 2013

Type: REFERENCE

In this Document
Purpose
Details
Executive Overview
Oracle E-Business Suite
Why Oracle E-Business Suite on Oracle Database Appliance?
Preparing to deploy Oracle E-Business Suite databases on Oracle Database Appliance
Oracle Database Appliance Configuration Customization
1. Extend logical volumes and create staging directory
2. Install required additional Linux RPMs
3. Install Database examples to target home
4. Create NLS directory to target home
Installing Oracle E-Business Suite using Rapid Install
Invoke Rapid Install Wizard on Database Node
Invoke Rapid Install Wizard on Application Node
Post Basic Installation Procedure
Patch applications tier for 11.2 interoperability
Patch database tier for 11.2 interoperability
Set Oracle binary permissions in target ORACLE_HOME
Run Pre-upgrade checklist and address findings
Prepare database for upgrade
Upgrade database to version 11.2 using DBUA
Post-install steps for patches
Change database initialization parameters
Move database files, control file, and spfile to Automatic Storage Management (ASM)
Finalize Oracle E-Business Suite Setup
Install AutoConfig on DB Tier
Cleanup current schema configuration
Create static listener configuration
Reload listener configuration
Generate and update Context file
Run AutoConfig on DB Tier
Update Grid Infrastructure (GI) Network files
Update OCR
Run adgrants.sql and grant create procedure privilege on CTXSYS
Update TNS alias on App tier
Validate Workflow Rules Set

https://support.oracle.com/epmos/faces/DocContentDisplay?_adf.ctrl-state=mt8r1v5vt_210...

5/7/2015

Document 1566935.1

Page 2 of 14

Update jdbc_url setting in context file

Run AutoConfig on app tier
Gather SYS schema stats
Re-Create Grants and Synonyms
Recompile the APPS Schema
Start applications tier Processes
Synchronize Workflow Views
Migrating Database using Rapid Clone
Conclusion
Appendix A - Database migration options
Oracle Data Guard
Transportable Tablespaces
Transportable Database
Data Pump
Appendix B: References

APPLIES TO:
Oracle Appliance Kit - Version 2.5.0.0 and later
Information in this document applies to any platform.

PURPOSE
The purpose of this note is to illustrate the high level deployment of an Oracle E-Business Suite 12.1 database
on Oracle Database Appliance.

DETAILS
Executive Overview
Oracle Database Appliance is a simple, reliable, and affordable Engineered System from Oracle. It consists of
hardware and software integrated to work together that saves customers time and money by simplifying
deployment, maintenance, and support of high availability database solutions. The bare metal (non-virtualized)
deployment of Oracle Database Appliance is an ideal option to host the database tier for small and medium size
implementations of Oracle E-Business Suite. This white paper discusses the benefits of utilizing Oracle
Database Appliance as the database tier for Oracle E-Business Suite and the associated deployment as well as
data migration steps. This white paper does not contain implementation steps for the complete Oracle EBusiness Suite stack on Oracle Database Appliance Virtualized Platform.

Oracle E-Business Suite

Oracle E-Business Suite is the most comprehensive suite of integrated, global business applications that enables
organizations to make better decisions, reduce costs, and increase performance. With hundreds of crossindustry capabilities spanning enterprise resource planning, customer relationship management, and supply
chain planning, Oracle E-Business Suite applications help customers manage the complexities of global business
environments in organizations of all sizes

https://support.oracle.com/epmos/faces/DocContentDisplay?_adf.ctrl-state=mt8r1v5vt_210...

5/7/2015

Document 1566935.1

Page 3 of 14

Why Oracle E-Business Suite on Oracle Database Appliance?

E-Business Suite is typically mission critical and requires reliable, performant, and secure application and
database environments. Oracle Database Appliance simplifies deployment, maintenance, and support of high
availability database solutions while embedding Oracles best practices into the configuration. As a result, the
appliance not only is a simple and cost effective solution for small and midsize Oracle E-Business Suite
databases, but also provides the reliability necessary to meet service level expectations.
Oracle Database Appliance also addresses one of the biggest management challenges for global business
application platforms such as Oracle E-Business Suite. Managing a consistent infrastructure for a multitude of
development, test, and production systems can be challenging for administrators. Traditionally, these ancillary
systems have tended to diverge from a standardized configuration. With Oracle Database Appliance it is easy to
synchronize the configuration since the deployment and patching process is standardized across database
environments.

Preparing to deploy Oracle E-Business Suite databases on Oracle Database Appliance

The Appliance Manager software that comes pre-installed with Oracle Database Appliance automates the
installation and configuration of the network, clusterware, ASM, and database software. This section discusses
the tasks that must be completed on Oracle Database Appliance before Oracle E-Business Suite databases can
be deployed on it.
You must complete standard Oracle Database Appliance deployment before beginning the installation and
configuration of E-Business Suite. For details on how to deploy Oracle Database Appliance please refer to Oracle
Database Appliance setup illustration at http://docs.oracle.com/cd/E22693_01/doc.21/e35554.pdf
All Oracle E-Business Suite database options are available in an Oracle Database Appliance environment,
including for example:

Partitioning
Real Applications Clusters
Advanced Security
Advanced Compression
Active Data Guard
Real Application Testing
Advanced Analytics
Golden Gate
Manageability

Oracle Database Appliance Configuration Customization

To prepare Oracle Database Appliance for Oracle E-Business Suite deployment, the following changes to the
Oracle Database Appliance configuration are required.

1. Extend logical volumes and create staging directory

In order to stage and install Oracle E-Business Suite software on Oracle Database Appliance, the local storage
volumes need to be expanded by 25 GB. The local storage volumes can be expanded by following the

https://support.oracle.com/epmos/faces/DocContentDisplay?_adf.ctrl-state=mt8r1v5vt_210...

5/7/2015

Document 1566935.1

Page 4 of 14

instructions given in My Oracle Support Knowledge Document: How to customize available disk space for
installing your application on the Oracle Database Appliance (ODA) (Doc ID 1457717.1).
For example
lvextend -L +25G /dev/mapper/VolGroupSys-LogVolOpt
resize2fs /dev/mapper/VolGroupSys-LogVolOpt
lvextend -L +25G /dev/mapper/VolGroupSys-LogVolU01
resize2fs /dev/mapper/VolGroupSys-LogVolU01

The Oracle E-Business Suite installation media needs to be locally available before installation can begin. The
installation media can be copied to a locally created staging area or mounted via NFS.
For example
mkdir -p /opt/oracle/stage
chown -R oracle:oinstall /opt/oracle/stage

2. Install required additional Linux RPMs

Oracle E-Business Suite requires additional RPMs to be installed on the application and database tiers.
Depending on the Appliance Manager software version, additional packages may be required to be installed on
Oracle Database Appliance before installation can begin. The information about required RPMs for Oracle Linux
5 is available in My Oracle Support Knowledge Document: Oracle E-Business Suite Installation and Upgrade
Notes Release 12 (12.1.1) for Linux x86-64 (Doc ID 761566.1)
For example, the following RPMs are installed on each Oracle Database Appliance server node. These RPMs can
be found in the distribution. Follow My Oracle Support note 1461798.1 on how to download RPMs directly onto
Oracle Database Appliance.

libstdc++-devel-4.1.2-14.el5.i386
gdbm-1.8.0-26.2.1.i386
libXp-1.0.0-8.1.el5.x86_64
libXi-1.0.1-4.el5_4.i386
db4-4.3.29-10.el5_5.2.i386

3. Install Database examples to target home

The ORACLE_HOME installed during the deployment process or using oakcli does not have the Database
Examples installed. The Oracle Database 11gR2 Examples CD needs to be downloaded and installed into the
target ORACLE_HOME.

4. Create NLS directory to target home

Run the following in the target ORACLE_HOME

https://support.oracle.com/epmos/faces/DocContentDisplay?_adf.ctrl-state=mt8r1v5vt_210...

5/7/2015

Document 1566935.1

Page 5 of 14

$ perl $ORACLE_HOME/nls/data/old/cr9idata.pl

Installing Oracle E-Business Suite using Rapid Install

Refer to Oracle E-Business Suite documentation for the details of the deployment processes. This section gives
a flavor of the Oracle Database Appliance specific tasks.
Note: During the writing of this white paper, installation of Oracle E-Business Suite 12.1 with Oracle
Database version 11.2.0.3 PSU 5 was validated.
The Rapid Install wizard is used to install the database tier for Oracle E-Business Suite on Oracle Database
Appliance. The wizard collects all the deployment configuration information and stores it as the conf_<SID>.txt
file. In the name of the file, SID refers to the installation identifier, such as PROD, PPRD, QA2, etc. This file
includes information about the database and application tier nodes and is critical to the installation and
management of the Oracle E-Business Suite environment. Rapid Install stores the conf_<SID>.txt file in the
$ORACLE_HOME/appsutil directory on the database server node and in the $INST_TOP directory on the
application tier node. Rapid Install provides two install options: Standard Install and Express Install. This paper
uses the Standard Install. In a multi-tier architecture, Rapid Install is run on all servers starting with the
database server node(s).
Oracle Database Appliance supports all versions of Oracle Database starting with 11.2.0.2. Older versions of
Oracle Database are not supported on Oracle Database Appliance. However, since Oracle E-Business Suite
requires an 11.1.0.7 database code tree on the database tier, the process of installing Oracle Applications on
Oracle Database Appliance requires a slightly different approach that includes an upgrade of the database code
tree and migration of the database from one version to another within Oracle Database Appliance.
On Oracle Database Appliance, the Oracle E-Business Suite database tier (including the software and seed
database) is initially installed on a local file system. Then the database is upgraded and data is migrated to the
ASM storage configuration. Post installation steps are therefore needed to complete database deployment.
Please note that during the input phase of the installation process, a different port pool should be selected
because the default 1521 ports would have been assigned to the existing (initial) installation

Invoke Rapid Install Wizard on Database Node

Invoking the Rapid Install Wizard is a standard process for all Oracle E-Business Suite deployments. For
example,
$ cd /u01/StageR12/startCD/Disk1/rapidwiz
$. /rapidwiz

Note: The recommended rapidwiz version to use for your deployment is 12.1.1.13 or higher.

Note that the initial deployment is performed on a single Oracle Database Appliance node. The configuration

https://support.oracle.com/epmos/faces/DocContentDisplay?_adf.ctrl-state=mt8r1v5vt_210...

5/7/2015

Document 1566935.1

Page 6 of 14

may be extended to a RAC configuration at a later stage, if desired. The process of extending a single instance
database configuration to a clustered database configuration is presented later in this white paper.

Invoke Rapid Install Wizard on Application Node

Once the database installation has completed, run rapid install on the application node. If multiple application
nodes are planned, then Rapid Install is run on the primary application node first. This paper describes a single
application node configuration.
Before invoking rapidwiz, the configuration file prepared during the database tier installation is copied to the
primary application tier node, for example, by running the following command from the application tier node.
$ scp db_node1:/directory/conf_<SID>.conf /tmp

Once the installation on the Application tier has completed, the post installation steps need to be carried out,
which are described in the next section.

Post Basic Installation Procedure

As mentioned, Oracle E-Business Suite installs Oracle database version 11.1.0.7, which needs to be upgraded.
However, before the database upgrade, both the database tier and the application tier must be prepared for
interoperability.

Patch applications tier for 11.2 interoperability

The Oracle Applications environment needs to be patched for it to be compatible with RDBMS 11.2. The
required patches are listed in My Oracle Support Knowledge Document: Interoperability Notes EBS R12 with
Database 11gR2 [ID 1058763.1].

Patch database tier for 11.2 interoperability

Note that the post install actions for any of the database patches that are listed in the interoperability note need
not be run at this stage but need to be completed after the database has been upgraded.

Set Oracle binary permissions in target ORACLE_HOME

Use the following command to change the group ownership of the Oracle binary.

$ su - grid
$ $GRID_HOME/bin/setasmgidwrap o=$RDBMS_HOME/bin/oracle

Run Pre-upgrade checklist and address findings

The pre-upgrade scripts validate current database environment and identify required pre-upgrade changes proactively. Review the output after the following script is run.

https://support.oracle.com/epmos/faces/DocContentDisplay?_adf.ctrl-state=mt8r1v5vt_210...

5/7/2015

Document 1566935.1

Page 7 of 14

SQL> ORACLE_HOME/rdbms/admin/utlu112i.sql

Prepare database for upgrade

Before the database is upgraded, purge the database recycle bin to free up space. Also increase sysaux
tablespace size and gather data dictionary optimizer statistics.
SQL> purge recyclebin;
SQL> alter tablespace sysaux add datafile sysaux02.dbf size 500MB;
SQL> alter system gather dictionary stats;

Also an entry should be added to the /etc/oratab for the database. For example,
PROD:/u01/app/oracle/PROD/db/tech_st/11.2.0:N

It is advisable to run the pre-upgrade checklist again to verify that all requirements have been properly
addressed before proceeding.

Upgrade database to version 11.2 using DBUA

The database upgrade is carried out using Oracle Database Upgrade Assistant and not the Oracle Appliance
Manager as the latter does not support database versions prior to Oracle database release 11.2. For example,
$ /u01/app/oracle/product/11.2.0.3/dbhome_1/bin/dbua

Post-install steps for patches

Once the database has been upgraded, complete the post install operations specified for RDBMS patches
applied during the earlier step.

Change database initialization parameters

The database compatible parameter is now changed to 11.2.0.3 and the diagnostic_dest parameter is reset
from the default value as follows.

Note: The diagnostic_dest parameter is derived from $ORACLE_BASE (if used) or $ORACLE_HOME
environment variable setting.
SQL> alter system set compatible='11.2.0.3' scope=spfile;
SQL> alter system reset diagnostic_dest;

The database is restarted to mount state using srvctl for changes to take effect.

https://support.oracle.com/epmos/faces/DocContentDisplay?_adf.ctrl-state=mt8r1v5vt_210...

5/7/2015

Document 1566935.1

Page 8 of 14

Move database files, control file, and spfile to Automatic Storage Management (ASM)
- Data files
$ rman target /
RMAN> backup as copy database format '+DATA';
RMAN> switch database to copy;

- Control file
RMAN> restore controlfile to '+DATA/PROD/control01.dbf' from
'/u01/app/oracle/PROD/db/apps_st/data/cntrl01.dbf';
SQL> alter system set control_files='+DATA/PROD/control01.dbf' scope=spfile;

- spfile
RMAN> backup spfile;
RMAN> restore spfile to '+DATA/PROD/spfileprod.ora';
$ srvctl modify database -d PROD -p '+DATA/PROD/spfileprod.ora';

- Remove old spfile and restart database

$ srvctl stop database -d PROD
$ rm $ORACLE_HOME/dbs/spfilePORD.ora
$ srvctl start database -d PROD

Finalize Oracle E-Business Suite Setup

In this section, the Oracle E-Business Suite setup is finalized and the database is converted into a clustered
(Oracle Real Application Clusters) configuration.

Install AutoConfig on DB Tier

In this section, AutoConfig is installed. Create appsutil.zip file on the application tier as follows.

$$ADPERLPRG $AD_TOP/bin/admkappsutil.pl

The appsutil.zip file is created in the $APPL_TOP/admin/out directory.

On the database tier, copy the file to RDBMS $ORACLE_HOME

$ cd $ORACLE_HOME
$ cp /cloudfs/app/oracle/PROD/inst/apps/PROD_slcac459/admin/out/appsutil.zip .

https://support.oracle.com/epmos/faces/DocContentDisplay?_adf.ctrl-state=mt8r1v5vt_210...

5/7/2015

Document 1566935.1

Page 9 of 14

$ unzip -o appsutil.zip
$ cp -r /u01/app/oracle/PROD/db/tech_st/11.1.0/appsutil/jre .

Cleanup current schema configuration

The Concurrent Manager tables and FND_NODES table etc. are cleaned during this stage.

$ sqlplus apps/apps
SQL> exec fnd_conc_clone.setup_clean;

Create static listener configuration

Oracle Database 11.2 database listener executes from the Grid Infrastructure home. A static listener
configuration needs to be created from the GI home. For example,

SID_LIST_LISTENER=
(SID_LIST=
(SID_DESC=
(ORACLE_HOME= /u01/app/oracle/product/11.2.0/dbhome_1)
(SID_NAME = PROD)
)
)

Reload listener configuration

$ lsnrctl
LSNRCTL> reload

Generate and update Context file

$perl $ORACLE_HOME/appsutil/bin/adbldxml.pl

During the enquiry phase, configure the context file to use SCAN. After generating the context file, update the
variable s_virtual_hostname to refer to the database node VIP.
For example,
<host oa_var="s_virtual_hostname">dbnode-vip</host>

Run AutoConfig on DB Tier

$ ORACLE_HOME/appsutil/bin/adconfig.sh

https://support.oracle.com/epmos/faces/DocContentDisplay?_adf.ctrl-state=mt8r1v5vt_210...

5/7/2015

Document 1566935.1

Page 10 of 14

Update Grid Infrastructure (GI) Network files

Since the listeners are run from the GI home, the network configuration should be updated to include the files
generated for the Applications setup. The network files listener.ora, sqlnet.ora and tnsnames.ora for the
Applications setup are generated in the directory $ORACLE_HOME/network/admin/<CONTEXT_NAME>. Validate
the files exist. Next, update the listener.ora, sqlnet.ora & tnsnames.ora in the network/admin directory of the GI
home to include the generated files.
For example, in the listener.ora file of GI Home, add the following entry:
ifile=/u01/app/oracle/product/11.2.0.3/dbhome_1/network/admin/<DB>_<dbnode>/listener.ora

Similarly, update the sqlnet.ora of GI home with the following entry:

ifile=/u01/app/oracle/product/11.2.0.3/dbhome_1/network/admin/<DB>_<dbnode>/sqlnet.ora

The tnsnames.ora of the GI home also needs to be update with:

ifile=/u01/app/oracle/product/11.2.0.3/dbhome_1/network/admin/<DB>_<dbnode>/tnsnames.ora

Update OCR
Update the OCR to setup TNS_ADMIN set to the GI network admin files.
$ srvctl setenv database -d PROD -T \ TNS_ADMIN=/u01/app/11.2.0/grid/network/admin

Run adgrants.sql and grant create procedure privilege on CTXSYS

copy $APPL_TOP/admin/adgrants.sql file to the DB server
$ sqlplus "/ as sysdba" @adgrants.sql [APPS schema name]
$AD_TOP/patch/115/sql/adctxprv.sql
$ sqlplus apps/[APPS password] @adctxprv.sql [SYSTEM password] CTXSYS

Update TNS alias on App tier

Update TNS alias on the application tier server to use SERVICE_NAME and INSTANCE_NAME. For example,
FRESH=
(DESCRIPTION=
(ADDRESS=(PROTOCOL=tcp)(HOST=dscgig03-vip.us.oracle.com)(PORT=1521))
(CONNECT_DATA=(SERVICE_NAME=PROD)(INSTANCE_NAME=PROD) )
)

https://support.oracle.com/epmos/faces/DocContentDisplay?_adf.ctrl-state=mt8r1v5vt_210...

5/7/2015

Document 1566935.1

Page 11 of 14

Validate Workflow Rules Set

$ FND_TOP/patch/115/sql/wfaqupfix.sql
$ sqlplus [APPS user]/[APPS password] @wfaqupfix.sql [APPLSYS user] [APPS user]

Update jdbc_url setting in context file

In the application node, update the context file to specify the correct values of HOST (the SCAN hostname),
PORT, SERVICE_NAME & INSTANCE_NAME. For example,
<jdbc_url oa_var="s_apps_jdbc_connect_descriptor">jdbc:oracle:thin:\
@(DESCRIPTION=(ADDRESS_LIST=(LOAD_BALANCE=YES)(\
FAILOVER=YES)(ADDRESS=(PROTOCOL=tcp)(HOST= dbnode-\ scan.us.oracle.com)(PORT=1521)))
(CONNECT_DATA=(SERVICE_NAME=\
PROD) (INSTANCE_NAME=PROD)))</jdbc_url>

Note: For ease of reading, the entry is broken into multiple lines using a line break.

Run AutoConfig on app tier

$INST_TOP/admin/scripts/adautocfg.sh

Gather SYS schema stats

$APPL_TOP/admin/adstats.sql
$ sqlplus "/ as sysdba"
SQL> alter system enable restricted session;
SQL> @adstats.sql
$ sqlplus "/ as sysdba"
SQL> alter system disable restricted session;

Re-Create Grants and Synonyms

On the Application Tier, execute adadmin. Select 4. Maintain Applications Database Entities menu and then
option 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

$ INST_TOP/admin/scripts/adstrtal.sh

https://support.oracle.com/epmos/faces/DocContentDisplay?_adf.ctrl-state=mt8r1v5vt_210...

5/7/2015

Document 1566935.1

Page 12 of 14

Synchronize Workflow Views

Log on to Oracle E-Business Suite with the "System Administrator" responsibility.
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

Migrating Database using Rapid Clone

In some cases, an existing Oracle E-Business Suite database may simply be moved to an Oracle Database Appliance envir
The standard Oracle E-Business Suite database cloning is the preferred utility for these migration scenarios. Refer t

Note: Additional information on database migration options and Oracle E-Business Suite supported versions
can be found in the appendix A.
The cloning process may include preparing the source environment, copying the database to Oracle Database
Appliance, and completing post-cloning steps.
Once the database files have been copied, execute the following steps in the Oracle Database Appliance
environment to complete the cloning process.
1. Configure database initialization parameters based on Oracle Database Appliance DBCA templates. The
following parameters need to be set for all databases:
_disable_interface_checking=true
_gc_undo_affinity=false
_gc_policy_time=0
_enable_numa_support=false
_file_size_increase_increment=2143289344
db_recovery_file_dest='+RECO'
db_create_file_dest='+DATA'
db_create_online_log_dest_1='+REDO'
db_block_checksum=full
db_block_checking=full
db_lost_write_protect=typical
filesystemio_options=setall
use_large_pages=only
2. Move REDO log files to +REDO diskgroup on Solid State Disks (SSDs).
For each redolog group, add an additional member with '+REDO' diskgroup as the location.
SQL> alter database add logfile member '+REDO' to group 1;

Then, for each redolog group, drop the old member.

https://support.oracle.com/epmos/faces/DocContentDisplay?_adf.ctrl-state=mt8r1v5vt_210...

5/7/2015

Document 1566935.1

Page 13 of 14

SQL> alter database drop logfile member '<non REDO diskgroup path>';

Conclusion
Oracle Database Appliance is an engineered system from Oracle that is easy to deploy, manage, and maintain.
This paper describes how to implement an Oracle E-Business Suite database on Oracle Database Appliance and
outlines the best practices

Appendix A - Database migration options

There are several options available for migrating Oracle E-Business Suite database to Oracle Database
Appliance. The following are some of the common approaches. You may refer to standard Oracle
documentation for details on each of these methods.

Oracle Data Guard

Oracle Data Guard provides an easy to use approach to migrate Oracle E-Business Suite databases to an Oracle
Database Appliance environment. This can be easily accomplished by creating a physical standby database on
Oracle Database Appliance for a source Oracle E-Business Suite database that may be operating in a non-Oracle
Database Appliance environment. Oracle Data Guard physical standby database requires the source and target
databases to be running on the same operating system. Therefore, this approach to migrate a database from a
non-Oracle Database Appliance environment to Oracle Database Appliance can only be used when the source
database is operating in a Linux environment as used by Oracle Database Appliance.

Transportable Tablespaces
The Transportable Tablespace feature can be used to migrate an Oracle E-Business Suite database to an Oracle
Database Appliance environment. This method requires some down time on the source database.

Transportable Database
The Transportable Database feature can also be used to migrate an Oracle E-Business Suite database to an
Oracle Database Appliance environment. This method cannot be used for migrating across different Endian
formats. The source system must be 11.2 and the platform must be little Endian. This method also requires
some down time on the source database.

Data Pump
Oracle Data Pump provides the most flexible approach to migrate a database from an external environment to
Oracle Database Appliance as it can operate across database versions. Data Pump is also an excellent choice
when performing cross-platform database migrations. However, extracting, moving, and loading data from the
source system to the target system can be a long process and could require extended downtime depending on
the size of the database being migrated.

https://support.oracle.com/epmos/faces/DocContentDisplay?_adf.ctrl-state=mt8r1v5vt_210...

5/7/2015

Document 1566935.1

Page 14 of 14

Appendix B: References
1. My Oracle Support Knowledge Document: 406982.1 -- Cloning Oracle Applications Release 12 with Rapid
Clone
2. My Oracle Support Knowledge Document: 1362116.1 -- ODA (Oracle Database Appliance): How to
Convert Single-Instance database to RAC on Oracle Database Appliance Using RCONFIG Utility
3. My Oracle Support Knowledge Document: 1457717.1 -- How to customize available disk space for
installing your application on the Oracle Database Appliance (ODA)
4. My Oracle Support Knowledge Document: 761566.1 -- Oracle E-Business Suite Installation and Upgrade
Notes Release 12 (12.1.1) for Linux x86-64
5. My Oracle Support Knowledge Document: 1058763.1 -- Interoperability Notes EBS R12 with Database
11gR2
6. My Oracle Support Knowledge Document: 823587.1 -- Using Oracle 11g Release 2 Real Application
Clusters with Oracle E-Business Suite Release 12

Didn't find what you are looking for?

https://support.oracle.com/epmos/faces/DocContentDisplay?_adf.ctrl-state=mt8r1v5vt_210...

5/7/2015