# Oracle EBS 12.2 Patching Checklist (adop Online Patching Cycle)

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

## Short answer

Step through a full adop patching cycle with pre-checks, the five phases and post-patch validation.

## Category

oracle

## Erp

Oracle E-Business Suite

## Audience

- EBS DBA
- Apps DBA
- Release manager

## Tool

**Kind:** checklist

**Scoring Note:** Run the cycle on a test copy first. Record start and end time of each phase so you can estimate the production window.

**Groups:**

#### Before you start

**Items:**

**Text:** Read the readme of every patch and note prerequisites and post-install steps

**Critical:** true

**Text:** Check that no previous patching cycle is left incomplete, using adop status reporting

**Critical:** true

**Text:** Take a backup of the database and application file systems

**Critical:** true

Confirm free disk space on both file systems and in the database

Source the run file system environment before running adop

Merge patches where the readme or your policy asks for it

Notify users and support teams of the patching window

#### Prepare phase

**Items:**

**Text:** Run adop phase=prepare to create the patch edition and sync the patch file system

**Critical:** true

Confirm the prepare phase finished with no failed workers

Check that the patch file system is a clean copy of run before applying

Record the session id for the cycle

#### Apply and finalize

**Items:**

**Text:** Run adop phase=apply patches=<number> for each patch or merged patch

**Critical:** true

**Text:** Review the adop log files and worker logs for errors

**Critical:** true

Resolve failed jobs and restart the apply phase with the correct options

Run adop phase=finalize to compile invalid objects and prepare for cutover

Check invalid objects count in the patch edition

#### Cutover and cleanup

**Items:**

**Text:** Schedule the short outage and stop users before cutover

**Critical:** true

**Text:** Run adop phase=cutover to switch the patch edition to run

**Critical:** true

Start services on the new run file system and verify access

**Text:** Run adop phase=cleanup to remove obsolete editions and objects

**Critical:** true

Run a full cleanup mode when the policy requires it and the cycle is verified

Run the file system clone if the old run file system must be synced to the new one

#### After patching

**Items:**

**Text:** Run the post-install steps from each patch readme

**Critical:** true

Check invalid objects and compile what remains

Smoke test login, key forms, a concurrent request and a workflow

Run regression tests for modules touched by the patch

Update the patch log with patch numbers, dates and who applied them

Apply the same patch set to the other environments in order

## Content

**Intro:** In Oracle E-Business Suite 12.2, patches are applied with the adop utility through a set of phases: prepare, apply, finalize, cutover and cleanup. This checklist turns that cycle into a runbook you can tick through and export for your change record.

**Sections:**

#### How to use the checklist

**Body:** Print or export the list for each patching cycle and fill it in as you go. Add the patch numbers and the time each phase started and ended in your change ticket. Use the checklist on your test instance first and keep the notes, because the timings from test are what you will quote when you ask the business for a cutover window. Keep one cycle open at a time per environment.

#### The adop phases in order

**Body:** The prepare phase creates a patch edition and syncs the patch file system. The apply phase applies patches to the patch file system and database edition, and you can apply more than one patch in this phase. Finalize does the compile work that can be done ahead of cutover. Cutover is the short outage when the patch edition becomes the run edition. Cleanup removes the obsolete objects. Hotpatch mode applies a patch directly to the run file system and needs downtime, so use it only when the readme says so.

**Bullets:**

- adop phase=prepare
- adop phase=apply patches=<number>
- adop phase=finalize
- adop phase=cutover
- adop phase=cleanup

#### Common mistakes

**Body:** Frequent problems include starting a new cycle while the previous one is incomplete, skipping the readme post-install steps, and running out of space on the patch file system. Another is running cleanup before the team has verified the cutover. Read the log directory that adop prints at the start of each phase, because worker failures are in the logs, not always on the screen. Never delete adop session data by hand.

**Bullets:**

- Check adop status before starting
- Do not skip the readme steps
- Verify cutover before cleanup
- Keep logs for each cycle

**Cta:** If your patch runbooks live in scattered documents, we can discuss an on-premises assistant that reads your own runbooks and patch logs and answers DBA questions, with no data leaving your network.

**Faq:**

#### What are the adop phases?

**Answer:** The standard online patching phases are prepare, apply, finalize, cutover and cleanup. A separate fs_clone phase syncs the file systems. You run them in order for a patching cycle, and users stay online until cutover.

#### Do I need downtime to patch EBS 12.2?

**Answer:** For online patching, downtime is limited mainly to the cutover phase. Patches applied in hotpatch mode or patches that require downtime according to their readme need a longer outage. Always read the patch readme before you plan the window.

#### Can I apply several patches in one cycle?

**Answer:** Yes. You can pass several patch numbers to the apply phase in one cycle, and you can merge patches when the readme or your policy asks. Test the combination first, since one failing patch can hold up the whole cycle.

#### What if a cycle is left incomplete?

**Answer:** Check the adop status first. Depending on the state you may restart the failed phase, or abort the cycle if the guidance for that state allows it. Do not start a new cycle until the old one is closed or aborted according to Oracle documentation.

## Search terms

oracle ebs adop patching checklist, adop phase prepare apply finalize cutover cleanup, oracle ebs 12.2 online patching steps, adop phase=apply patches, ebs 12.2 patching cycle, adop hotpatch mode, oracle ebs patch runbook

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