Upgrading Oracle EBS to Release 12.2

Upgrading Oracle EBS to Release 12.2?  what we should keep in mind !


There is always a generic question that arises: “Our current EBS release is stable and running without any issues. Why should we upgrade to a newer release?” Software development is a continuous process, and we need to align with current and future information technology trends. We need to ensure we are moving forward and ready to accept these changes. Moreover, Oracle stopped development on the release 12.1.3, and all future enhancements are focused on the 12.2 release.

In this scenario there is a huge requirement of Upgrade to the latest versions (R12.2). Oracle, no doubt  adopted latest technology and moves to give the best in industry and so on the  Oracle Application side. Latest version on Oracle application is 12.2.6

The below points gives the high level overview of upgrade to R12.2 from the lower versions. Let’s start with Tech stack versions

Application Server


Any upgrade to R12.2 goes through below  phases

Plan for Upgrade – Better plan is surety of success most of the time. We need to
plan and also document all the issues reported so that during the Final
Production upgrade downtime can be minimal. We need to plan and check all the
intermediate version are supported if not operational. That is the key point
during the planning. Follow the best practices for minimizing the upgrade
downtime suggested by Oracle and also as per the client and DBA experiences.

Prepare for Upgrade– This phase starts after the planning phase and includes Database
and Application preparation for upgrade activity. This is the main upgrade
phase where we perform all the upgrade activities
Database Upgrade – Select the latest version for database. If 11g database,
consider for version or 12c version is highly recommended. Also
apply the latest Consolidate patches as per the database versions. On the
application side we need to be on the Minimum base line patches as per the Oracle
File System Lay down – As we know R12.2 comes with latest technology and file system, so
we need to lay down the R12.2 file system using the latest startCD.
Upgrade to 12.2.0  – We need to first upgrade to 12.2.0 and need to apply AD
and TXK patches on the 12.2 filesystem. As this is the intermediate stage we
need to perform it as preinstall activity. At this stage Application
will not be operational.
Enable Online Patching – As you know new feature of R12.2 is online patching so we
need to enable our old instance for the same. This is bit time
consuming activity and we need to follow the Online Patching Readiness
document 1531121.1 from MOS. 

This phase fixes:
Any Coding Violation
Enable edition of Application and or any custom schema.
Generate edition views and column
further to 12.2.X
– We are at 12.2 with latest database now. Now on the
application side we can come to the 12.2.5 version. We need to apply
the latest technology patches (Delta 7) and EBS RUP patches after that.

Middle Tier patches >1594274.1
AD-TXK RUP patches >1617461.1 
EBS R12.2.X Document >12.2.4 or 12.2.5
All the post upgrade patches and steps.

Oracle always recommends to
apply the latest technology patches, the newest version includes the maximum
no. of bug fixes and newest enhancements. Technology(AD/TXK) patches are
regularly updated in MOS Doc ID:1583092.1.


Translations – In case multiple
languages are there then we need to take care of Translation patches
as well. 12.2 and then 12.2.X translated patches and also we need to apply
TSP (Translation Sync Patches).
Customization – Once standard/seeded
code is at R12.2.X level we need to take care of the customization’s in our old
versions. For R12.2 we have new development standards and need to follow
the same to get the custom code compliant with our applications.


Planning Your Oracle E-Business Suite (EBS) Upgrade from Release 11i to Release 12 (1406960.1)
Best Practices for Minimizing Oracle E-Business suite Release 12 Upgrade Downtime (1581549.1)
Developing and Deploying customization’s(157766.1)
Happy EBS Upgrading..

  • March 23, 2017 | 14 views
  • Comments