Oracle Apps R12.2 Online Patching

Patching Oracle E-Business Suite Release 12.2 Technology Components

Oracle Homes

Oracle E-Business Suite Release 12.2 uses the following Oracle Homes:

  • Oracle Fusion Middleware
    • Oracle WebLogic Server (WLS) 10.3.6
    • OHS (WebTier) 11.1.1 and Oracle Common (Common Modules)
  • Application Server (OracleAS)
    • Forms and Reports 10.1.2
  • Oracle Database
    • Oracle Database Server 11.2

An overview of the process to follow when applying a technology patch within Oracle E-Business Suite. Download any required technology patches and unzip the contents. The patch contents may be unzipped into $NE_BASE/EBSapps/patch.

  1. Prepare the system for patching.
    • source <EBS_ROOT>/EBSapps.env run
    • adop phase=prepare
  2. Apply Fusion Middleware technology patches as needed to the appropriate Oracle Home under the Patch Edition.
    • source <EBS_ROOT>/EBSapps.env patch
    • Reference Table 1 below for details about patch application
  3. (Optional) Apply any Oracle E-Business Suite patches planned for this patching cycle
    • adop phase=apply patches=<patch_list>
  4. After all patches have been successfully applied, complete the patching cycle.
    • adop phase=finalize
    • adop phase=cutover
    • source <EBS_ROOT>/EBSapps.env run
    • adop phase=cleanup
  5. To complete the process and synchronize the technology level between patch and run f/s.
    • adop phase=fs_clone

 

Prepare:  Copies the production application code, which in turn creates so called patch edition. During this stage, patch edition and the actual run edition of the file systems are synchronized. It’s in a way easier to sync the patch and run edition. But becomes more complicated during the database’s prepare phase. Even in database, the ADOP process creates a patch version. Here, code objects in the patch edition got just pointers to the actual run edition. Interestingly, none of the storage objects (tables, indexes, etc.) are not copied though.

Apply:  In this phase, ADOP applies one or more patches to the copy edition. It executes the patch drivers to the patch edition.
Finalize: This is the final online phase where ADOP process performs tasks such as compile invalid objects, pre-compute DDL to be run. Once this process is completed, the next phase ‘Cutover’ can be scheduled.

Cutover:  This is the phase that requires predictable downtime. Here the actual migration of run version to patch version in both file system and database occurs. A restart of middle-tier is required at this stage. Per Oracle, we still are able to perform certain patches in hotpatch mode that doesn’t require downtime. Details to follow upon further hands-on.

Cleanup:  Literally clean-up occurs after the users are back online. In this phase ADOP starts cleaning up the old editions to recover space.

ADOP’s Major capabilities are not limited to the following:

A patch cycle can be aborted any time before cutover phase.
As the new ADOP process maintains a copy of the file system, the size would absolutely double.
System and seed tablespaces would now require 100% more space.
You can have one instance top to point to multiple environments.

Nagulu Polagani

"We are all apprentices in a craft where no one ever becomes a master."