UnionSys is a leading software services and solutions providing company. Established in 2008, with a small group of highly skilled and experienced professionals dedicated to provide best solutions and services. UnionSys capabilities encompass all aspects of software development solution and services. Headquartered in Pune, India, with branches worldwide from North America, Middle-East to South East Asia

Contact Us!!!

contact@unionsystechnologies.com

Oracle Technologies

Wednesday, 31 December 2014

Adop utility in oracle apps R12.2

adop (Online Patching) Patching while End Users are
accessing Applications. EBS R12.2 onwards all patching operations
are online (system remains available during patching) unlike previous
versions where system was unavailable for users during patching (Maintenance
Mode).

A: Run Edition of database objects: used by online
users and is not changed by patching

B: Patch Edition of database objects: used by patching
tool and do not affect the running application

Note: There is third edition called Old Edition.

Previous Run Edition is marked as Old
Edition. During full Cleanup Operation, adop removes Old Edition.

Oracle provides this online patching system by using two Apps
tier file systems named fs1 and fs2 in Application
tier, by using edition based redefinition feature of 11gR2 RDBMS in
Database Tier.

Phases in adop

Normally, we have 5 phases when applying EBS patch. These phases
are prepare, apply, finalize, cutover and cleanup.

Phases must be specified in the order they run, which is the
order listed.

Prepareà Prepare the instance for online patching.

ApplyàApply patches to the patch edition.

FinalizeàReady the instance for cutover.

CutoveràPromote the patch edition to become the new run edition.

CleanupàDrop obsolete objects and seed data from old editions.

We start with prepare for synchronizing the
patch file system for Applications and the patch version for db tier. Then we
continue with apply phase. This phase is actual phase that the
patch operations are done. adop uses patch file system to upload new apps tier
files and uses the patch edition of the database to take db actions.
After apply we continue with adop=finalize. In this phase,
application and database specific actions such as compilation takes place.

So those 3 phases require no downtime, but the next phase which
is called cutover needs a little downtime. It is automatic
though. In cutover phase, adop switches the patched file system and db edition
with the current/run file system and db edition. That's why Application Tier
components are restarted in this phase. Downtime is coming from restarting the
components.
The last phase is cleanup phase. It is self explanatory. In
this phase ADOP starts cleaning up the old editions.