10/8/2018 Document 1349240.

1
Copyright (c) 2018, Oracle. All rights reserved. Oracle Confidential.

Database Preparation Guidelines for an E-Business Suite Release 12.2 Upgrade (Doc ID
1349240.1)

Database Preparation Guidelines for an Oracle E-Business Suite

Release 12.2 Upgrade
October 2018

In this Document

Overview
Upgrade Paths
References
Change Log

Overview
i
This document details the database preparation process for Oracle E-Business Suite Release 11 and R12 (12.0, 12.1)
customers planning to upgrade to Release 12.2.

This document is subject to continual update after initial release and changes are listed in the Change Log below. If you
print this document, periodically check to ensure you have the most recent version. The current version of this document
can be obtained in My Oracle Support Knowledge Document 1349240.1.

Unlike previous versions of Oracle E-Business Suite R12, 12.2 is not supported with earlier versions of the RDBMS such as
i
9 , 10gR2 or 11gR1. The Edition Based Redefinition feature (available starting with 11gR2) is required to implement
'Online Patching' to achieve reduced downtimes during the application of 12.2 Oracle E-Business Suite patches.

The Release 12.2 Rapid Install (beginning with startCD 51) delivers the 12cR1 (12.1.0.2) version of the Oracle RDBMS
including required patches for interoperability with EBS. Upgrading the database to version 11.2.0.4 or higher is required
for an Oracle E-Business Suite upgrade to 12.2. Earlier versions of the startCD delivered 11gR2 (11.2.0.3) of the Database
- those versions are not recommended any more for use in the 12.2 upgrade.

Note: Database desupport schedules have important operational and planning implications for Oracle E-Business
Suite environments. Oracle strongly recommends that customers review the following documents detailing the latest
database support policies and desupport schedules:

Database, FMW, Enterprise Manager, TimesTen In-Memory Database, and OCS Software Error Correction Support
Policy (My Oracle Support Knowledge Document 209768.1)
Release Schedule of Current Database Patch Sets (My Oracle Support Knowledge Document 742060.1)

Note: In performing the upgrade to 12.2 from 11i or 12.0/12.1, ensure you have the latest Rapid Install patch (or
startCD patch) before you begin your upgrade.

This document assumes that the startCD version is 51 or higher, with the latest available version
recommended for use by customers - see the Oracle E-Business Suite Release Notes, Release 12.2
(My
Oracle Support Knowledge Document 1320300.1) for information on the current version of startCD.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=1ac33yw52w_57&id=1349240.1 1/13
10/8/2018 Document 1349240.1

Note: If you are using an Oracle RAC environment, you should only run the Release 12.2 upgrade on a single Oracle
RAC node.
This is because most of the elapsed time in the upgrade will be taken by jobs running DML (INSERT, UPDATE,
DELETE). These jobs use multiple workers and parallel severs, which will typically attempt to access the same objects
and blocks at the same time. The consequent additional communication between cluster nodes (and associated
cluster waits) will significantly outweigh any gains from using the additional CPUs to increase throughput.

The process of upgrading Oracle E-Business Suite to Release 12 involves updating the middleware technology stack with a
new installation in addition to installing a new APPL_TOP on the application tier.

The primary utilities used in the R12 upgrade process are Rapid Install and AutoPatch. Rapid Install installs the new R12
technology stack and AutoPatch upgrades the Oracle E-Business Suite database to Release 12. The upgrade no longer
requires a two-step approach of upgrading the Oracle E-Business Suite database by running AutoUpgrade and AutoPatch.
The upgrade is a one step approach of updating the data model by using the R12 AutoPatch tool.

i
The 11 requirement for upgrading to Release 12.2 is that the Oracle E-Business Suite version be at 11.5.10.2 along with
minimum baseline patches - see Patch Requirements for Sustaining Support for Oracle E-Business Suite Release 11.5.10
(My Oracle Support Knowledge Document 883202.1). Systems on Releases 11.5.1 to 11.5.10 must be first upgraded to
11.5.10.2 prior to attempting a 12.2 upgrade.

For all Oracle E-Business Suite systems, the database must at least be on version 11gR2 before proceeding with the 12.2
upgrade process and specifically prior to running AutoPatch to upgrade the data model:

Customers on the latest patchsets of earlier database versions (10gR2, 11gR1) or earlier patchsets of 11gR2 or
12cR1 may upgrade using the 12cR1 (12.1.0.2) database Oracle Home installed from the 12.2 Rapid Install which
also includes required interoperability patches.
Customers on older patchsets of earlier database versions (10gR2, 11gR1, 11gR2) should upgrade to the latest
11gR2 (11.2.0.4) patchset and apply all required interoperability patches.
Customers already on the latest patchsets of 11gR2 (11.2.0.4) or 12cR1 (12.1.0.2) should update their existing
Oracle Home and apply all required interoperability patches.
i
Customers on 11.5.10.2 with the 9 version of the database must upgrade to either 11gR2 (11.2.0.4) or 12cR1
(12.1.0.2) prior to performing the 12.2 upgrade (i.e. they cannot combine the Database and Oracle E-Business
Suite upgrades in one single downtime). It is recommended to go to the latest patchset available for the Database.

For R12, the requirement is that the Oracle E-Business Suite versions be at 12.0.4 (or higher) or 12.1.1 (or higher) prior to
upgrading to 12.2 - the database must be upgraded to the latest patchsets of 11gR2 or 12cR1 prior to the 12.2 upgrade if
not already done so.

Upgrade Paths
Prior E-Business Suite R12 (such as 12.0 and 12.1) upgrade processes certified earlier database versions as part of the
overall R12 upgrade - starting with 12.2, customers must first be at 10gR2, 11gR1, 11gR2 or 12cR1 of the database prior
to upgrading to 11gR2 or 12cR1 as part of the 12.2 upgrade (if not already done). The requirement for 11gR2 or 12cR1 in
12.2 is due to the use of unique newer database features in the release such as Edition Based Redefinition.

E-Business Suite supports the upgrade of the Database using the version included with the 12.2 Rapid Install media -
beginning with startCD 51, the Database version bundled with Rapid Install is 12cR1 (12.1.0.2). Prior startCD versions
included 11.2.0.3, and customers using earlier startCD versions were required to upgrade their existing Oracle Homes to
the latest 11gR2 or 12cR1 patchsets prior to upgrading to 12.2.

The following table lists the current available 12.2 upgrade paths for the supported Oracle E-Business Suite and Database
releases from which customers would be upgrading:

Oracle E-Business Suite

Current Database Release Av
Release

11.5.10.2, 12.0.4+, 12.1.1+ 10gR2 (10.2.0.5), 11gR1 (11.1.0.7), 11gR2 (11.2.0.2 or later), 12cR1 (12.1.0.1) Pa

11.5.10.2, 12.0.4+, 12.1.1+ 10gR2, 11gR1, 11gR2 (11.2.0.1, 11.2.0.2, 11.2.0.3) Pa

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=1ac33yw52w_57&id=1349240.1 2/13
10/8/2018 Document 1349240.1

11.5.10.2, 12.0.4+, 12.1.1+ 11gR2 (11.2.0.4) Pa

11.5.10.2, 12.0.4+, 12.1.1+ 12cR1 (12.1.0.2) Pa

Path A: Customers on 11.5.10.2/12.0/12.1 with earlier DB or patchset versions upgrading Database to 12cR1
(12.1.0.2) using Rapid Install

This path follows the 12.2 upgrade path as documented in the Oracle E-Business Suite Upgrade Guide: Release 11i to
Release 12.2 and Oracle E-Business Suite Upgrade Guide: Release 12.0 and 12.1 to Release 12.2.
Customers choosing this path will follow the instructions in Chapter 4 ('Performing the Upgrade') in the appropriate Oracle
E-Business Suite Upgrade Guide where they are asked to run Rapid Install to install the applications technology stack -
pick the 'Create Upgrade File System' option in the 'Select Upgrade Action' dialog window, and do not pick the 'Use
Existing Oracle Home' option in the 'Database Node Configuration' dialog window while running rapidwiz. This upgrade
installation will include a new E-Business Suite application tier and all required technology stack components including a
new 12.1.0.2 Oracle Home and required patches needed for the upgrade.

Note: The upgrade of the Database to 12cR1 and the upgrade to 12.2 must be done in a single downtime following
the process outlined in this path. Customers wishing to upgrade the Database to 12cR1 and then bring up their 11i,
12.0 or 12.1 system as an interim step should simply follow the appropriate Interoperability Notes
(see References
section below) to upgrade to 12cR1 first - you can then upgrade to 12.2 following Path C below at a later downtime.

Here are the steps:

1. Plan Upgrade to 12.2 and Install the 12cR1 Database Oracle Home
Follow the standard 12.2 upgrade path as documented in the Oracle E-Business Suite Upgrade Guide: Release 11i
to Release 12.2 Oracle E-Business Suite Upgrade Guide: Release 12.0 and 12.1 to Release 12.2
or . Perform all
requirements documented in Chapters 1, 2 and 3 and all applicable steps in Chapter 4 including installing the new
12.1.0.2 Oracle Home using the 12.2 Rapid Install wizard.

Before performing the next step, review My Oracle Support Knowledge Document 1594274.1 (' Oracle E-Business
Suite Release 12.2: Consolidated List of Patches and Technology Bug Fixes ') and apply any additional patches that
may be needed for Oracle Database 12.1.0.2 listed in Section 3 of the document.

Also note the value of the Database initialization parameter 'SEC_CASE_SENSITIVE_LOGON' in the pre-upgrade
database, which will be needed for the new Database created by Rapid Install (see Step ' Check and Modify
Initialization Parameters' below)

2. Upgrade Database to 12.1.0

Refer to the 'Interoperability Notes: Oracle Applications Release 11i with Oracle Database 12c Release 1 (12.1.0)' if
upgrading from 11i, or 'Interoperability Notes: Oracle E-Business Suite Release 12 with Oracle Database 12c
Release 1 (12.1.0)' if upgrading from Release 12.0 or 12.1 (see References section below).

Perform only the following in the appropriate Interoperability Notes to upgrade the Database to 12.1.0:
Apply only the following from the 'Verify software versions' step in Section 1:
Patch 8796558* for R12 upgrades to 12.1.0.2 (12c)
Skip 'Database Installation in Section 1 and perform all steps in 'Database Upgrade':
Prior to upgrading the database in the 'Upgrade the database instance' section, you should ensure
that required environment variables are set by running the following (substituting the variables shown
in italics with acutal values):

$ source <12102_OH>/<SID>_<HOSTNAME>.env

All steps in 'After the Database Upgrade' except the following

Run adgrants.sql
Specific steps in the 'Implement and run Autoconfig' section of the Interoperability Notes such as
generating a new appsutil.zip on the database tier:
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=1ac33yw52w_57&id=1349240.1 3/13
10/8/2018 Document 1349240.1

If on 11i, MOS Note 165195.1 Section 8 Step 1 ('Copy AutoConfig to the

RDBMS_ORACLE_HOME')
If on R12, MOS Note 387859.1, Section 3.2 Steps 1, 2 and 3
Re-create custom database links (conditional)
Enable Database Vault (conditional)
Restart Applications server processes
Synchronize Workflow views (Note that this step must be completed after the 12.2.0 upgrade and
the application of the latest 12.2 RUP when all services are up as noted in the last step below)

*Note:
- Customers upgrading from R12 (12.0/12.1) and upgrading to 12cR1 as part of the 12.2 upgrade process
must apply particular EBS patches at the 12.0/12.1 level prior to upgrading to 12.2
- The patch 8796558 is not needed if the current EBS instance is 12.1 and has the 12.1.3+ Recommended
Patch Collection 4 [RPC4] applied.

Note (for Windows on 12cR1 only) :

After applying the patch 27440294 with the description "WINDOWS DB BUNDLE PATCH
12.1.0.2.180417(64bit):27440294" or later, perform the following before starting up the database:

1. Create a directory 'custom' in $ORACLE_HOME/appsutil/template directory.

2. Copy the afinit_db121.ora and afinit_db121RAC.ora templates into the custom directory.
3. Edit the afinit_db121.ora and afinit_db121RAC.ora templates in the custom directory to remove
optimizer_adaptive_features=false and replace with optimizer_adaptive_plans=false.
4. In order to use these templates for instantiating the init< SID
>.ora file on the instance, remove or rename
SID
the existing init< >.ora in $ORACLE_HOME/dbs directory and run AutoConfig to create a new init< SID
>.ora
file from the custom template.

3. Run post-install steps for Database Patches

The following steps should now be be performed:

a) Execute 'catmgd.sql' if upgrading from 11 : i

sqlplus / as sysdba

SQL> @?/rdbms/admin/catmgd.sql

b) Execute other post-install DB commands:

sqlplus / as sysdba
SQL> alter session set current_schema=SYS;
SQL> @?/rdbms/admin/dbmsxdbschmig.sql
SQL> @?/rdbms/admin/prvtxdbschmig.plb
SQL> @?/rdbms/admin/utlrp.sql

4. Apply Oracle Service Patch 5880762 (for 11i upgrades only)

Apply patch 5880762.

5. Check and Modify Initialization Parameters if necessary

Use the following sections in My Oracle Support Knowledge Document 396009.1 (' Database Initialization
Parameters for Oracle E-Business Suite Release 12
') as a guideline for the required modifications (as mentioned in
the Note box below) as well as for general best practices:

Section 1: Common Database Initialization Parameters for All Releases

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=1ac33yw52w_57&id=1349240.1 4/13
10/8/2018 Document 1349240.1

Section 5: Release-Specific Database Initialization Parameters for Oracle 12c Release 1

Section 6: Additional Database Initialization Parameters For Oracle E-Business Suite Release 12.2
Section 9: Database Initialization Parameter Sizing

Note:
If you encounter the error:

ORA-04030: out of process memory when trying to allocate 822904 bytes (pga heap, kco buffer)
ORA-07445: exception encountered: core dump [dbgtfdFileWrite()+48]
set the _pga_max_size initialization parameter to a larger value as follows: _pga_max_size=104857600
and restart your database.

Note (for AIX customers only):

If you encounter the error:

ORA-04030: out of process memory when trying to allocate 16416 bytes (callheap,kqlidpc)
ORA-04030: out of process memory when trying to allocate 169040 bytes (pga heap,kgh stack)
ORA-04030: out of process memory when trying to allocate 82456 bytes (pga heap,control file i/o buffer)
set the two initialization parameters below as follows:
_use_realfree_heap=TRUE
_realfree_heap_pagesize_hint = 262144

and restart your database.

Users should reset the above initialization parameters to their original state (or remove them if they did not
exist before) after the upgrade is completed.

Note (for Windows customers on 12cR1 only):

Due to a performance issue during the running of Readiness reports, it is recommended that the following
parameter be set prior to the 'Run the Online Patching Enablement - Readiness Reports' step (Step 4 of the
'Enabling Online Patching' section of the 'Oracle E-Business Suite Online Patching' chapter in the Upgrade
Guide) to the following value:

optimizer_dynamic_sampling=0

This parameter should then be removed so it reverts to its default value after this step is complete.

Note:
Set the parameter 'SEC_CASE_SENSITIVE_LOGON' to the value in the pre-upgrade database (as noted in Step
1 above).

Ensure that the sqlnet_ifile.ora has the following set if 'SEC_CASE_SENSITIVE_LOGON' is FALSE:
SQLNET.ALLOWED_LOGON_VERSION_SERVER = 8

If it is TRUE, then the parameter should be:

SQLNET.ALLOWED_LOGON_VERSION_SERVER = 10

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=1ac33yw52w_57&id=1349240.1 5/13
10/8/2018 Document 1349240.1

6. Continue and complete 12.2 upgrade

Perform the remaining steps in Chapter 4 ( 'Preparing for the Upgrade
') of the Upgrade Guide to complete the file
system installation using Rapid Install, and the later chapters of the Upgrade Guide to complete the upgrade to
12.2.

7. Apply latest 12.2 Release Update Pack (RUP) and complete remaining Database related steps
After completing the upgrade to 12.2.0, apply the latest 12.2 RUP - see Oracle E-Business Suite Release Notes,
Release 12.2 (My Oracle Support Knowledge Document 1320300.1).
After this, customers should perform the actions outlined above if relevant:
i
- For 11 upgrade customers, apply the patch 19007053
- Complete the 'Synchronize Workflow views' step as outlined in the Interoperability Notes
.

Path B: Customers on 11.5.10.2/12.0/12.1 with earlier DB or patchset versions of 10gR2 or 11g

This path follows the 12.2 upgrade path as documented in the Oracle E-Business Suite Upgrade Guide: Release 11i to
Release 12.2 and Oracle E-Business Suite Upgrade Guide: Release 12.0 and 12.1 to Release 12.2.
In Chapter 4 of the Oracle E-Business Suite Upgrade Guide, customers run Rapid Install to install the applications
technology stack which also includes a 12.1.0 Database Oracle Home. Customers will not use this Oracle Home for the
upgrade since customers will be using the Database Oracle Home created as part of the 11gR2 Interoperability Notes.
Customers should ensure that they pick the 'Use Existing Oracle Home' in the Database node configuration window of
Rapid Install and pick their existing database.

Systems in this category will be upgrading their databases to the latest patchset of 11gR2 (11.2.0.4) by using the process
documented in the 11gR2 Interoperability Notes
(see References section below).

Prior to running Rapid Install in Chapter 4 ('Performing the Upgrade') of the Upgrade Guide, apply database patches to the
existing 11g Oracle Home and perform all tasks documented in the patch readmes as noted below, before continuing with
installing the new application tier with Rapid Install and the standard R12 upgrade process.

Here are the steps:

1. Plan Upgrade to 12.2

Follow the 12.2 upgrade path as documented in the Oracle E-Business Suite Upgrade Guide: Release 11i to Release
12.2 Oracle E-Business Suite Upgrade Guide: Release 12.0 and 12.1 to Release 12.2
or . Perform all requirements
documented in Chapters 1, 2 and 3 and all applicable steps in Chapter 4 prior to running Rapid Install.

2. Upgrade to latest 11gR2 Database Patchset (11.2.0.4)

Customers currently on earlier versions of 10gR2, 11gR1 and 11gR2 should now upgrade to 11.2.0.4 as part of the
12.2 upgrade following the process documented in the appropriate 11gR2 Interoperability Notes (see References
section below) for 11gR2 (11.2.0).

Perform only the following in the appropriate Interoperability Notes to upgrade the Database to 11.2.0.4:
All steps in 'Database Installation' in Section 1
All steps in 'Database Upgrade' in Section 1 except
Perform patch post-install instructions
All steps in 'After the Database Upgrade' in Section 1 except the following
Apply post-upgrade ECX patch (upgrades from R12 only)
Apply Oracle Human Resources (HRMS) patch 7721754 (upgrades from 11 only) i
Enable Database Vault (conditional)
Restart Applications server processes
Synchronize Workflow views (Note that this step must be completed after the 12.2.0 upgrade and
the application of the latest 12.2 RUP when all services are up as noted in the last step below)

Under Section 1 of the Interoperability Notes, users should complete all steps listed in 'Database Installation' - in
place of the 'Apply additional 11.2.0.4 RDBMS patches', users should review Step 3 ('Apply Database Patches')
below to apply all required 11.2.0.4 patches following My Oracle Support Knowledge Document 1594274.1 ('Oracle
E-Business Suite Release 12.2: Consolidated List of Patches and Technology Bug Fixes'). These patches should be
applied before upgrading the Database to 11.2.0.4 in the 'Database Upgrade' steps of the Interoperabilty Notes.

3. Apply Database Patches

Before performing the step 'Run Rapid Install' in the 'Performing the Upgrade' section of Chapter 4 of the Upgrade
Guide, users who have not already applied the Database patches in Step 2 above should do so now.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=1ac33yw52w_57&id=1349240.1 6/13
10/8/2018 Document 1349240.1

Note: While not mandatory for the interoperability of Oracle E-Business Suite with the Oracle Database,
customers may apply Database Patch Set Updates (PSUs) on their Oracle E-Business Suite Database prior to
or as part of a 12.2 upgrade.
Customers who have not applied the PSU and wish to do so as part of their 12.2 upgrade should apply the
PSU after the database patches listed below.
Customers should review ' Database Patch Set Update Overlay Patches Required for Use with PSUs and Oracle
E-Business Suite ' (My Oracle Support Knowledge Document 1147107.1) for information on patches required
for conflict resolution.

Note: When using the current version of OPatch (11.2.0.3.3) to patch a RAC-enabled Oracle Database on a
shared file system, there is a current known issue that will lead to patch application failure.
To work around the issue, users who have RAC-enabled databases on a shared file system should run OPatch
with the '-local' option (described in the OPatch documentation).

Before performing the next step, review My Oracle Support Knowledge Document 1594274.1 (' Oracle E-Business
Suite Release 12.2: Consolidated List of Patches and Technology Bug Fixes
') and apply all relevant patches for
Oracle Database 11.2.0.4 listed in Section 2, Table 1 of the document.

4. Run post-install steps for Database Patches

Note: Some of the individual patches listed below (4247037, 17420796, 17629476, 16989137) are included in
the 11.2.0.4 n-apply bundle patch 20523280 as documented in ' Oracle E-Business Suite Release 12.2:
Consolidated List of Patches and Technology Bug Fixes' (My Oracle Support Knowledge Document 1594274.1).

In addition to performing all the post install steps mentioned in the READMEs of patches listed in the document in
Step 3, additional post install steps for the following patches need to be performed:

a) 4247037 - Run @catmgdidcode

b) 17629476

For Unix, run the post install instructions for the patch.

For Windows, run the following:

$ sqlplus / as sysdba
SQL> alter session set current_schema=SYS;
SQL> @?/rdbms/admin/dbmsobj.sql
SQL> @?/rdbms/admin/dbmsxdbschmig.sql
SQL> @?/rdbms/admin/prvtxdbschmig.plb

c) 16989137 - run the following:

$ sqlplus / as sysdba
SQL> @?/sqlpatch/16989137/postinstall.sql

d) Perform DST upgrade steps as outlined in Steps 3 and 4 of the My Oracle Support Knowledge Document
977512.1 (' Updating the RDBMS DST version in 11g Release 2 (11.2.0.1 and up) using DBMS_DST ') due to the
inclusion of the DST patch v18 (13417321) or later in 11.2.0.4.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=1ac33yw52w_57&id=1349240.1 7/13
10/8/2018 Document 1349240.1

5. Apply Oracle Service Patch 5880762 (for 11i upgrades only)

Apply patch 5880762.

6. Check and Modify Initialization Parameters if necessary

Use the following sections in My Oracle Support Knowledge Document 396009.1 (' Database Initialization
Parameters for Oracle E-Business Suite Release 12
') as a guideline for the required modifications (as mentioned in
the Note box below) as well as for general best practices:

Section 1: Common Database Initialization Parameters for All Releases

Section 4: Release-Specific Database Initialization Parameters for Oracle 11g Release 2
Section 6: Additional Database Initialization Parameters For Oracle E-Business Suite Release 12.2
Section 9: Database Initialization Parameter Sizing

Note:
If you encounter the error:

ORA-04030: out of process memory when trying to allocate 822904 bytes (pga heap, kco buffer)
ORA-07445: exception encountered: core dump [dbgtfdFileWrite()+48]
set the _pga_max_size initialization parameter to a larger value as follows: _pga_max_size=104857600
and restart your database.

Note (for AIX customers only):

If you encounter the error:

ORA-04030: out of process memory when trying to allocate 16416 bytes (callheap,kqlidpc)
ORA-04030: out of process memory when trying to allocate 169040 bytes (pga heap,kgh stack)
ORA-04030: out of process memory when trying to allocate 82456 bytes (pga heap,control file i/o buffer)
set the two initialization parameters below as follows:
_use_realfree_heap=TRUE
_realfree_heap_pagesize_hint = 262144

and restart your database.

Users should reset the above initialization parameters to their original state (or remove them if they did not
exist before) after the upgrade is completed.

7. Continue and complete 12.2 upgrade

Perform the remaining steps in Chapter 4 ( 'Performing the Upgrade
') of the Upgrade Guide to complete the file
system installation using Rapid Install and the later chapters of the Upgrade Guide to complete the upgrade to
12.2.

8. Apply latest 12.2 Release Update Pack (RUP) and complete remaining Database related steps
After completing the upgrade to 12.2.0, apply the latest 12.2 RUP - see Oracle E-Business Suite Release Notes,
Release 12.2 (My Oracle Support Knowledge Document 1320300.1).
After this, customers should perform the actions outlined above if relevant:
- Users should complete the 'Synchronize Workflow views' step as outlined in the . Interoperability Notes
Path C: Customers on 11.5.10.2/12.0/12.1 on the latest 11gR2 or 12cR1 patchset (11.2.0.4 or 12.1.0.2)

This path follows the 12.2 upgrade path as documented in the Oracle E-Business Suite Upgrade Guide: Release 11i to
Release 12.2 and Oracle E-Business Suite Upgrade Guide: Release 12.0 and 12.1 to Release 12.2.
In Chapter 4 of the Oracle E-Business Suite Upgrade Guide, customers run Rapid Install to install the applications
technology stack which also includes a 12.1.0 Database Oracle Home. Customers will not use this Oracle Home for the
upgrade since customers would already have upgraded to 11.2.0 or 12.1.0 prior to doing the R12 upgrade and would be

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=1ac33yw52w_57&id=1349240.1 8/13
10/8/2018 Document 1349240.1

using their existing Database Oracle Home. Customers should ensure that they pick the 'Use Existing Oracle Home' in the
Database node configuration window of Rapid Install and pick their existing database.

Systems in this category have databases already upgraded to 11.2.0.4 or 12.1.0.2 by using the process documented in the
Interoperability Notes(see References section below).

Prior to running Rapid Install in Chapter 4 ('Performing the Upgrade') of the Upgrade Guide, apply database patches to the
existing 11g or 12c Oracle Home and perform all tasks documented in the patch readmes as noted below, before
continuing with installing the new application tier with Rapid Install and the standard R12 upgrade process.

Here are the steps:

1. Plan Upgrade to 12.2

Follow the standard 12.2 upgrade path as documented in the Oracle E-Business Suite Upgrade Guide: Release 11i
to Release 12.2 Oracle E-Business Suite Upgrade Guide: Release 12.0 and 12.1 to Release 12.2
or . Perform all
requirements documented in Chapters 1, 2 and 3 and all applicable steps in Chapter 4 prior to running Rapid
Install.

2. Pre-upgrade Database checks

Customers who have upgraded to 11.2.0.4 or 12.1.0.2 prior to the 12.2 upgrade followed the process documented
in the appropriate Interoperability Notes (see References section below) and should ensure they have all pre-
requisites and interoperability patches applied to their Database.

3. Apply Database Patches

Before performing the step 'Run Rapid Install' in the 'Performing the Upgrade' section of Chapter 4 of the Upgrade
Guide, users who have not already applied the Database patches in Step 2 above should do so now.

Note: While not mandatory for the interoperability of Oracle E-Business Suite with the Oracle Database,
customers may apply Database Patch Set Updates (PSUs) on their Oracle E-Business Suite Database prior to
or as part of a 12.2 upgrade.
Customers who have not applied the PSU and wish to do so as part of their 12.2 upgrade should apply the
PSU after the database patches listed below.
Customers should review ' Database Patch Set Update Overlay Patches Required for Use with PSUs and Oracle
E-Business Suite ' (My Oracle Support Knowledge Document 1147107.1) for information on patches required
for conflict resolution.

Note: When using the current version of OPatch (11.2.0.3.3) to patch a RAC-enabled Oracle Database on a
shared file system, there is a current known issue that will lead to patch application failure.
To work around the issue, users who have RAC-enabled databases on a shared file system should run OPatch
with the '-local' option (described in the OPatch documentation).

Before performing the next step, review My Oracle Support Knowledge Document 1594274.1 (' Oracle E-Business
Suite Release 12.2: Consolidated List of Patches and Technology Bug Fixes ') and apply all relevant patches for
Oracle Database 11.2.0.4 or 12.1.0.2 listed in Section 2, Table 1 of the document.

4. Run post-install steps for Database Patches

Attention: With Oracle Database 12cR1, several patches may require running DATAPATCH which needs to be
done only once.

Note: Some of the individual patches listed below (4247037, 17420796, 17629476, 16989137) are included in
the 11.2.0.4 n-apply bundle patch 20523280 as documented in ' Oracle E-Business Suite Release 12.2:
Consolidated List of Patches and Technology Bug Fixes' (My Oracle Support Knowledge Document 1594274.1).

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=1ac33yw52w_57&id=1349240.1 9/13
10/8/2018 Document 1349240.1

In addition to performing all the post install steps mentioned in the READMEs of patches listed in the document in
Step 3, additional post install steps for the following patches need to be performed:

a) 4247037 (for customers on 11.2.0.4 only) - Run @catmgdidcode

b) 17420796 which is superceded by 21249127 (for customers on 11.2.0.4 only), run the command:

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

c) Perform the following steps (for customers on 12.1.0.2):

- run dbmsxdbschmig.sql, prvtxdbschmig.sql, utlrp.sql scripts:

sqlplus / as sysdba
SQL> alter session set current_schema=SYS;
SQL> @?/rdbms/admin/dbmsxdbschmig.sql
SQL> @?/rdbms/admin/prvtxdbschmig.plb
SQL> @?/rdbms/admin/utlrp.sql

- run adgrants.sql:

sqlplus / as sysdba

SQL> @?/rdbms/admin/adgrants.sql [APPS schema name]

i
d) Customers upgrading from 11 with 12cR1 to 12.2 should do the following:

sqlplus / as sysdba

SQL> @?/rdbms/admin/catmgd.sql

These customers should also apply the patch 19007053 after upgrading to 12.2.0 and the latest available 12.2 RUP
as noted in the last step below. .

e) If not already done so, perform DST upgrade steps as outlined in Steps 3 and 4 of the My Oracle Support
Knowledge Document 977512.1 (' Updating the RDBMS DST version in 11g Release 2 (11.2.0.1 and up) using
DBMS_DST ') due to the inclusion of the DST patch v18 (13417321) or later in 11.2.0.4.

5. Check and Modify Initialization Parameters if necessary

Use the following sections in My Oracle Support Knowledge Document 396009.1 (' Database Initialization
Parameters for Oracle E-Business Suite Release 12
') as a guideline for the required modifications (as mentioned in
the Note box below) as well as for general best practices:

Section 1: Common Database Initialization Parameters for All Releases

Section 4: Release-Specific Database Initialization Parameters for Oracle 11g Release 2 or Section 5: Release-
Specific Database Initialization Parameters for Oracle 12c Release 1
Section 6: Additional Database Initialization Parameters For Oracle E-Business Suite Release 12.2
Section 9: Database Initialization Parameter Sizing

Note:
If you encounter the error:

ORA-04030: out of process memory when trying to allocate 822904 bytes (pga heap, kco buffer)
ORA-07445: exception encountered: core dump [dbgtfdFileWrite()+48]

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=1ac33yw52w_57&id=1349240.1 10/13
10/8/2018 Document 1349240.1

set the _pga_max_size initialization parameter to a larger value as follows: _pga_max_size=104857600

and restart your database.

Note (for AIX customers only):

If you encounter the error:

ORA-04030: out of process memory when trying to allocate 16416 bytes (callheap,kqlidpc)
ORA-04030: out of process memory when trying to allocate 169040 bytes (pga heap,kgh stack)
ORA-04030: out of process memory when trying to allocate 82456 bytes (pga heap,control file i/o buffer)
set the two initialization parameters below as follows:
_use_realfree_heap=TRUE
_realfree_heap_pagesize_hint = 262144

and restart your database.

Users should reset the above initialization parameters to their original state (or remove them if they did not
exist before) after the upgrade is completed.

Note (for Windows customers on 12cR1 only):

Due to a performance issue during the running of Readiness reports, it is recommended that the following
parameter be set prior to the 'Run the Online Patching Enablement - Readiness Reports' step (Step 4 of the
'Enabling Online Patching' section of the 'Oracle E-Business Suite Online Patching' chapter in the Upgrade
Guide) to the following value:

optimizer_dynamic_sampling=0

This parameter should then be removed so it reverts to its default value after this step is complete.

6. Continue and complete 12.2 upgrade

Perform the remaining steps in Chapter 4 ( 'Performing the Upgrade
') of the Upgrade Guide to complete the file
system installation using Rapid Install and the later chapters of the Upgrade Guide to complete the upgrade to
12.2.

7. Apply latest 12.2 Release Update Pack (RUP) and complete remaining Database related steps
After completing the upgrade to 12.2.0, apply the latest 12.2 RUP - see Oracle E-Business Suite Release Notes,
Release 12.2 (My Oracle Support Knowledge Document 1320300.1).
After this, customers should perform the actions outlined above if relevant:
i
- If upgrading from 11 with 12cR1 to 12.2, users should apply the patch 19007053

References
Oracle E-Business Suite Release Notes, Release 12.2 (My Oracle Support Knowledge Document 1320300.1)
Oracle E-Business Suite Upgrade Guide: Release 11i to Release 12.2 (HTML, PDF from the 12.2 Documentation
Web Library)
Oracle E-Business Suite Upgrade Guide: Release 12.0 and 12.1 to Release 12.2 (HTML, PDF from the 12.2
Documentation Web Library)
Interoperability Notes: Oracle Applications Release 11i with Oracle Database 11g Release 2 (11.2.0) (My Oracle
Support Knowledge Document 881505.1)
Interoperability Notes: Oracle E-Business Suite Release 12 with Oracle Database 11g Release 2 (11.2.0) (My Oracle
Support Knowledge Document 1058763.1)
Interoperability Notes: Oracle E-Business Suite Release 11i with Oracle Database 12c Release 1 (12.1.0) (My Oracle
Support Knowledge Document 1524399.1)

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=1ac33yw52w_57&id=1349240.1 11/13
10/8/2018 Document 1349240.1

Interoperability Notes: Oracle E-Business Suite Release 12.0 or 12.1 with Oracle Database 12c Release 1 (12.1.0)
(My Oracle Support Knowledge Document 1524398.1)
Database Patch Set Update Overlay Patches Required for Use with PSUs and Oracle E-Business Suite (My Oracle
Support Knowledge Document 1147107.1)
Oracle E-Business Suite Release 12.2: Consolidated List of Patches and Technology Bug Fixes ( My Oracle Support
Knowledge Document 1594274.1)

Change Log

Date Description

05-Oct-2018 Changes for 12.2.8

08-Sep-2017 Changes for 12.2.7 (pertaining to Upgrade Guide changes)

15-May-2017 Changes to DST patch reference (to 13417321) and changes to Windows 12cR1 Note box

22-Aug-2016 Changes as part of 12.2.6

18-Feb-2016 Changes needed for release of startCD 51 (repackaging of 12.1.0.2 with RI)

Added recommendation for Windows 12cR1 upgrades to set a parameter before running readiness
28-Oct-2015
reports.

Removed old Path A (installing EBS 11.2.0.3 from 12.2 RI) and other changes as part of 12.2.5
25-Sep-2015
release; added recommendation for RAC upgrades to be done on a single node (doc bug 21563751)

Removed instruction 'Run adgrants.sql' in these instructions since it is now a general

recommendation doc'ed in MOS Note 1594274.1
16-Jun-2015
Added Note in Path B regarding the inclusion of particular patches in the 11.2.0.4 n-apply bundle
patch 20523280 referenced in MOS Note 1594274.1

Added post 12.2.0 upgrade step, and other relevant info for actions to be done after applying the
07-May-2015
latest 12.2 RUP

20-Apr-2015 Further refinements to details in Path B for 11i upgrades, etc.

Recommendation for going to latest patchsets (11.2.0.4, 12.1.0.2) and de-emphasizing Path A given
13-Apr-2015
11.2.0.3 ECS policy.

17-Feb-2015 Added patch 8796558 to Path B for 12c upgrades

10-Feb-2015 Changes in Path B Step 2 for 11i/12.0 certification with 12.1.0.2 (steps that cannot be skipped)

12.1.0.2 certification changes added. With the release of startCD 49, removed reference to 48 and
07-Jan-2015
added language that the latest available version is recommended and to check the Release Notes.

18-Sep-2014 Added DB 12c (12.1.0.1)

17-Jun-2014 Fixed current startCD number

16-Jun-2014 Changes resulting from 11204 on Linux on System z announcement (instructions for 16989137)

02-Jun-2014 Added instructions for upgrade to 11204 as part of Path B; changes for 11204 Windows certification.
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=1ac33yw52w_57&id=1349240.1 12/13
10/8/2018 Document 1349240.1

09-Apr-2014 Replaced 17502060 with 17693770

26-Feb-2014 Added support for 11204 upgrades

07-Feb-2014 Added Windows specific changes

Added note to review the 11203 DB patches for Path A as well since there could be additional
28-Jan-2014 patches required, while changing the wording for these instructions in Path B as well. Clarified that
startCD 46 is supported, with the latest being recommended.

In Upgrade Path B, Step 2, Apply Database Patches, changed:

Apply the 11.2.0.3 Database patches listed in Section 1 of 'Oracle E-Business Suite Release 12.2:
Consolidated List of Patches and Technology Bug Fixes' (My Oracle Support Knowledge Document
1594274.1).
18-Dec-2013
to:

Apply the 11.2.0.3 Database patches listed in Section 2, Table 1 of 'Oracle E-Business Suite Release
12.2: Consolidated List of Patches and Technology Bug Fixes' (My Oracle Support Knowledge
Document 1594274.1).

For 12.2.3 release, replaced list of DB patches in Path B with a pointer to the MOS Note 1594274.1
13-Dec-2013 and removed/updated patches listed in Path A that have been included in startCD 47. Added AIX
only init parameters Note to Path B.

14-Oct-2013 Replaced 16702016 with 17468141

08-Oct-2013 Added reference to the PSU Overlay with EBS MOS Note 1147107.1

19-Sep-2013 Initial release for 12.2 GA

My Oracle Support Knowledge Document 1349240.1 by Oracle E-Business Suite Development

Copyright © 2013, 2018 Oracle and/or its affiliates. All rights reserved.

Didn't find what you are looking for?

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=1ac33yw52w_57&id=1349240.1 13/13