Академический Документы
Профессиональный Документы
Культура Документы
Prepared By Sachin
Oracle E-Business R12.2 introduced a new patching mechanism that allow the
application of patches while your environment is up and running which is called as
Online patch. ADOP Patching replaces adpatch in 12.2
The base for the online patching concept came into picture with 11GR2 database
version, where there is a concept called "Edition Based Redefinition", database
online patching is based on it.
Now it is possible to apply even upgrade patches in Online Patching mode
minimizing downtime to very low.
Please note upgrade to 12.2 is not possible via online patching from lower versions.
Online Patching in 12.2 is done using adop utility (No more adpatch), but this utility
calls internally adpatch to do the patching.
All the patches need to be applied using adop only, other options/methods are not
supported. But we can apply the patches in hot patch mode using adop, but in this
method, the online patching concept will not come into picture, it is a traditional
way of applying patch directly on the run file system and run edition of the database
when applications and DB is running.
On database side, online patching database objects also maintain two copies to
support this method i.e. run file system and run edition of DB, patch file system and
patch edition of DB.
On applications side, It contains two set of file systems patch and run file system.
Run is where actually applications is running from and patch is used for patching the
applications when it is running.
In database we have edition based concept, where we contain patch edition and run
edition.
The online patching cycle consists of number of phases:
1)
2)
3)
4)
5)
6)
7)
1|Page
1) Prepare Phase :
In this phase, patch edition and run editions are synchronized in incremental
synchronizations of files changed in the run file system.
Syntax: $ adop phase=prepare
2) apply phase :
In this phase, patches are applied to patch edition in the database and patch
file system in the applications.
adpatch is called internally by adop to apply the patches.
Production application is not affected by these changes, and multiple patches
can be applied.
Syntax: $ adop phase=apply
3) finalize phase :
In this phase, performs all the activities which can be done when applications
is up & running like compile invalid objects.
Syntax: $ adop phase=finalize
4) cutover phase :
This is the stage where actual changes reflects and downtime is required for
this phase.
Users are logged off during this stage. Patch file system is promoted to be the
run file system.Patch database edition is promoted to the run database
edition.
Syntax: $ adop phase=cutover
5) cleanup phase :
This phase happens once users online on the system.There is no cleanup on
the file system , only it happens on the database where it deletes the code
objects from old editions of the database where patching happened.
Syntax: $ adop phase=cleanup
6) fs_clone phase :
Synchronize the file system, which copy the new run edition code and
configuration to the patch file system.
2|Page
3|Page
4|Page
$ echo $RUN_BASE
<shows absolute path to run file system>
$ echo $PATCH_BASE
<shows absolute path to patch file system>
$ echo $NE_BASE
<shows absolute path to non-edition file system>
$ echo $APPL_TOP_NE
<non-editioned appl_top path. Equivalent to $NE_BASE/EBSapps/appl>
$ echo $LOG_HOME
<Application Instance Specific Log Directory>
$ echo $ADOP_LOG_HOME
< ADOP Log Directory i.e. $NE_BASE/EBSapps/log/adop>
Thank You.
5|Page