In this post we will discuss about ADOP online patching method which was introduced in Oracle EBS R12.2. It has different phases which help us to apply the patch with minimum downtime using adop.
Overview of ADOP in Oracle EBS R12.2
ADOP – stands for Application DBA Online Patching which is introduced in Oracle EBS R12.2 version to patch oracle applications while a system is available for users during Patching.
The new ADOP tool has greatly reduces the downtime that was needed in previous release. Before EBS R12.2 we need to shutdown Oracle application tier services to apply the patch using adpatch but EBS R12.2 finally comes up with the solution to this by introducing new ADOP Online Patching tool where the users can be still connected to the environment while patch is being applied to the system.
Only a very small downtime is required when the users gets disconnected during the cutover phase.
Online patching is supported by the capability of storing multiple application editions in the database, and the provision of a dual application tier file system fs1 and fs2. At any given point in time, one of these file systems is designated as run (part of the running system) and the other as patch (either being patched or
awaiting the start of the next patching cycle).
NOTE: The adop utility always runs from the run edition file system. Full application functionality is retained as patch execution proceeds, until the cutover phase is reached.
The online patching cycle consists of five of high level phases:
- prepare: Prepares the environment for patching.
- apply: Applies the specified patches to the environment.
- finalize: Performs any final steps required to make the system ready for cutover.
- cutover: Shuts down application tier services, makes the patch edition the new run edition, and then restarts application tier services. This is the only phase the involves a brief downtime.
- cleanup: Removes obsolete code and data from old editions.
Special Phases
abort: The abort phase is used to terminate a patching cycle before it is complete, and roll back any changes that have been made. It aborts the online patching cycle by dropping the database patch edition.
After running abort, a full cleanup must be performed. The cleanup command is : adop phase=cleanup cleanup_mode=full. This will remove any columns that were added by the patch but are no longer needed because of the abort. If they are not removed, they may cause problems in a later patching cycle.
fs_clone : The fs_clone phase is a command (not related to adcfgclone.pl) that is used to synchronize the patch file system with the run file system. Normally, the fs_clone phase should only be run when mentioned as part of a specific documented procedure.
It recreates the patch edition file system as an exact copy of the run edition file system, preserving the mode, ownership, and timestamps of the files. This phase cannot be specified with any other phase. Use of fs_clone is normally not required. Situations that do require fs_clone are will explicitly document that requirement. If running this phase, ensure that your current working directory is not within the patch edition file system.
Steps to Apply Patch using R12.2 ADOP Online Patching Tool
STEP 1: Download the patch <patch > and unzip on fs_ne location.
cd /scratch/u01/E-BIZ/fs_ne/EBSapps/patch
unzip < patch >
STEP 2: Source the env file.
As an application user source the environment variable.
source /scratch/u01/E-BIZ/EBSapps.env run
STEP 3: Run prepare phase and once completed move to next step.
adop phase=prepare
Enter the APPS password:
Enter the SYSTEM password:
Enter the WLSADMIN password:
STEP 4: Execute apply phase and move to next step once completed
adop phase=apply patches=<patch Number> workers=16
Enter the APPS password:
Enter the SYSTEM password:
Enter the WLSADMIN password:
NOTE: You can also use options=forceapply, and also you can apply multiple patches at a time. Specify patch number separated by a comma like adop phase=apply patches=32078417, 3207818 workers=32
STEP 5: Run finalize phase and move to next step.
adop phase=finalize
Enter the APPS password:
Enter the SYSTEM password:
Enter the WLSADMIN password:
STEP 6: Run cutover phase and it requires downtime.
adop phase=cutover
Enter the APPS password:
Enter the SYSTEM password:
Enter the WLSADMIN password:
STEP 7: Finally run the cleanup phase.
adop phase=cleanup
Enter the APPS password:
Enter the SYSTEM password:
Enter the WLSADMIN password:
Once the phase is complete, you can check the adop status using below command.
adop -status
Query to Check the Applied Patch in apps R12.2
select BUG_NUMBER,LAST_UPDATE_DATE from apps.ad_bugs where BUG_NUMBER='&patchnumbe';
After going through the above post hope you are clear on:
- What is adop in EBS R12.2 ?
- Overview of Adop in R12.2
- Steps to apply patch using adop in R12.2
- To check the status of adop
- To check the applied patch in Oracle EBS R12.2