R12.2.X ADOP Patching Cycle

ADOP / Online Patching: 
****************************

Main Feature => ***  Minimal definable Downtime ***

FS1 – (RUN_EDITION) Production file system that is used by online users when system is being patched.

FS2 – (PATCH_EDITION) Exact copy of production(fs1) used by the patching tools. Changes do not affect the running application(RUN_EDITION).

When patching is completed and we do CUTOVER, then patching tool swaps the FS1 and FS2 file systems. It means, FS2  file system will become FS1 , which will be access by the users.

FS-NE (Non-Edition) – This is a non-edition file system which stores data that is stored in a file system like log file, report file and patch top files.

There are below 5 Phases of ADOP(online patching)

1) PREPARE
2) APPLY
3) FINALIZE
4) CUTOVER
5) CLEANUP

$ adop phase=prepare

check the status - $ adop -status

$adop phase=apply patches=<Patch Number>

$adop phase=finalize

$adop phase=cutover

$adop phase=cleanup

If there are some reason either the prepare or apply phase failed or any problems then you can abort this patching cycle.

$adop phase=abort

After running abort, you must always run a full cleanup as:

$adop phase=cleanup cleanup_mode=full