ADOP : Online Patching in Oracle Apps (E-Business Suite) R12 12.2 : Apps DBA’s Must Read

Last month I discussed about Oracle Application 12.2 Installation, from this version ADPATCH is being replaced by ADOP (AD Online Patching) to support Online Patching (Patching while End Users are accessing Applications). This post covers, key points about Online Patching introduced in Oracle Applications 12.2

If you want to learn more about Oracle E-Business Suite (Oracle Apps) 12.2, register here for  our –  Oracle Apps DBA 12.2 Training (next batch starts on 31st October, 2015)

1. In Oracle Apps R 12.2 onwards all patching operations are online ( EBS system remains available to users during patching) unlike previous versions where system is unavailable during patching (Maintenance Mode)

2. Online Patching uses Edition Based Redefinition (EBR) at Database Layer and Multiple File System at Application Tier level

3. Edition Based Re-Definition provides two copies of Database object (schema) pre and post patch .

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 (zero or more editions) called Old Edition – Patch Edition when prompted to Production i.e. new Run Edition, previous Run Edition is marked as Old Edition. Full Cleanup Operation (part of ADOP) removes Old Edition (More on Cleanup Operation later)



3. In Oracle Applications 12.2 there are two file system

a) FS1 : Production File System used by users

b) FS2 : Copy of production File System used by patching tools (adop : More on adop later)

Note: FS1 and FS2 can switch role i.e. FS2 will become production File system and FS1 will become File System for Patching at Cutover Phase of online patching (ADOP). More on various phases in AD Online Patching (adop) later.

Note: Third files system fs_ne stores data on filesystem like log, out, data import/export files

4. Patches are applied to copy of production environment (copy of code and NOT data) where as users access the original production environment (Patching applied is to file system and Patch Ediiton of database objects and not applicable to transactions tables/data in database)

5. Actual downtime during patching (ADOP) is to switch users from pre-patched copy to patched copy.

6. Online Patching Tool ADOP (AD Online Patching) now replaces adpatch in 12.2

7. Phases on ADOP (replacement of ADPATCH) are Prepare -> Apply -> Finalize -> Cutover -> Cleanup (more on these phases later)

8. Patching can be aborted any time before Cutover Phase (More on how to abort patching in ADOP later)


I highly recommend below two resources to understand AD Online Patching

Did you get a chance to download 6 Docs Every Apps DBA Must Read for EBS R12.2 ? If not, then get it now by clicking on link below.

6 docs every apps dba must read


If you need to learn more about Oracle Apps DBA (Architecture, Installation, WebLogic, Patching, Cloning and other maintenance tasks with the upgrade of Oracle E-Business Suite 12.2.0 to 12.2.4 then have a look at our  Oracle Apps DBA Training

Series Navigation<< Changes in Oracle E-Business Suite R12 12.2 from 12.0.x and 12.1.xInstall Oracle E-Business Suite 12.2 on Linux – Part I : Download, Stage & Start Oracle Apps 12.2 software installation >>

Share This Post with Your Friends over Social Media!

About the Author Atul Kumar

Oracle ACE, Author, Speaker and Founder of K21 Technologies & K21 Academy : Specialising in Design, Implement, and Trainings.

follow me on:

Leave a Comment:

Nishant says October 25, 2013

Thanks for the concise preview of ADOP.

abhi says May 19, 2014

thanks for the synopsis!!

abdul hameed says September 2, 2015

Hi Guru Ji,

Can you please explain once we apply patch in the patching file system, how to make it live.

Is the ADOP concept focusing on reduce down time or reducing time on maintaining a patching environment.

Thanks in Advance.

Abdul Hameed

    Atul Kumar says September 3, 2015

    @Abdul Hameed read more on adop options

    Finalize phase – Used to perform the final patching operations that can be executed while the application is still online:

    $ adop phase=finalize
    Cutover phase – Used to perform the transition to the patched environment:

    $ adop phase=cutover

    Q: Is the ADOP concept focusing on reduce down time or reducing time on maintaining a patching environment
    It’s same thing isn’t time, ADOP (compared to adpatch) helps in reducing downtime caused by applying apps patch

Farhan says October 12, 2015

Hi Atul,

To summarize can we follow below approach in Oracle EBS 12.2 for patch application

0. Source Environment of RUN filesystem (fs1 in my case)
1. Run adop phase=prepare (RUN Filesystem)
2. Source the Environment of PATCH filesystem (fs2 in my case)
3. Run adop phase=apply patches=xxxx (on fs2 i.e PATCH filesystem)
4. Run adop phase=finalize (on fs2 i.e PATCH filesystem)
5. Bring down the EBS (which is currently running on fs1 i.e RUN filesystem)
6. Run adop phase=cutover (on fs2 i.e PATCH filesystem)
7. Run adop phase=cleanup (on fs2 i.e PATCH filesystem)
8. Bring up Application on RUN filesystem again.

Farhan Shaikh | Oracle Apps DBA

Deven Singh says November 6, 2015

What is the difference between adpatch & adop?

This is asked in interview.

    Atul Kumar says November 12, 2015

    Both ars tools to path R12 apps , adpatch is for r12.0, 12.1 where as adop is new utility to patch 12.2+

syed omer says March 30, 2016

I want to join Oracle Apps DBA R12.2 Training. let me know

santosh says September 13, 2016

what are the objects covered/created in patch edition. Is it only the objects which are getting patched or all the code objects in database stored in patch edition?
pl answer it.

Add Your Reply