# Oracle EBS 12.2 Upgrade Readiness Checklist > Source: https://netray.co/tools/oracle-ebs-12-2-upgrade-readiness-checklist > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Check whether your EBS environment, custom code and team are ready to move to Release 12.2 and what to settle before the project starts. ## Category oracle ## Erp Oracle E-Business Suite ## Audience - EBS DBA - EBS project manager - IT director ## Tool **Kind:** checklist **Scoring Note:** Unchecked critical items are blockers for a project start date. Convert each into an owner and a due date in the project plan. **Groups:** #### Scope and support **Items:** **Text:** Confirm your current release and patch level and the supported upgrade path to 12.2 in Oracle documentation **Critical:** true **Text:** Check the Oracle support dates for your current release and set a latest-start date **Critical:** true Decide upgrade only, or upgrade plus functional change, and write the scope down Confirm licenses and any extended support cost in the budget Name a business owner for each module in scope **Text:** Agree testing resources from the business, not only from IT **Critical:** true #### Technology stack **Items:** **Text:** Check certified combinations of database, operating system, browser and Java for your target 12.2 patch level **Critical:** true Plan the database upgrade or move needed for your target release **Text:** Check disk space for the dual file system that online patching uses **Critical:** true Plan the Oracle WebLogic Server based application tier and its sizing Review load balancer, SSL and single sign-on integrations for compatibility Review backup and restore capacity for repeated test upgrades #### Customizations and integrations **Items:** **Text:** Inventory custom objects, forms, reports, workflows and personalizations **Critical:** true **Text:** Run the Online Patching Readiness reports and list objects that need remediation **Critical:** true Check custom tables, views, synonyms and PL/SQL packages for online patching rules List all integrations, file interfaces, database links and third-party tools Retire custom code that no longer has users Decide who owns each remediation item and when it is due Check that Forms and OAF customizations are compatible with the target stack #### Testing and data **Items:** **Text:** Plan at least one full-size test upgrade on a production copy **Critical:** true **Text:** Record upgrade run time for each test so cutover planning has real numbers **Critical:** true Build a regression test set for each module, including period close and interfaces Prepare test data and test users that match production roles Plan performance testing for key concurrent programs and reports Agree defect triage and sign-off rules #### Cutover and operations **Items:** **Text:** Pick a cutover window outside period close and agree the freeze period **Critical:** true **Text:** Write a rollback plan and test restoring the pre-upgrade backup **Critical:** true Train DBAs on adop phases and on running a patching cycle Update monitoring, backup jobs and runbooks for the 12.2 file system layout Plan user communication and training for new screens or behavior Plan a hypercare period with named support people ## Content **Intro:** Moving Oracle E-Business Suite to Release 12.2 changes more than the version number: it introduces online patching, a dual file system and a WebLogic based application tier. This checklist helps you judge readiness before you commit to a date. **Sections:** #### How to use this checklist **Body:** Work through the groups with your DBA, functional leads and the owner of customizations. Mark an item only when you have evidence, such as a certified combination from Oracle documentation or a readiness report output. The unchecked critical items become the first month of the project plan. Export the result to PDF and attach it to your business case, so the budget conversation uses facts. #### What changes with 12.2 **Body:** Release 12.2 uses online patching, so most patches are applied to a copy of the application file system and database objects while users stay on the running system. The tool that drives this is adop, and it uses edition-based redefinition in the database. For you, this means more disk, new DBA routines, and a requirement that custom database objects follow online patching rules. The upgrade effort is often driven more by custom code remediation than by the standard upgrade scripts. **Bullets:** - Dual run and patch file systems - Edition-based redefinition in the database - adop replaces the older patching routine - Custom objects need readiness review #### Common planning mistakes **Body:** The usual mistakes are starting too late against a support date, counting only technical time and forgetting business testing, and running one test upgrade on a small copy that hides real run times. Another is leaving custom code review to the last month. Start with the inventory and the readiness reports, because they tell you how large the remediation work is. Then size the project from your own test upgrade timings, not from generic estimates. **Cta:** If custom code analysis is your bottleneck, we can discuss using on-premises AI tooling to read and summarize your custom PL/SQL and report definitions, with your engineers reviewing every output. **Faq:** #### How long does an EBS 12.2 upgrade take? **Answer:** It depends on module count, data size and the amount of custom code. Projects commonly run several months from planning to go-live. Your own test upgrade timings and remediation inventory are better predictors than any generic figure, so measure them early. #### What is online patching in 12.2? **Answer:** It is a patching method where patches are applied to a second copy of the file system and to a new database edition while users keep working. A short cutover switches to the patched copy, which reduces downtime for normal patching cycles. #### Do I need to change my custom code? **Answer:** Often yes. Custom objects in the database must follow online patching rules, for example around editioned objects. Oracle provides readiness reports that list issues. Run them early so you can size remediation before you set the go-live date. #### Where do I check support dates? **Answer:** Use Oracle's Lifetime Support Policy documents and your support contract, since dates and terms can change. This checklist does not state dates for that reason. Confirm the current dates, then use the planning calculator on this site to test your timeline. ## Search terms oracle ebs 12.2 upgrade checklist, oracle ebs upgrade from 12.1.3 to 12.2, ebs 12.2 upgrade readiness, online patching readiness report, oracle ebs 12.2 upgrade planning, ebs 12.2 customization remediation, oracle ebs upgrade project plan --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json