How do I apply multiple patches using Adop?

Applying multiple patches using Adop (Application Downtime Optimization) in Oracle E-Business Suite involves a structured sequence of commands that ensure the integrity and continuity of your system. The core concept revolves around specifying all desired patch numbers in a single apply command.

How Do I Apply Multiple Patches Using Adop?

To apply multiple patches using Adop, you combine the patch numbers into a single comma-separated list within the adop phase=apply command. This process follows a well-defined lifecycle, ensuring efficient and minimized downtime for your Oracle E-Business Suite environment.

Understanding Adop and Its Patching Phases

Adop facilitates online patching, allowing many patching operations to occur while the application remains available to users. It organizes patching into distinct phases, each serving a specific purpose in the maintenance cycle.

The Adop utility operates through a series of phases, and to apply multiple patches, you will orchestrate these phases systematically.

The Adop Patching Cycle for Multiple Patches

The standard Adop patching cycle, modified for applying several patches, includes the following sequential phases:

1. Prepare Phase

The prepare phase sets up the file system for applying patches. It synchronizes the run file system with the patch file system, making it ready for new changes. This is the initial step for any patching cycle.

• Command: adop phase=prepare
• Purpose: Prepares the patch file system by synchronizing it with the current run file system. This ensures a clean slate for applying patches.

2. Apply Phase (Applying Multiple Patches)

The apply phase is where the actual patches are merged into the patch file system. For multiple patches, you provide a comma-separated list of patch numbers. This is a critical step where all specified patches are applied concurrently or sequentially by the adop utility.

• Command: adop phase=apply patches=<patch_number1,<patch_number2 workers=<number_of_worker
• Purpose: Applies the specified patches to the patch file system.
• Example for multiple patches: If you want to apply Patch A (e.g., 12345) and Patch B (e.g., 67890), the command would look like:
  adop phase=apply patches=12345,67890 workers=8
  (Replace 12345,67890 with your actual patch numbers and 8 with your desired number of workers.)
• Practical Insight: The workers parameter determines the number of parallel processing threads, significantly impacting the patch application speed. Choosing an optimal number based on your server's CPU and I/O capacity is crucial.

3. Finalize Phase

The finalize phase performs tasks to prepare for the cutover, such as compiling invalid objects and generating necessary files. This phase can often run automatically after the apply phase if not explicitly called.

• Command: adop phase=finalize workers=<number_of_worker
• Purpose: Completes compilation and other finalization steps before the system switches to the patched environment. This phase is often called automatically.

4. Cutover Phase

The cutover phase is the downtime window where the system switches from the old run file system to the newly patched file system. Users cannot access the application during this phase.

• Command: adop phase=cutover workers=<number_of_worker
• Purpose: Performs the actual switch, making the newly patched file system the active run file system. This requires a brief downtime.

5. Cleanup Phase

The cleanup phase removes obsolete objects and data from the old file system to free up space. This phase is typically called automatically after a successful cutover.

• Command: adop phase=cleanup
• Purpose: Removes obsolete data and objects from the previous patch edition, freeing up disk space. This phase is often called automatically.

Key Considerations for Multiple Patches

• Patch Compatibility: Always verify the compatibility and prerequisite patches for all patches you intend to apply together. Oracle typically provides a "Readme" file with each patch detailing these requirements.
• Order of Application: While Adop handles dependencies to some extent, it's generally recommended to group related patches or apply patches with specific prerequisites together, or in a logical order if dependencies are complex.
• Error Handling: If an error occurs during the apply phase, Adop provides options to restart or skip the problematic patch. Review the Adop logs thoroughly to diagnose and resolve issues.
• Downtime Planning: Even with online patching, the cutover phase requires downtime. Plan this window carefully, considering the size and number of patches, as well as your organizational needs.

Summary of Adop Commands for Multiple Patches

Here's a quick reference table for the essential Adop commands when applying multiple patches:

By following these steps and utilizing the patches= argument within the adop phase=apply command, you can efficiently apply multiple patches to your Oracle E-Business Suite environment, leveraging Adop's capabilities for minimized downtime.