Database Reference
In-Depth Information
will be reluctant to upgrade their systems to R12.2 so soon after the date of general availability, so the migrations of
Release 12.1 to ODA will still be common.
For new implementations, the R12.2 Rapid Install process has been improved by packaging RMAN backups of
the e-Business Suite database and adding options to deploy the RAC or single node configuration using ASM or file
system to store the data files. This provides more flexibility compared to the only native deployment option that was
available for R12.1—the single node database with data files on a file system. Unfortunately, you will not be able to
use these new capabilities to deploy the R12.2 environment into the ODA's RAC on ASM, because the e-Business Suite
database has been prepackaged with the
compatible=11.2.0
parameter. In addition, the database compatibility of
ASM disk groups on ODA is set to 11.2.0.2. This behavior was observed while using the latest available version of the
Rapid Install StartCD (12.2.0.46), and it might change in later versions, so make sure to check My Oracle Support note
“Oracle E-Business Suite Release Notes, Release 12.2 (Doc ID 1320300.1)” for information about the StartCD updates.
Listing 11-1 shows the errors reported by the Rapid Install process if you try to install the database directly to an
ASM disk group on ODA.
Listing 11-1.
Release 12.2 Installation Errors When ASM Is Used for Data Files on ODA
RMAN-03002: failure of restore command at 10/17/2013 22:16:46
ORA-19504: failed to create file "+DATA/controlfile_tst1221.ctl"
ORA-17502: ksfdcre:3 Failed to create file +DATA/controlfile_tst1221.ctl
ORA-15001: diskgroup "DATA" does not exist or is not mounted
ORA-15204: database version 11.2.0.0.0 is incompatible with diskgroup DATA
ORA-19600: input file is control file (/SOFTWARE/eBS/R12.2.2/stage/EBSInstallMedia/AppDB/PROD/
backup_controlfile.ctl)
ORA-19601: output file is control file (+DATA/controlfile_tst1221.ctl)
The inability to deploy the system on ASM by running Rapid Install introduces a serious complication for the
installation process of R12.2 on ODA. The initial installation of the e-Business Suite database has to be on a file
system and, as the only shared storage option for a RAC database on ODA is ASM, you're also limited to a single node
configuration. This means the freshly deployed e-Business Suite will have to be migrated to ASM and converted to
RAC immediately after the installation.
If you're planning a migration project for your e-Business Suite R12.1 system to an ODA without upgrading it to
R12.2, then the complexity of the whole project depends on the current state of the system. The target state is clear—
an 11.2 database running on Linux x86-64, and an Oracle Linux 5 or 6 for the application tier in case you choose to
deploy as virtual machines on ODA. Although it's technically possible to build the application tier using Red Hat
Enterprise Linux as the OS on the VMs, it's not recommended in order to preserve the “one throat to choke” support.
4
The contents of this chapter will explain how to configure the ODA to be capable of running the e-Business Suite
R12.2, but the same configuration of the ODA is also able to run e-Business Suite 12.1.
The deployment process of the e-Business Suite R12.1 database tier on ODA in a bare metal (nonvirtualized)
configuration has been very well explained in My Oracle Support note “Implementing Oracle E-Business Suite 12.1
Databases on Oracle Database Appliance (Doc ID 1566935.1).” At this moment,
5
a dedicated note for R12.2 is not available,
but must be similar. Here I'll pay most of the attention to the virtualized deployment of e-Business Suite R12.2 on ODA.
Plan for Your Unique Environment
One of the settings to be careful at is the number of CPU cores you choose to enable and license by generating the
license keys in My Oracle Support. If you set the initial core count too high, it's not possible to reduce it in bare metal
configurations without assistance from My Oracle Support. It's better to start with a lower setting that can be increased
later if needed.
4
The same vendor supports all components of the system.
5
October 17, 2013.
