1

2
3
4
EBS 12.2 represents our most-groundbreaking release in years. It includes new
product functionality, new Fusion Middleware and database components, and
introduces new tools for installing, configuring, and maintaining E-Business Suite
environments:
• Includes significant enhancements across the integrated suite of business
applications spanning enterprise resource planning, human capital management,
and supply chain management.
• Apply EBS patches while users are still entering transactions and using the E-
Business Suite. Online Patching uses the Oracle Database's Edition-Based
Redefinition feature and other new technologies to allow the E-Business Suite to
be updated while the system is still running.
• Uses Oracle WebLogic Server, which replaces the Oracle Containers for Java (OC4J)
application server used in EBS 12.0 and 12.1.
• Streamlined installation
Option for installing EBS 12.2 on to existing database servers.
• Capability of installation into existing Real Application Clusters environments.
• Database deployment on Automatic Storage Management (ASM) and other file
systems.

5
The online patching mechanism introduced with Oracle E-Business Suite Release 12.2
uses a dual file system. At a given time, one file system (designated 'run') is part of
the running system, while the other (designated 'patch') is either having patches
applied or standing by in readiness for patch application. The two file systems are
often referred to as fs1 and fs2. It is important to distinguish between the file system
(fs1 or fs2) ) itself and its current role, which alternates between 'patch' and 'run'
with every patching cycle. As well as fs1 and fs2, there needs to be a non-editioned
file system (fs_ne), which is used to store files containing data that is needed across
all file systems.
Log Files
Oracle E-Business Suite Release 12.2 has seen significant changes to the locations
under which log files are stored. In large part, this is because of the introduction of
online patching and the additional file systems it employs. The adoption of Oracle
WebLogic Server for some configuration management tasks has brought its own log
file requirements, over and above those of the traditional AutoConfig tool.
$LOG_HOME
This environment variable and its associated location are used in Release 12.2 as they
were in previous releases. Most of the Oracle E-Business Suite log files are stored
here, under $LOG_HOME/appl/admin/log. Examples include service control logs,

6
AutoConfig logs, and runtime-generated logs.
A change in Release 12.2 is that HTTP, Oracle WebLogic Server, and concurrent
processing log files are not stored under $LOG_HOME as they were in previous
releases:
HTTP log files are located under the native instance home.
Oracle WebLogic Server log files are located under the domain home.
Concurrent processing log files are located on the none-editioned file system (fs_ne)
Patching Log Files
The adop log files for online patching are located on the non-editioned file system
(fs_ne), under:
s_ne_base/EBSapps/log/adop/<adop_session_id>/<phase_timestamp>/<context_na
me>For example, if s_ne_base was /u01/R122_EBS/fs_ne, the adop log files would
be located under:
/u01/R122_EBS/fs_ne/EBSapps/log/adop/<adop_session_id>/<phase_timestamp>/<
context_name>For more information, see 'The adop Utility' in the Patching Utilities
chapter of Oracle E-Business Suite Maintenance Guide.
Configuration Log Files
The AutoConfig log files are stored under <INST_TOP>/admin/log/<MMDDhhmm> on
the Application tier, and
<RDBMS_ORACLE_HOME>/appsutil/log/<CONTEXT_NAME>/<MMDDhhmm> on the
Database tier.
For more information, see the Technical Configuration chapter of Oracle E-Business
Suite Setup Guide.
Language Files
When you install Oracle E-Business Suite in a language other than American English,
each product tree includes directories that use the relevant NLS language code. These
directories hold translated data, forms, and message files. For example, the language
directory named D designates German. The data loader files in the D subdirectory of
the admin directory contain the German translation of the product seed data.
The US subdirectory in the forms directory contains Oracle Forms forms in American
English. The D directory in the forms directory contains the same forms, translated
into German. However, the mesg directory contains message files in both American
English and German.
Note: For further details, see the Oracle Globalization Support Guide.
Core Technology Directories
The admin, ad, au, and fnd directories are the core technology directories. They, along
with product directories such as ar and gl, are located under the $APPL_TOP
directory. For example, /u01/R122_EBS/fs1/EBSapps/appl/admin.
The admin directory
This directory and its subdirectories contain files and scripts used by the AD utilities
during upgrade and maintenance processes.
These files and scripts include:

6
The adovars.env environment file, which defines certain file and directory locations.
Scripts run during the upgrade.
<SID>/log and <SID>/out directories for upgrade, log, and output files respectively.
A <SID>/restart directory where AD programs create restart files.
The ad (Applications DBA) directory
This directory and its subdirectories contain installation and maintenance utilities,
including:
AD Administration (adadmin)
AutoConfig (adconfig.sh)
The au (Applications Utilities) directory
This directory and its subdirectories contain product files that are consolidated in a
single location for optimal processing. These files include:
PL/SQL libraries used by Oracle Forms, in the resource subdirectory
Oracle Forms source files, in the forms subdirectory
A copy of all Java files used when regenerating the desktop client JAR files, in the java
subdirectory
Certain reports needed by products such as Discoverer, in the reports subdirectory
The fnd (Application Object Library) directory
This directory and its subdirectories contain the scripts and programs that are used as
the foundation for all Oracle E-Business Suite products to build data dictionaries,
forms and C object libraries.

6
7
8
9
10
Area
Create an Oracle E-Business Suite 12.2 stage directory, then copy only the zip files you
downloaded from Oracle E-Delivery Portal specified in sections A through E below to
your stage directory. Important: There should not be any additional zip files present
in stage area apart from those listed below. Addition files will result in installation
hang at 38%.
Steps to download Oracle E-Business Suite Release 12.2.0 installation files from
Oracle E-Delivery Portal

1. Navigate to the "Oracle Software Delivery Cloud" (formally known as E-Delivery

site): http://edelivery.oracle.com/
2. Click on "Sign In" button
3. Use My Oracle Support account username/password(same account that you use to
create a new SR).
4. Once logged in, Accept the terms and condition for "Export Restriction"
5. Do a search with the following parameters in next screen:
Product - select "Oracle Payroll" from drop down list. You can search with any other
product like "Oracle Purchasing" or "Oracle Order Management"
Platform - select "Linux x86-64" or as applicable for your OS

11
6. In the search result list, you will see “Oracle E-Business Suite Release 12.2.5 Update
Pack for Linux x86-64” (this always will be the most recent version available for the
application)
7. Click on "Continue" button (by default, it should have the appropriate one
selected)
8. Select the check box for "License Agreement" and click on the "Continue" button.
9. In next screen, Download the files as mentioned below in this document.

Note: Scroll down for 'Oracle E-Business Suite (12.2.0)' to obtain the files listed in this
note.

A. Oracle E-Business Suite Release 12.2.0 Rapid Install Start Here (All Parts)
The startCD version available with the install materials on Oracle E-Delivery Portal is
12.2.0.51. Oracle support strongly recommend you use latest startCD 12.2.0.51,
either available on Oracle E-Delivery Portal or via Patch 22066363. If you are
planning to install EBS R12.2.0 then upgrade from R12.2.0 to R12.2.5, you must use
startCD 51 (12.2.0.51) to create the stage area for R12.2.0.

Note : For Example, Below listed zip file numbers are for <Platform> = Linux x86-64
under "Oracle E-Business Suite Release 12.2.0 Rapid Install Start Here" from Oracle E-
Delivery Portal.

V100052-01_1of3.zip
V100052-01_2of3.zip
V100052-01_3of3.zip
Or
For latest startCD 12.2.0.51, Please download Patch 22066363 available on My Oracle
Support and unzip in a directory.
p22066363_R12_GENERIC.zip
Note: Oracle support strongly recommend you use latest startCD 12.2.0.51, available
via Patch 22066363 or startCD available on Oracle E-Delivery Portal.

B. Oracle E-Business Suite Release 12.2.0 for <Platform> Rapid Install (All Disks and
Parts) Ex: <Platform> = Linux x86-64
Note : For Example, Below listed zip file numbers are for <Platform> = Linux x86-64

V100053-01_1of2.zip
V100053-01_2of2.zip
V100054-01.zip
V100055-01.zip
V100056-01.zip
V100057-01.zip

11
V100058-01.zip
V100059-01_1of2.zip
V100059-01_2of2.zip
V100060-01_1of3.zip
V100060-01_2of3.zip
V100060-01_3of3.zip
V46095-01_1of2.zip
V46095-01_2of2.zip
V35802-01.zip
V35803-01_1of3.zip
V35803-01_2of3.zip
V35803-01_3of3.zip
V35804-01_1of2.zip
V35804-01_2of2.zip
C. Oracle E-Business Suite Release 12.2.0 for <Platform> Rapid Install Technology one-
off Patches. Ex: <Platform> = Linux x86-64
Note : For Example, Below listed zip file number is for <Platform> = Linux x86-64

V100061-01.zip
D. Oracle WebLogic Server 11gR1 (10.3.6) Generic and Coherence
Note : For Example, Below listed zip file number is for <Platform> = Linux x86-64

V29856-01.zip
E. Oracle Fusion Middleware Web Tier Utilities 11g Patch Set 7 (11.1.1.9.0) for
<Platform> . Ex: <Platform> = Linux x86-64
Note : For Example, Below listed zip file number is for <Platform> = Linux x86-64

V75792-01.zip

Note: Please refer below document and compare md5 checksum results to confirm
12.2 stage for any corruption due to incorrect download of the media from Oracle E-
Delivery Portal.
Note 1505510.1: MD5 Checksums for R12.2 Rapid Install Media

11
Create an Oracle E-Business Suite 12.2 stage directory, then copy only the zip files you
downloaded from Oracle E-Delivery Portal specified in sections A through E below to
your stage directory. Important: There should not be any additional zip files present in
stage area apart from those listed below. Addition files will result in installation hang
at 38%.
Steps to download Oracle E-Business Suite Release 12.2.0 installation files from
Oracle E-Delivery Portal
1. Navigate to the "Oracle Software Delivery Cloud" (formally known as E-Delivery
site): http://edelivery.oracle.com/
2. Click on "Sign In" button
3. Use My Oracle Support account username/password(same account that you use
to create a new SR).
4. Once logged in, Accept the terms and condition for "Export Restriction”
5. Do a search with the following parameters in next screen:Product - select "Oracle
Payroll" from drop down list. You can search with any other product like "Oracle
Purchasing" or "Oracle Order Management"Platform - select "Linux x86-64" or as
applicable for your OS
6. In the search result list, you will see “Oracle E-Business Suite Release 12.2.5
Update Pack for Linux x86-64” (this always will be the most recent version

12
 available for the application)
7. Click on "Continue" button (by default, it should have the appropriate one
selected)
8. Select the check box for "License Agreement" and click on the "Continue" button.
9. In next screen, Download the files as mentioned below in this document.

12
After creating the stage area directory it is required to manually unzip only the
"Oracle E-Business Suite Release 12.2.0 Rapid Install Start Here" or unzip Patch
22066363 files. Do not manually unzip the other stage files. After unzipping the
startCD, the buildStage.sh script should be run to unzip the rest of the installation
software.

Running the buildStage.sh script is a mandatory pre-installation step. To create a

successful R12.2 stage, you must run buildStage.sh as suggested below with "Option
1" first "Create new stage area" followed by "Option 2" "Copy new patches to current
stage area.". The buildStage.sh script is run as follows:

$ cd /u01/StageR122/startCD/Disk1/rapidwiz/bin
$ buildStage.sh

[oracle@erp]$ ./buildStage.sh

Build Stage Menu

------------------------------------------------------

13
1. Create new stage area

2. Copy new patches to current stage area.

3. Display existing files in stage TechPatches.

4. Exit menu

Enter your choice [4]: 1

Rapid Install Platform Menu

------------------------------------------------------

1. Oracle Solaris SPARC (64-bit)

2. Linux x86-64

3. IBM AIX on Power Systems (64-bit)

4. HP-UX Itanium

5. Exit Menu

Enter your choice [5]: 2

Once completed above step successfully, you must run the buildStage.sh script and
select option 2. Copy new patches to current stage area from the Build Stage Menu:

Build Stage Menu

------------------------------------------------------

1. Create new stage area

2. Copy new patches to current stage area.

3. Display existing files in stage TechPatches.

13
4. Exit menu

Enter your choice [4]: 2

This will copy the latest technology patches to the shiphome. Failure to do this will
cause the installation to fail during the Oracle Home patching phase.

Important: Please review the R12.2 installation documents and make sure that all OS
pre-requisites has been met prior to installing R12.2.

13
EBS R12.2 comes with dual file systems and therefore we need to select port pools
for each of the file editions, that is run and patch. This is required to avoid port
conflicts and making sure both file system services are no overlapping.

14
Starting from Oracle E-Business suite R12.2 we can configure RAC database during
the first Installation itself. It makes the life of Apps DBA's easier. Oracle EBS R12.2 is
shipped with database 12.1.0.2 and If want to configure RAC database during first
Install then we need to make sure that 12.1.0.2 Grid Infrastructure is configured
before Installation of EBS R12.2.

15
One of the other new features of R12.2 is that database files can be directly laid out
to Oracle ASM storage. Please note the directory structure format when installing
database to ASM. The database files aliases would be created under /dbfiles directory
in ASM.

16
17
Installation screen – Application User Information.

18
19
20
21
22
23
24
The EBS Technology Codelevel Checker (ETCC) utility provides two scripts you can run
to help ensure you have the necessary database and middle tier bugfixes installed on
your Oracle E-Business Suite Release 12.2 system. Oracle strongly recommends the
use of this utility to ensure that all required database and middle tier bugfixes have
been installed.
ETCC can be downloaded via Patch 17537119 from My Oracle Support. The latest
version (January 2016) maps missing bugfixes to the default corresponding patches
and displays them in a patch recommendation summary. If your Oracle E-Business
Suite 12.2 installation has additional patches installed as well as the recommended
patches, you may need to install a merge patch from Oracle Support. As well as
installation instructions and basic commands, the README for this patch includes a
number of usage scenarios and examples so should be carefully reviewed before
running ETCC.
Note: Always use the latest version of ETCC, as new bugfixes will not be checked by
older versions of the utility. Also, patch recommendation summaries are only
provided for the latest and latest but one quarterly bundles supported by Oracle E-
Business Suite Release 12.2. Refer to Section 3: Database Patches and Bug Numbers
for the Oracle database releases and bundle documentation.
The two scripts that make up ETCC are:

25
checkDBpatch.sh (checkDBpatch.cmd on Microsoft Windows). This is the Database
EBS Technology Codelevel Checker (DB-ETCC), which determines if all the needed
bugfixes exist in the specified database ORACLE_HOME. When using Oracle Real
Application Clusters (Oracle RAC) ensure ETCC is run on every database
ORACLE_HOME.
checkMTpatch.sh (checkMTpatch.cmd on Microsoft Windows). This is the Middle
Tier EBS Technology Codelevel Checker (MT-ETCC), which determines if all the needed
bugfixes exist in the middle tier file system.

25
Screenshot – database patches reported by ETCC.

26
Screenshot – middleware patches reported by ETCC.

27
Oracle strongly recommends that you always apply the latest version of the AD and
TXK release update packs at your earliest convenience. New AD and TXK code fixes
require the codelevel documented here as a prerequisite. If for some specific reason
you need to use an older version for a limited period, refer to My Oracle Support
Knowledge Document 1903052.1, Applying A Non-Current Version of the AD and TXK
Release Update Packs to Oracle E-Business Suite Release 12.2.

28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
In Release 12.2.0 and higher, patching is performed by running the new adop (AD
Online Patching) utility. You must use adop instead of the adpatch utility that was
provided in previous releases. Download and unzip all the patches to the default
patch location for Release 12.2 ($PATCH_TOP). The PATCH_TOP location must be
accessible to all application tier nodes in an application tier configuration. For more
information about the adop utility, refer to Oracle E-Business Suite Concepts (Part No.
E22949) and Oracle E-Business Suite Maintenance Guide, Release 12.2 (Part No.
E22954).

45
46
1. Prepare: This syncs the current patch file system with run file system, to make sure
patch file system is up to date compared to run file system and ready for the patches
to get applied. This also created a new patch edition in the database. This syncing
process is incremental process to be efficient
$ adop phase=prepare

2. Apply : Patches are applied to patch file system during this phase, we can apply as
many patches we want during this phase. Changed code objects are from patch
edition of database. Changes to tables are stored in new columns which are only
visible from patch edition of the database.

$ adop phase=apply patches=<patch_#>

3. Finalize: This phase involves compiling of invalid objects etc.

$ adop phase=finalize

4. Cutover: This phase configures the patch file system as new run file system and
patch edition of the database as new run edition. Restart application services from

47
new run file system of Apps. This is where downtime is required.

$ adop phase=cutover

5. Cleanup: Deletes obsolete code objects and columns from earlier patch edition are
removed at database.

$ adop phase=cleanup

47
48
49
50
51
52
53
54
55