Do you have any questions in your mind or are you confused about Why Upgrade To EBS R12.2?
- Why upgrade to Database 19c?
- What are the new features available in EBS R12.2?
- What are the pre-requisites for the EBS R12.2 upgrade?
Then you have landed at the correct place my dear!
New to Oracle EBS Upgrade? No worries!
Here we have our blog on EBS R12.2 Upgrade High-Level Overview
In this blog, we are continuing with part -3 of FAQs that were asked during the recent batch of our EBS Upgrade R12.2.
Please go through our previous series blogs,
Before moving to the FAQs, let’s brush up on our knowledge of Oracle FMW concepts.
Oracle Fusion Middleware (OHS & WLS)
- FMW is a software application layer that lies between the database and the application layer.
- An infrastructure that facilitates the creation of the business application.
- This includes Web Servers, Application servers, Identity management, SOA, Content Management, and Business Intelligent
- Oracle E-Business Suite R12.2 uses WebLogic & OHS from FMW
To know more, check our blog on Oracle Fusion Middleware.
Oracle E-Business Suite R12.2 Upgrade path & Flow
Oracle E-Business Suite R12.2.9 is the latest release announced by Oracle. Oracle supports a direct upgrade to Oracle E-Business Suite R12.2.9 from Oracle E-Business Suite R12.2.x. So, before performing the upgrading task we must be aware of the below points.
- Identify the supported paths
- Intermediate supported versions
- Check the certification matrix
To know more read our blog on certification matrix and supported OS & versions of Oracle E-Business Suite R12.2.
You can upgrade to Oracle E-Business Suite R12.2 directly from the below base versions.
- EBS 11i
- EBS 12.0
- EBS 12.1
Check Out: Our blog post on Oracle Apps DBA R12.
FAQs Related to Upgrade Path
Q1: Use Case
PROD env is 12.1.3
- 2 node RAC 11204 with PCP enabled CM and ADMIN on the same nodes
- 2 node Forms and Web (shared appl_top)
- 2 nodes DMZ iStore
Can you please put some highlights on Upgrade on multimode PROD env?
Ans: 12.1.3 to 12.2 multi-node or single node are the same.
You will be upgrading your DB, your applications are going to re-install.
Once you upgrade your DB, you will add all your nodes as per your requirements.
Firstly, you have to upgrade to R12.2.9 and then you will do horizontal scaling by adding the nodes and then you configure whatever services, you need as a part of that configuration.
Q2: During our upgrade to 12.2 how to deal with custom codes that running in 12.1.3 and does it need to modify respective to EBR?
Ans: You need to modify your custom codes as per EBR standards, and it is mandatory.
Q3: If we are on oracle database 11.2.0.3 and EBS is on R12.1.3. Does oracle support 11.2.0.3 with extended support?
Ans. No 11.2.0.3 support is expired, the minimum version is 11.2.0.4(ACS market-driven support).
Q4: Every year we see a new version of Apps, so within another 2 or 3 months are we expecting a new version of Apps like 12.2.9.X or any name?
Ans. Yes, it is a point upgrade and 12.2.10 is expected soon.
Q5: For In-place upgrade, Which Application server node, we need to select CM NODE or WebNode. Do We select one node and need to remove the other node before the application upgrade?
Ans. Oracle will take the server you provide, and you must use the primary server and all the services will be configured on that server.
Q6: Before the upgrade is it better to take care of custom unused/unwanted schemas?
Ans. After upgrading to R12.2.0, you can run the adsplice, for an individual custom schema.
Q7: if we want to do an upgrade in our own system, what is the requirement? sys configuration?
Ans. 2 mount points, u01, and root,
16gb RAM, I5 processor
- Mountpoint size: 500G
- OS version: Linux 7 or above
- How many VMs: Only 1 VM
Q8: Before the upgrade is it better to take care of custom unused/unwanted schemas?
Ans. After upgrading to R12.2.0, you can run the adsplice, for the individual custom schema.
Also Check: Our blog post on Oracle EBS Vision Instance.
Online Patching in Oracle E-Business Suite R12.2
Online patching is the new feature introduced in Oracle EBS R12.2 to patching Oracle Applications while the system is available for the users during patching. Online Patching is also known as ADOP which stands for Application DBA Online Patching. Online Patching has 5 phases.
- prepare
- Apply
- Finalize
- Cutover
- Cleanup
To know more, check our blog on Patching.
FAQs related to Online Patching
Q1: Completing cut over is it required to run fs_clone.
Ans. Not mandatory, but recommended, fs_clone deletes the patch file system and recreates it from the run file system. It syncs your patch file system with the run file system.
Q2: Can you explain about downtime mode.
Ans. You stop all the apps tier services, then you call ADOP in downtime mode, it will apply the patch in full downtime mode.
Q3: Unable to find appltop_id for host xxxx in the database, and the cutover phase has failed. How to resolve this patching issue.
Ans. Try to run the autoconfig and retrigger the cutover.
Q4: Is it possible to track the stubs in any newly created ADOP cycle.
Ans. When a new edition is created, stubs are created for all the objects by default. ADZDREPORTS.pl will tell you how many objects are newly created.
Q5: Can we clean up old editions regularly after completing a few patching cycles (around 10 for example)? Do we have any impact because of this?
Ans. you can but doesn’t make sense, suggested and recommended is to do after every 25 editions, every time you run actualize/cleanup it will take around 24-72 hrs, so it is not recommended to do for less number of editions. And the impact is we cannot run any other patch during this cutover or cleanup.
Q6: If we stop the patch can it be restarted without any modification.
Ans. You cannot stop the patch, but if due to some issue it gets terminated, you can restart it by restart=yes, and it will be started from the point of failure.
Q7: When you switch to ‘adop’, do you lose the ability to use ‘adpatch’ – or can you continue to apply patches with ‘adpatch’?
Ans. Yes, you won’t be able to use adpatch anymore but internally adop uses adpatch only to apply patch
Q8: If Adop hangs in the middle of patching what we need to do.
Ans. You should check the logs, there should be the error, the error needs to be troubleshot, fixed and the adop job should be restarted.
Q9: So what is the difference between cleanup full mode and actualize all?
Ans. Actualize moves your editioned objects to a new edition. Cleanup which you run after actualize_all will remove old editions and covered objects.
We have covered the most commonly asked questions related to R12.2 upgrade here. To gain more knowledge on Oracle E-Business Suite R12.2 upgrade, read below mentioned related readings.
Related/ Further Readings
- EBS Upgrade R12.2:Step by a Step activity guide
- EBS R12.2 Upgrade High-Level Overview/Steps
- 19c Database In Oracle EBS R12: Everything You Must Know
- Oracle E-Business Suite R12.1 vs R12.2
- EBS R12.2 Upgrade Frequently asked questions
- EBS R12.2 Upgrade Frequently asked questions Part 2
Next Task For You
Begin your journey towards becoming an Oracle EBS Upgrade R12.2 AppsDBA by joining our Training on Upgrade EBS R12/11i To R12.2
Click on the image below to join FREE Masterclass on Upgrade EBS R12/11i To R12.2:
Leave a Reply