# How the adop Patching Cycle Works in Oracle EBS 12.2

> Source: https://netray.co/erp-help/ebs-adop-patching-cycle-r12-2
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: ERP Help

## Short answer

adop, AD Online Patching, applies patches to the offline patch edition of the file system while users keep working on the current run edition, then switches editions in a short cutover window. A standard cycle runs prepare, apply, finalize, cutover and cleanup, each invoked as its own adop phase= command.

## Kind

advanced

## System

oracle-ebs

## Erp

Oracle E-Business Suite

## Module

AD / Online Patching (adop)

## Query

how does the adop patching cycle work in Oracle EBS 12.2

## Alternate Queries

- adop prepare apply finalize cutover cleanup
- adop patching phases explained
- oracle ebs online patching fs1 fs2
- adop apply phase stuck or fails

## Applies To

Oracle E-Business Suite 12.2.x (Online Patching / Edition-Based Redefinition architecture)

## Steps

### Run a standard adop patching cycle

**Items:**

- Confirm system readiness with adop -status, and run adop phase=fs_clone first if fs1 and fs2 are not already in sync before starting a new cycle.
- Run adop phase=prepare to create a new patch edition on the patch file system and validate prerequisites.
- Run adop phase=apply patches=<patch numbers> to apply one or more patches to the offline patch file system while users keep working on the run file system.
- Review the apply log under $APPL_TOP/admin/<SID>/log for errors; a failed apply phase can be rerun after the underlying issue is fixed, since adop resumes from the failure point rather than starting over.
- Run adop phase=finalize to perform steps that must complete before cutover, including compiling and validating packages on the patch edition.
- Run adop phase=cutover during a short maintenance window; this is the only phase that requires application downtime, typically a few minutes, since it swaps the run and patch file systems.
- Run adop phase=cleanup to remove the old run edition data and reclaim space once the cutover is confirmed stable.
- Use adop phase=abort if a cycle needs to be rolled back before cutover completes.

## Sections

### Why dual file systems (fs1/fs2)

**Body:**

Online patching keeps two complete copies of the application tier, fs1 and fs2. At any time one is the run edition serving users and the other is the patch edition being updated, so patching does not require downtime until the brief cutover phase swaps them.

On the database side, each patching cycle creates a new Edition-Based Redefinition edition, so PL/SQL objects can be recompiled and changed on the patch edition without breaking sessions still running against the current run edition's objects.

### What each phase actually does

**Body:**

Prepare creates the new patch edition, checks the file system is in sync, and verifies patch prerequisites and locks before any patch content is applied.

Apply applies the patch driver's actions, copy, generate and database changes flagged hotpatch or nonhotpatch, to the patch edition; hotpatch-eligible changes can apply to the run edition immediately for the zero-downtime portion of a patch.

Finalize completes housekeeping before the swap, cutover performs the actual edition switch and restarts services on the new run file system, and cleanup drops obsolete edition data and superseded PL/SQL objects once the cycle is stable.

### Common failure points and recovery

**Body:**

Merging related patches with admrgpch before running apply reduces the number of cutovers needed for a large patch set, since multiple merged patches can go through prepare, apply, finalize and cutover as a single cycle.

adop tracks session and cycle state, so a failed phase can be restarted with the same command after fixing the underlying issue, an invalid object, a missing prerequisite patch, or a failed worker, rather than restarting the whole cycle. Check ad_adop_session_patches and the worker-level adzdpatch.log for the specific failure before rerunning.

## Pitfalls

- Running cutover during business hours without warning users about the brief outage
- Skipping fs_clone after a failed or aborted cycle, leaving fs1 and fs2 out of sync for the next cycle
- Not merging related patches with admrgpch before apply, causing more cutovers than necessary
- Ignoring invalid objects left after finalize instead of investigating them before cutover
- Running cleanup too soon after cutover, before confirming stability, which makes rollback harder
- Multiple DBAs running adop concurrently on the same instance without checking adop -status first, causing phase order conflicts

## Ai Angle

An AI assistant grounded in the instance's AD admin logs can summarize a failed apply phase's adzdpatch.log across thousands of worker lines, point directly at the failing object and error, and suggest whether the fix is a reapply, an invalid-object recompile, or a missing prerequisite patch, saving a DBA the usual manual log scroll during a patching window.

## Faq

### How long does cutover actually take?

**Answer:** Typically a few minutes, since cutover only swaps the run and patch file system pointers and restarts services rather than reapplying any patch content, which already completed during the apply and finalize phases.

### Can I apply multiple patches in a single adop cycle?

**Answer:** Yes. Merge the patches with admrgpch first, or list multiple patch numbers on the same adop phase=apply command, so they go through prepare, apply, finalize and cutover together instead of requiring a separate cutover per patch.

### What does hotpatch mean in adop?

**Answer:** A hotpatch-eligible action is safe to apply directly to the run edition without waiting for cutover, typically simple, low-risk changes, which is why some patch content appears to take effect immediately during the apply phase.

### Does the apply phase require any downtime?

**Answer:** No. Apply runs against the offline patch edition while users continue on the run edition; only the cutover phase requires a short application outage.

## Search terms

adop patching cycle, oracle ebs 12.2 online patching, adop phase=cutover, fs1 fs2 file system, adop prepare apply finalize, ebs online patching explained, adop apply phase failure, ad online patching phases

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