Category: ADOP

Downtime mode is introduced in E-Business Suite Release 12.2, to minimize the duration of 12.2 upgrade process.This feature is available from AD.Delta.5 Release Update Pack.

Before applying patch in downtime mode, all Application services must be shutdown.Downtime mode does not use online patching cycle phases,hence it applied patches quickly compared to online patching. However, EBS application will be down for longer time in downtime mode.Make sure that no adop cycle is in progress while applying patch in downtime mode, Otherwise it will give error.

To apply patch in downtime mode. Follow the below steps

1. Shut down Application Services

2. Apply patch using the below command

 $ adop phase=apply patches=<patch_number> apply_mode=downtime

3. Startup Application Services

Following Scenarios require to apply patch in downtime mode in R12.2

1. All Patching that is part of 12.2 upgrade process. Once the upgrade is complete and users are online, all subsequent patching on a production system should use online mode, unless stated in patch ReadMe.

2. Single-node development or test environments, where production support and high availability are not required.

Limitations of downtime mode

1. We cannot test the patch application prior to cutover as in online patching cycle.
2. We cannot rollback patch applied using downtime mode.
3. Downtime mode is not applicable for Multi-node environments

The online patching cycle in R12.2  which uses ADOP  utility applies patch in 5 Phases
The phases are

PREPARE
APPLY
FINALIZE
CUTOVER
CLEANUP

PREPARE PHASE:

1)Prepares the Filesystem

During Prepare phase,RUN and PATCH filesystems are synchronized.By Default, Synchronization is done in incremental mode.
Full Synchronization is also available, if needed.

This is to ensure that all files on PATCH filesystem are exact copy of files on RUN Filesystem.

2)Prepares the Database

A new patch edition is created in the database.All code objects in the Patch Edition begin as pointers to code objects in the Run Edition
Objects are only “Actualized” into the Patch Edition when a new revision of the code is applied. Storage objects such as tables are not copied.
This ensures efficient use of space.

Use the below Command to start prepare

$ adop phase=prepare

Prepare phase runs Cleanup from previous cycle if it wasn’t run explicitly. To minimise the execution time of prepare phase, we need to run cleanup  explicitly.
Also, submits Online Patching concurrent program (ADZDPATCH),o prevent online patching incompatible concurrent programs from executing.