Introduction
In Oracle E-Business Suite (EBS) R12.2, patching is performed using the Online Patching utility (ADOP). This approach allows administrators to apply patches with minimal downtime, ensuring that the system remains available to users during most of the patching process.
ADOP uses Edition-Based Redefinition (EBR) to maintain two database editions:
-
Run Edition – Used by end users for normal operations
-
Patch Edition – Used by DBAs to apply patches
Once patching is completed, the patch edition becomes the new run edition during cutover.
The ADOP patching cycle consists of several phases:
-
Prepare
-
Apply
-
Finalize
-
Cutover
-
Cleanup
This article explains each phase of the Oracle ADOP patching cycle from Prepare to Cleanup.
ADOP Patching Cycle Phases
1. Prepare Phase
The Prepare phase initializes the online patching cycle and prepares the system for patching.
Key activities in this phase:
-
Creates the patch edition in the database
-
Synchronizes the file system between run and patch editions
-
Verifies system readiness for patching
-
Starts required services for the patch edition
Command
adop phase=prepare
Example
adop phase=prepare apps_user=apps apps_pwd=*****
Verification
Check the status of the patching session:
adop -status
2. Apply Phase
The Apply phase is where the patch is actually applied to the patch edition of the system.
During this phase:
-
Patch files are applied to the patch file system
-
Database changes are applied to the patch edition
-
Users continue working on the run edition
Command
adop phase=apply patches=<patch_number>
Example
adop phase=apply patches=12345678
Multiple Patches
You can apply multiple patches at once:
adop phase=apply patches=12345678,87654321
3. Finalize Phase
The Finalize phase prepares the system for the cutover phase.
This phase performs several tasks to reduce downtime during cutover.
Key activities:
-
Compiles invalid objects
-
Validates patch edition changes
-
Prepares data dictionary objects
-
Ensures system readiness for cutover
Command
adop phase=finalize
4. Cutover Phase
The Cutover phase is the only phase that requires system downtime.
During cutover:
-
The patch edition becomes the new run edition
-
The old run edition becomes obsolete
-
Services are restarted
Command
adop phase=cutover
Activities performed:
-
Stops application services
-
Promotes patch edition to run edition
-
Restarts services
Cutover typically takes a few minutes, depending on the environment.
5. Cleanup Phase
The Cleanup phase removes obsolete data from previous editions.
Key tasks:
-
Drops the old database edition
-
Removes unused objects
-
Frees database space
Command
adop phase=cleanup
Cleanup Options
Standard cleanup:
adop phase=cleanup
Full cleanup:
adop phase=cleanup cleanup_mode=full
Check ADOP Status
You can check the status of the patching cycle using:
adop -status
This command displays:
-
Current phase
-
Session ID
-
Patch progress
Best Practices for ADOP Patching
Always run ETCC (EBS Technology Codelevel Checker) before patching
Ensure sufficient disk space in both file systems
Take a backup before starting the patching cycle
Monitor logs during the apply phase
Run cleanup regularly to remove old editions
Caution: Your use of any information or materials on this Blog is entirely at your own risk. It is provided for educational purposes only.