# Oracle EBS 12.2.x Release Update Pack (RUP) Upgrade Checklist

> Source: https://netray.co/tools/oracle-ebs-12-2-rup-upgrade-checklist
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Plan and run an Oracle EBS 12.2.x Release Update Pack upgrade with adop, from ETCC and AD/TXK delta to cutover and regression tests.

## Category

oracle

## Erp

Oracle E-Business Suite

## Audience

- EBS DBA
- Apps DBA
- EBS developer
- ERP project manager

## Tool

**Kind:** checklist

**Groups:**

#### 1. Plan the target code level

**Items:**

**Text:** Choose the target RUP (for example 12.2.14 or later) from Oracle's current suite-wide RUP information note, not from an old blog post

**Critical:** true

**Text:** Read the target RUP readme end to end: prerequisites, minimum database release, required AD/TXK level and post-install steps

**Critical:** true

Check Certifications on My Oracle Support for your OS, database and Java releases at the target RUP

Record current code levels from AD_TRACKABLE_ENTITIES (abbreviation, codelevel) and the release_name in FND_PRODUCT_GROUPS

Book a full-size clone for a timed rehearsal

#### 2. Technology stack first

**Items:**

**Text:** Run ETCC (checkDBpatch.sh and checkMTpatch.sh, Doc ID 1594274.1) and apply missing database and Fusion Middleware fixes

**Critical:** true

**Text:** Apply the latest AD and TXK Delta Release Update Packs in their own adop cycle before the RUP, as the readme requires

**Critical:** true

Bring WebLogic Server and Oracle JDK patch levels to what the RUP and ETCC expect

Confirm the database release meets the RUP minimum; upgrade the database first if it does not

#### 3. Custom code readiness

**Items:**

**Text:** Run the Online Patching Database Compliance Checker (ADZDDBCC.sql) and fix violations in custom objects

**Critical:** true

Run the Online Patching Readiness reports (ADZDPSUM.sql, ADZDPMAN.sql, ADZDPAUT.sql) and act on the manual fixes

Use Patch Wizard impact analysis to list seeded files the RUP changes and compare with your custom code inventory

Identify Forms Personalizations, CUSTOM.pll logic and OAF personalizations on screens the RUP replaces

#### 4. Execute with adop

**Items:**

adop phase=prepare on a healthy system (no pending sessions, previous cycle cleaned up)

**Text:** Apply the RUP with the mode the readme states: online with adop phase=apply, or downtime mode with adop phase=apply apply_mode=downtime when an outage is scheduled

**Critical:** true

Run the RUP post-install steps listed in the readme in the order given

adop phase=finalize, then phase=cutover in the outage window, then phase=cleanup

adop phase=fs_clone to synchronise the patch file system before the next patching cycle

#### 5. Post-upgrade steps

**Items:**

**Text:** Complete product-specific functional post-steps from the readme (setups, data upgrade programs, concurrent requests)

**Critical:** true

Compile invalid objects and compare counts with the pre-upgrade baseline

Run AutoConfig if the readme or ETCC changes require it, and regenerate forms or JAR files where listed

Gather statistics as the readme recommends

Confirm the new release_name in FND_PRODUCT_GROUPS and codelevels in AD_TRACKABLE_ENTITIES

#### 6. Test and sign off

**Items:**

**Text:** Regression test custom extensions, reports and interfaces in the rehearsal environment

**Critical:** true

Review OAF personalizations and Forms Personalizations on changed screens

Test inbound and outbound integrations, printers, workflow mailer and scheduled requests

Record actual phase timings from the rehearsal to plan the production window

**Scoring Note:** The readme for your target RUP overrides any item here. Keep the AD/TXK cycle separate from the RUP cycle.

## Content

**Intro:** This checklist plans a move between Oracle E-Business Suite 12.2 code levels, for example 12.2.6 or 12.2.10 to 12.2.14 or a later RUP, using online patching (adop). It covers the technology stack, custom code compliance, the adop cycle and the post-steps that most projects underestimate.

**Sections:**

#### How to use it

**Body:** Treat the target RUP as a variable. Oracle publishes a readme for each 12.2.x release update pack and a suite-wide note listing RUPs with their AD/TXK requirements; read both before committing to a level. Then run the groups on a full-size clone, record timings and issues, and reuse the list for production. Critical items are the ones that, if skipped, stop the RUP from applying or leave the system unsupported.

**Bullets:**

- Rehearsal on a clone with production volumes
- Separate adop cycle for AD/TXK Delta
- Keep ETCC reports before and after

#### Where code levels live in EBS

**Body:** The current release shows in FND_PRODUCT_GROUPS.RELEASE_NAME, for example 12.2.10. Individual technology and product code levels are tracked in AD_TRACKABLE_ENTITIES, where ABBREVIATION identifies the entity (ad, txk, fnd and so on) and CODELEVEL holds the level such as C.13. Query both before and after the upgrade and keep the output with your change record. Applied patches are recorded in AD_APPLIED_PATCHES and AD_BUGS, which is how you confirm a prerequisite is present rather than trusting a spreadsheet.

**Bullets:**

- select release_name from apps.fnd_product_groups;
- select abbreviation, codelevel from apps.ad_trackable_entities where abbreviation in ('ad','txk','fnd');

#### Online or downtime mode

**Body:** adop normally applies patches to the patch file system while users work, then switches at cutover. For a RUP, the readme states whether online mode, downtime mode (adop phase=apply apply_mode=downtime) or both are supported. Downtime mode skips the online patching overhead and can shorten total elapsed time when you are already taking an outage, but users cannot work during the apply. Decide using rehearsal timings, not guesses, and check that your previous adop cycle is fully cleaned up before you start.

#### Common mistakes

**Body:** The usual failures are skipping the AD/TXK delta cycle, applying the RUP before ETCC is clean, and discovering custom objects that violate online patching rules halfway through. Post-install steps in the readme are also easy to miss because the patch itself completes successfully without them. Finally, teams often test seeded flows but not personalizations and custom extensions on replaced pages, which is where users notice the change first.

**Cta:** After a RUP, we can add an on-prem AI assistant that answers questions over your upgraded EBS data and documents, without sending anything outside your network.

**Faq:**

#### How do I upgrade EBS from 12.2.6 to 12.2.14?

**Answer:** Apply ETCC-required database and middleware fixes, then the latest AD and TXK Delta packs in their own adop cycle, then the 12.2.14 RUP with the mode its readme states, followed by the readme post-steps, cutover, cleanup and fs_clone. Rehearse on a full clone and regression test custom code before production.

#### How do I find my current EBS 12.2 version?

**Answer:** Query RELEASE_NAME from APPS.FND_PRODUCT_GROUPS. For technology code levels, query ABBREVIATION and CODELEVEL from AD_TRACKABLE_ENTITIES, for example for ad and txk. The Oracle Applications Manager pages also show the release, but the tables are the definitive source.

#### Should the RUP be applied in downtime mode?

**Answer:** Check the readme of the specific RUP: it states the supported modes. Downtime mode (apply_mode=downtime) avoids online patching overhead and is often faster when an outage is planned anyway, but the system is unavailable throughout. Online mode keeps users working until cutover at the cost of a longer total cycle.

#### What is ETCC and why run it before a RUP?

**Answer:** The EBS Technology Codelevel Checker (Doc ID 1594274.1) compares your database and middleware homes with the bug fixes EBS requires. checkDBpatch.sh runs on the database tier and checkMTpatch.sh on the application tier. Missing fixes can cause RUP failures or unsupported configurations, so clear them first.

## Search terms

upgrade oracle ebs r12.2.6 to r12.2.13, how to upgrade oracle ebs 12.2.0 to 12.2.10, oracle ebs 12.2 14 upgrade, oracle ebs 12.2 15 upgrade, oracle ebs 12.2.15 patches, oracle ebs latest version 12.2.14, ebs rup downtime mode

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json