Mon – Sat: 9:00 AM – 7:00 PM IST
Oracle

What is ADOP online patching?

How R12.2 applies patches while users stay on the system — and the phase where it most often goes wrong.

In short

ADOP (Application DBA Online Patching) is the R12.2 utility that applies patches to a second, patched file system and database edition while users continue working on the current one. A short cutover then switches users across. It is what allows patching without a long outage, and it is also the main reason R12.2 administration differs from R12.1.

Why It Matters

Why this matters in practice

Online patching removed the long maintenance window, which was the main obstacle to keeping an EBS estate current. In exchange it introduced a dual file system and an editioned database, both of which have to be understood and maintained. Estates that never adopted the discipline tend to fall behind on patching precisely because the mechanism feels unfamiliar.

Patches apply while users remain on the running system
Downtime is reduced to a short cutover rather than a full window
Requires a dual file system, which doubles that storage
Custom code must be editioned correctly or cutover fails
How It Works

How it works in practice

1

Prepare

A new patch edition is created from the running edition. The patch file system is synchronised.

2

Apply

Patches are applied to the patch edition. Users are unaffected throughout, which is the point.

3

Finalise

The system performs the work that can be done before cutover, shortening the outage.

4

Cutover

The only downtime. Services restart and users move to the patched edition.

5

Cleanup

Obsolete objects from the old edition are removed. Skipping this causes space and performance problems over time.

Worked example

A worked example: why cleanup is not optional

A team adopts online patching and is pleased with it: patches apply while users work, and cutover takes minutes rather than a weekend. Over several months they apply a dozen patch cycles and skip the cleanup phase each time, because cleanup takes a while and nothing appears to depend on it.

Database growth becomes the first symptom, then performance on editioned objects, then a patch cycle that fails outright because the environment is carrying accumulated editions it was never designed to hold. The fix at that point is a long maintenance window to clean up properly — the exact downtime online patching existed to avoid, now taken all at once and under pressure.

Online patching is a full cycle: prepare, apply, finalise, cutover, cleanup. Treating the first four as the patch and the fifth as optional housekeeping converts a routine into a debt. The discipline is simply to finish the cycle before starting the next one, and to treat a skipped cleanup as an incident rather than a saving.

Key terms

The vocabulary, briefly

Term What it means
Run edition The file system and schema users are currently on.
Patch edition The parallel copy being patched while users continue working on the run edition.
Cutover The brief downtime where the patch edition becomes the run edition.
Cleanup Removing the old edition after cutover. Skipping it is what causes space problems later.
Editioned object A database object that exists in both editions, which is what makes the parallel approach possible.
What Goes Wrong

Common mistakes worth avoiding

Skipping cleanup

Old editions accumulate. Cleanup is part of the cycle, not an optional tidy-up afterwards.

Custom code not editioned

Custom objects that do not follow the editioning rules break at cutover, which is the worst moment to find out.

Treating cutover as zero downtime

Cutover is short but real. It still needs a window and a communication to users.

Abandoning a failed cycle incorrectly

An abandoned patch cycle must be cleaned up properly, or the next one inherits the mess.

What to measure

Numbers worth tracking

Metric What it tells you What distorts it
Cutover duration The actual user-visible downtime, which is the point of the whole mechanism.
Cycles completed vs cleanups run Any gap here is accumulating debt that will be paid later with interest.
Patch cycle failures Often traced back to incomplete prior cycles rather than to the patch being applied.
File system and tablespace growth The dual file system and editions need headroom; running close to full is where cycles fail.
FAQ

Questions we are asked about this

Near-zero rather than zero. Patching happens online, but the cutover phase requires a short restart. The window moves from hours to minutes.
Because it maintains a run file system and a patch file system. That duplication is what allows patching to proceed while users continue on the running edition.
Near-zero, not zero. Users stay on the run edition while the patch applies to the patch edition, so the long part of patching is invisible to them. Cutover still requires a brief outage to switch editions — typically minutes rather than hours. The honest description is that it removes the maintenance weekend, not the maintenance window.
Downtime mode exists and is sometimes the right choice, particularly for large upgrade-class patches or when several patches are being applied together. The mistake is drifting back to it as the default because it feels more familiar. Decide per patch on its characteristics, and keep online mode as the normal route so the team stays practised in it.
Custom objects that are not editioned correctly, direct references to the file system that assume a single path, and anything that writes to database objects in ways the editioning model does not expect. Any custom code written before the move to 12.2 should be reviewed against the online patching standards rather than assumed compatible — it will often run fine until a cutover, and then not.
The apply phase can run for hours without affecting users, which is the whole point, so its duration matters much less than it used to. Cutover is typically minutes. The planning variable that actually matters is cleanup, which needs to complete before the next cycle begins — so schedule cycles with that in mind rather than back to back.
Related

Where to read next

What is Oracle EBS?

Read more

Our Oracle consulting services

Read more

OTBI vs BI Publisher

Read more

Need this applied to your own systems?

We build and support the systems this page describes. Start with a free working proof of concept — no cost, no commitment.