Oracle EBS R12.2 – ADOP Phases and Parameters Explained

Oracle E-Business Suite R12.2 uses Online Patching powered by ADOP (Application DBA Online Patching).

Understanding its phases and parameters is essential for smooth patching with minimal downtime.

This blog provides a clear explanation of each ADOP phase, along with commonly used parameters.

1) PREPARE Phase

The prepare phase starts a new patching cycle by preparing the patch file system for usage.

Syntax:

adop phase=prepare

2) APPLY Phase

The apply phase applies patches to the patch file system, allowing online patching with minimal downtime.

Syntax:

adop phase=apply patches=<patch_number>

Optional Parameters During APPLY Phase

Instead of specifying parameters on the command line, you can use an input file.

adop phase=apply input_file=<full_path_to_file>

Input file may contain:

workers=<number>

patches=<patch1>.drv, <patch2>.drv

phase=<phase>

patchtop=<path>

merge=<yes/no>

defaultsfile=<file>

abandon=<yes/no>

restart=<yes/no>

workers=<number>

Note: Always specify the full path of the input file.

Important APPLY Parameters

a) restart

Used to resume a previously failed patching session.

adop phase=apply patches=<patch> restart=yes

b) abandon

Starts the patch apply from scratch.

adop phase=apply patches=<patch> abandon=yes

c) apply_mode

Used to run the patch in downtime mode (patch applied on run FS).

adop phase=apply patches=<patch> apply_mode=downtime

d) apply = yes/no

Run in test mode by specifying:

apply=no

e) analytics

Enables additional analysis reports during patching.

adop phase=apply analytics=yes

This runs multiple SQL scripts and generates outputs under:

$EBS_HOME/fs_ne/EBSapps/log/adop/<adop_session>/

Generated reports include:

ADZDCMPED.sql – Differences between Run and Patch editions

ADZDSHOWED.sql – List of editions

ADZDSHOWOBJS.sql – Editioned object summary

ADZDSHOWSM.sql – Seed data manager report

3) FINALIZE Phase

The finalize phase performs required steps to prepare the system for cutover, including compilation of invalid objects.

Syntax:

adop phase=finalize

Modes:

finalize_mode=(full|quick)

4) CUTOVER Phase

During cutover, a new run file system is created from the patch file system and becomes active.

Syntax:

adop phase=cutover

Optional Parameters During CUTOVER

a) mtrestart

Prevents automatic restart of application services.

adop phase=cutover mtrestart=no

b) cm_wait

Specify how long ADOP waits for active concurrent requests before shutting down ICM.

Example:

adop phase=cutover cm_wait=30

(Default: waits indefinitely)

5) CLEANUP Phase

Used to clean patching artifacts and logs after cutover.

Syntax:

adop phase=cleanup cleanup_mode=(full|standard|quick)

Default is standard.

6) FS_CLONE Phase

Synchronizes the patch file system with the run file system.

Syntax:

adop phase=fs_clone

Note: Prepare phase automatically performs fs_clone if missed during the last patching cycle.

Optional FS_CLONE Parameters

a) force

Restart fs_clone from scratch.

adop phase=fs_clone force=yes

b) Patch File System Backup Count

s_fs_backup_count=<number>

Default = 0 (no backup)

Determines how many patch file system backups to retain.

7) ABORT Phase

Used to abort the current patching cycle.

Syntax:

adop phase=abort

Note: Can only be executed before cutover.

Conclusion

ADOP is a powerful tool that enables Oracle EBS R12.2 to perform online patching with minimal service downtime.

Understanding its phases and parameters is essential for efficient and error-free patching.