Oracle has announced on March 2021, they are following a “Continuous Innovation” release model for Oracle E-Business Suite 12.2, delivering ongoing applications and underlying technology stack updates for 12.2 without requiring a major upgrade. As well, 12.2 is the long-term support release for Oracle E-Business Suite, with Premier Support for 12.2 available through at least 2032, and there will be no 12.3 release.
This post covers a high-level overview of :
- Why Upgrade to EBS R12.2
- Why Upgrade to Database 19c
- Thing You Must Learn Before the EBS Upgrade
- EBS Upgrade Paths
- Upgrade High-level Steps
- Post Upgrade Steps
- FAQs
Why Upgrade To EBS R12.2? ^
- EBS 12.0 and 11.5.10 are in sustaining support.
- Oracle Apps DBA is in great demand and with 12.2 experience
- Good Salary if you know 12.2 as 11i & 12.0 out of support
- Customers on R12.1 are also looking to upgrade to R12.2 to take advantage of the Online Patching feature
Also Check: How To Install Oracle E-Business Suite R12.2
Why Upgrade To Database 19c? ^
- Oracle has already de-supported Oracle Database 11.2.0.4 on Dec 31 2020. (To know more, click here (Doc ID 2522948.1))
- Oracle Database 12.1.0.2/12.1.0.2 Extended Support Waived Only Till July 31, 2022(To know more click here)
- All Customers Should Upgrade Their Database By Then To Avoid Extra Cost
- At The Moment Only EBS R12.1.3 & R12.2.3+ Is Supported
- Support For R12.0 And 11i Is Expected On A Later Date
To know more about the Database upgrade 19c, check our post Here
Thing You Must Learn Before The EBS R12.2 Upgrade ^
EBS Architecture Concepts:
It is a three-tier architecture:
- Client Tier
- Application Tier
- Database Tier
To know more about the EBS Architecture, click HERE
Fusion Middleware: WLS & OHS:
- Software layer that lies between business application and database
- Infrastructure which facilitates the creation of business applications
- Includes Web Servers, Application Servers, Content Management, Identity Management, SOA, Business Intelligence
- Oracle EBS R12.2 uses WebLogic & OHS from FMW
Check out: What all operating systems are supported by the Oracle E-Business Suite (EBS) R12.2.
R12.2 File System:
- R12.2 has a dual File system.
- Run File system and Patch File system and are identical.
To learn more about the EBS File System, check our post HERE
Patching In EBS R12.2:
- In 12.2 all patching operations are online
- EBS will remain available to users during patching operations
To know more about patching, check our post HERE
EBR (Edition Based Redefinition):
- Edition-based redefinition allows multiple versions of PL/SQL objects, views, and synonyms in a single schema, which makes it possible to perform upgrades of database applications with zero downtime.
- Edition-based redefinition is a single technology that provides high availability during upgrades.
- 12.2 Uses Edition Based Redefinition to Support Online Patching (ADOP)
- Check Customizations Support 12.2 Development
- During Online Patching conversion make existing code compatible for EBR
Also read: Upgrading your EBS base version to R12.2 can be quite a complicated task. Make it simpler with the free diagnostic tool called analyzers for Oracle E-Business Suite 12.2, 12.1, 12.0, and 11i.
EBS Upgrade Paths ^
You can upgrade directly to EBS R12.2 from the following base versions:
- EBS 11i
- EBS 12.0
- EBS 12.1
Upgrade High-level Steps
1. Preparation (Lay Down 12c & R12.2) no downtime
- Plan & Prepare for Upgrade – 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 versions are supported if not operational. That is the key point during planning.
- 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
2. Apply Latest CUP+other performance patches – no downtime
3. Online Clone Database + Upgrade to 12c
- Database Upgrade – Select the latest version for the database. If 11g database, consider for 11.2.0.4 version or you can plan for 12c versions too. Also, apply the latest Consolidate patches as per the database versions. On the application side, we need to be on the Minimum baseline patches as per the Oracle recommendations.
- File System Lay down- As we know R12.2 comes with the latest technology and file-system, so we need to lay down the R12.2 file-system using the latest startCD. Currently, StartCD 51 is available.
4. 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 filesystems. As this is the intermediate stage we need to perform it as a pre-install activity. At this stage, the Application will not be operational.
5. Upgrade further to 12.2.X- We are at 12.2 with the latest database now. Now on the application side, we can come to the latest version (12.2.10 Currently). We need to apply the latest technology patches (Delta 12 till now) and EBS RUP patches after that.
- Middle Tier patches -> 1594274.1
- AD-TXK RUP patches -> 1617461.1
- EBS R12.2.X Document -> 12.2.9 or 12.2.10
- All the post-upgrade patches and steps
6. Apply Post – Upgrade Patch –
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. (MOS ID: 1531121.1)
7. Deploy Customization & External Integration
- Translations – In the case of 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 customizations 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.
8. Configuration:
- Check the Sizing’s
- Add Nodes for Horizontal Scale-up
- Add Managed Servers for Vertical Scale-up
Post – Upgrade Tasks ^
After the successful upgrade of your base version R12.1 to the version R12.2 or R12.2.x, you need to perform post-upgrade tasks which ensures the stability of the system and it includes:
- Minimize Downtime: MOS ID 1581549.1 Best Practices for Minimizing Oracle E-Business Suite Release 12 Upgrade Downtime
- Best Practices & Performance: MOS ID 1581549.1 Best Practices for Minimizing Oracle E-Business Suite Release 12 Upgrade Downtime
- Troubleshooting & Logs
FAQs ^
Q1. What’s the latest version of Oracle EBS?
Ans. EBS 12.2. 10 is Oracle’s most recent iteration of the E-Business Suite collection of software applications for enterprise resource planning, customer relationship management, and supply chain management. The previous version, EBS 12.2. 9, was released in August 2019.
Q2. How to check the EBS version?
Ans. You can use a simple SQLPlus query to find the version of Oracle E-Business Suite. Recently the latest Oracle EBS version R12. 2.10 has been released to download as a patch. If you are planning for EBS Oracle Applications upgrade and patching, then you must check the version of Oracle Apps R12 before the upgrade.
SELECT RELEASE_NAME FROM APPS.FND_PRODUCT_GROUPS;
Q3. What is new in 19c?
Ans.
- Automatic Indexing.
- SQL Diagnostics and Repair Enhancements.
- Bitmap Based Count Distinct SQL Function.
- Big Data and Performance Enhancements for In-Memory External Tables.
- Automatic SQL Plan Management.
- Real-Time Statistics.
- High-Frequency Automatic Optimizer Statistics Collection.
- Hybrid Partitioned Tables.
Q4. What is the difference between 11g and 12c in Oracle?
Ans. The main difference between Oracle 11g and 12c is that the Oracle 11g is an older version of Oracle RDBMS and has no pluggable databases while Oracle 12c is a newer version designed for the cloud and has pluggable databases. In other words, these systems use a relational model to store data
Related Further Readings
- [1Z0-238] Oracle EBS R12 Certified Specialist Everything You Must Know About
- 19c Database In Oracle EBS R12: Everything You Must Know
- Steps to Download Oracle EBS R12 Software from edelivery site
- Oracle E-Business Suite (EBS) 12.2.9 Now Available & Its Upgrade Steps
- MOS ID 1581549.1 Best Practices for Minimizing Oracle E-Business Suite Release 12 Upgrade Downtime
- Using Wget To Download Software/Patches From Oracle Support
- ADOP ( R12.2 Online Patching ) in Oracle EBS (R12) FAQ
- Release Schedule of Current Database Releases (Doc ID 742060.1)
- Quarterly EBS Upgrade Recommendations: May 2021 Edition
- EBS Certifications
Next Task For You
We cover Oracle E-Business R12.2 Architecture & concepts in our Oracle Apps DBA For Beginners Training along with the Installation, Patching, Cloning, and Troubleshooting and also, Database upgrade to 19c and much more including the hands-on labs you must perform to upgrade your skills and get a good job with a high package.
Begin your journey towards becoming an Apps DBA by joining our FREE Masterclass on How To Learn Oracle Apps DBA (R12) & It’s New Features.
Sanjay Desai says
Dear Sir/Madam,
We have currently oracle EBS R12.1.3. we have lots of personalizations and customizations in oracle forms.
we are planning to upgrade our EBS to R12.2.10.
I heard that all the forms in R12.2.10 are converted to JSP pages. Is it correct?
After upgradation to R12.2.10, can I still get access to forms like R12.1.3?
because we have lots of personalization?
All the personalizations will work/retro-fitted directly after upgrdation?
Please give your valuable advice?
Regards
Sanjay
Varsha Sharma Sharma says
Hi Sanjay,
First of all, R12.2 still has forms similar to R12.1.3, most of the personalizations will work like in R12.1.3, some might need redevelopment if not compatible with R12.2 object structures which will be done by forms developers.
Regards
Varsha
K21Academy
Creative says
Hello
Thank You for providing detailed instructions with followup steps.
I have a followup question on below:
“Customization – Once standard/seeded code is at R12.2.X level we need to take care of the customizations 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.“
Can you pls elaborate on this statement: “ we need to take care of the customizations in our old versions. ”?
Prabhu says
Dear Sir/Madam,
We are planning to upgrade our EBS to R12.2.10. We have currently oracle EBS R12.1.3. we have many custom RDF Reports. Will these reports work in 12.2.10. If not can you please suggest.
Rahul Dangayach says
Hi Prabhu,
There is a possibility that some of your custom RDF Reports may not work in EBS R12.2.10, as there may be some changes in the technology stack and architecture between the two versions that could impact the functionality of your reports. However, it’s difficult to say for certain without knowing the specific details of your custom RDF Reports and the changes in the upgrade.
To determine if your custom RDF Reports will work in EBS R12.2.10, you should perform a thorough analysis and testing of your reports in a test environment running the new version of EBS. This will help you identify any compatibility issues and allow you to make any necessary adjustments to ensure that your reports function correctly in the upgraded environment.
If you do encounter issues with your custom RDF Reports, you may need to update or modify them to make them compatible with EBS R12.2.10. This may involve working with your development team or engaging with a third-party vendor to help you make the necessary changes.
It’s worth noting that Oracle provides documentation and tools to help customers with the upgrade process, including upgrade guides, patch recommendations, and certification matrices that outline the supported versions of various components. So, be sure to review this information and work closely with Oracle support and any third-party vendors to ensure a smooth and successful upgrade.
Hope this helps.
Thanks and Regards
Rahul Dangayach
Team K21Academy
Leo Caipei Chen says
what is the “For R12.2 we have new development standards and need to follow the same to get the custom code compliant with our applications.” could you plz more tetail?
Rahul Dangayach says
Hi Leo,
The statement “For R12.2 we have new development standards and need to follow the same to get the custom code compliant with our applications” refers to the new set of development standards that Oracle introduced in Oracle E-Business Suite (EBS) Release 12.2. These standards are designed to improve the quality, maintainability, and portability of custom code in EBS.
Some of the key changes in the R12.2 development standards include:
* The use of version control systems to track changes to custom code.
* The writing of unit tests to ensure that custom code works as expected.
* The documentation of custom code to make it easier to understand and maintain.
* The use of coding standards to ensure that custom code is consistent and easy to read.
These new standards are important for several reasons. First, they help to ensure that custom code is compliant with the latest Oracle technologies. Second, they help to improve the quality and maintainability of custom code. Third, they make it easier to upgrade custom code to new versions of EBS.
If you have custom code in EBS that is not compliant with the R12.2 development standards, you will need to update it to comply with the standards in order to continue using it in EBS Release 12.2. There are a number of resources available to help you with this, including the Oracle EBS Developer’s Guide and the Oracle EBS online documentation.
Here are some additional details about the R12.2 development standards:
* **Version control systems:** Version control systems allow you to track changes to custom code over time. This makes it easier to revert to a previous version of the code if something goes wrong.
* **Unit tests:** Unit tests are small, self-contained tests that verify that individual units of code work as expected. Unit tests can help to ensure that custom code is reliable and bug-free.
* **Documentation:** Documentation is essential for making custom code easy to understand and maintain. Documentation should include information about the purpose of the code, how it works, and any known limitations.
* **Coding standards:** Coding standards are a set of rules for writing code. Coding standards can help to ensure that custom code is consistent and easy to read.
I hope this information is helpful. Please let me know if you have any other questions.
Hope this helps.
Thanks and Regards
Rahul Dangayach
Team K21Academy