{"id":6401,"date":"2013-10-25T11:26:39","date_gmt":"2013-10-25T15:26:39","guid":{"rendered":"http:\/\/onlineappsdba.com\/?p=6401"},"modified":"2017-02-28T10:17:41","modified_gmt":"2017-02-28T14:17:41","slug":"adop-online-patching-cycle-in-oracle-apps-e-business-suite-r12-12-2-apps-dbas-must-read","status":"publish","type":"post","link":"https:\/\/onlineappsdba.com\/index.php\/2013\/10\/25\/adop-online-patching-cycle-in-oracle-apps-e-business-suite-r12-12-2-apps-dbas-must-read\/","title":{"rendered":"ADOP : Online Patching in Oracle Apps (E-Business Suite) R12 12.2 : Apps DBA’s Must Read"},"content":{"rendered":"

\"\"<\/a><\/p>\n

Last month I discussed about Oracle Application 12.2 Installation<\/a>, from this version ADPATCH<\/strong> is being replaced by ADOP<\/strong> (AD<\/strong> O<\/strong>nline P<\/strong>atching) to support Online Patching<\/strong> (Patching while End Users are accessing Applications<\/span>). This post covers, key points about Online Patching introduced in Oracle Applications 12.2<\/p>\n

If you want to learn more about Oracle E-Business Suite (Oracle Apps) 12.2, register here for \u00a0our<\/span> \u2013\u00a0\u00a0Oracle Apps DBA 12.2 Training<\/a>\u00a0(next batch starts on\u00a031st October, 2015)<\/p>\n

1.<\/strong> In Oracle Apps R 12.2 onwards all patching operations are online ( EBS system remains available to users during patching<\/span>) unlike previous versions where system is unavailable during patching (Maintenance Mode<\/span>)<\/p>\n

2.<\/strong> Online Patching uses Edition Based Redefinition<\/strong><\/a> (EBR) at Database Layer<\/strong> and Multiple File System<\/strong> at Application Tier<\/strong> level<\/p>\n

3.<\/strong> Edition Based Re-Definition provides two copies of Database object (schema) pre<\/strong> and post<\/strong> patch .<\/p>\n

a) Run Edition of database objects<\/strong> : used by online users and is not changed by patching<\/p>\n

b) Patch\u00a0Edition of database objects<\/strong> : used by patching tool and do not affect the running application<\/p>\n

Note<\/strong>: There is third edition (zero or more editions<\/strong>) called Old Edition<\/strong> – Patch Edition when prompted to Production i.e. <\/strong>new Run Edition<\/strong>, previous Run Edition<\/strong> is marked as Old Edition<\/strong>. Full Cleanup Operation (part of ADOP)\u00a0removes Old Edition (More on Cleanup Operation later<\/span>)<\/p>\n

 <\/p>\n

 <\/p>\n

\"\"<\/a><\/p>\n

3.<\/strong> In Oracle Applications 12.2 there are two file system<\/strong><\/p>\n

a) FS1<\/strong> : Production File System used by users<\/p>\n

b) FS2<\/strong> : Copy of production File System used by patching tools (adop : More on adop later<\/span>)<\/p>\n

Note<\/strong>: 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).<\/span> More on various\u00a0phases<\/strong> in AD Online Patching (adop) later<\/span>.<\/p>\n

Note:<\/strong> Third files system fs_ne<\/strong>\u00a0stores data on filesystem like log<\/strong>, out<\/strong>, data import\/export<\/strong> files<\/p>\n

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

5.<\/strong> Actual downtime during patching (ADOP)\u00a0is to switch users from pre-patched copy to patched copy.<\/p>\n

6.<\/strong> Online Patching Tool ADOP (AD Online Patching) now replaces adpatch in 12.2<\/p>\n

7.<\/strong> Phases on ADOP (replacement of ADPATCH) are Prepare -> Apply -> Finalize -> Cutover -> Cleanup (more on these phases later)<\/p>\n

8.<\/strong> Patching can be aborted any time before Cutover Phase (More on how to abort patching in ADOP later<\/span>)<\/p>\n

 <\/p>\n

I highly recommend below two resources to understand AD Online Patching<\/p>\n