How to Upgrade R12.1.3 to R12.2

What’s coming in Oracle E-Business Suite 12.2?


I will try to analyze architectural overview of the latest updates, installation and upgrade options, new configuration options, and new tools for hot-cloning and automated “lights out” cloning in R-12.2

Oracle E-Business Suite 12.1 Architecture





Oracle E-Business Suite 12.2 Architecture

Release 12.2 will replace Oracle Containers for Java (OC4J) 

10g with WebLogic Server 11g

Release 12.2 Database tier will run RDBMS 11gR2 to 

support online patching.





There will be number of updates coming in release R12.2, from a technology stack perspective, EBS 12.2 will be notable for two things:
1-Replacing Oracle Containers for Java (OC4J) 10g with WebLogic Server 11g
EBS 12.2 will use WebLogic Server from Fusion Middleware 11g in place of OC4J 10g as part of the release’s internal technology stack. Other additional new Fusion Middleware 11g components used will include WebLogic JSP and UIX 11g 

2-Online Patching support via 11gR2 Edition-Based Redefinition. EBS 12.2 will use the 11gR2 Database’s Edition-Based Redefinition features to provide support for Online Patching. Edition-Based Redefinition is really exciting new technology.


Upgrade R12.1.3 to R12.2 Steps:


1. List of recommended pre-upgrade activities:-


• Purge all old data that is no longer needed prior to the upgrade.
• Flush all the interfaces, such as Auto Invoice, Journal Entry Import, Order Import etc.
• Drop MRC Schema if it still exists.
• Gather the schema statistics (with GATHER_AUTO option for all schemas) close to the start of the downtime. Use FND_STATS or Gather Statistics concurrent programs.

• Gather Fixed Object and Dictionary Statistics.



Purge old data:-

Purge all old data that is no longer needed prior to the upgrade.
This can be quite a lengthy process, and you may need to resolve issues around performance, execution frequency and the periods to be purged in each execution. So this should be started as soon as possible.
There are over 100 standard purge programs in 11i. You can use OAM to administrate, configure, initiate and monitor purge programs.

System Administrator >Oracle Applications Manager >Purging/Critical Activities.


Purge interface data


Flush all the interfaces, such as Auto invoice, Journal entry import, and order import.



Fixed Object and Dictionary Statistics

These should have been gathered and be correct/up to date on the pre-upgrade environment.

Drop MRC Schema

All programs and reports now use the APPS schema. The MRC_APPS schema is no longer needed, so dropping it frees space and reduces processing overhead during the upgrade.
You can drop this schema prior to the Release 12 upgrade if it still exists. It should have already been removed on upgrade to 11.5.10.



Removing Unnecessary Workloads / Overheads

To reduce the workload you should do the following:

• Disable any custom triggers and business events.
• Disable auditing if enabled. The “Oracle E-Business Suite Upgrade Guide” states that the Oracle AOL Audit Trail should be disabled before upgrade, anyway.
• Review and disable all debug and logging that has been enabled using profiles. Do this at all levels (e.g. site, responsibility, user level.).
• If possible, run in noarchivelog mode.
• Disable flashback DB.
• Remove TDE (Transparent Data Encryption) from high volume tables.
• Consider running AutoConfig in parallel on a multi-node system.


Use TUMS (The Upgrade Manual Script)
 to avoid running tasks not relevant to your system
The TUMS report lists tasks that you can omit from the upgrade because they do not apply to your system (for example, a task required for a product that you do not use or a patch that you have previously applied). TUMS is delivered in a patch (7705743), which supplies the scripts you need to examine your system and create the report. We strongly recommend you create and review the TUMS report before you begin the upgrade.
Download and apply patch 7705743, then run the script adtums.sql to generate the report tumsr12.html.


The tumsr12.htm report lists the steps (identified by the TUMS step key in this book) that do not apply to your installation. You may safely ignore any steps listed in this report.