During Release 12.2 installation, Rapid Install will lay down two copies of the application tier file system. One of the copies will be labeled as the run file system, and the other as the patch file system. Subsequently, when a patch is applied, adop will:
- Synchronize the contents of the run file system to the patch file system. This happens during the prepare phase.
- Perform patching actions on the patch file system. This happens during the apply phase.
- Finally, during the cutover phase, the adop utility restarts the application tier services. The patch file system is then promoted to be the new run file system, and the old run file system becomes the patch file system for the next patching cycle.
Note that a third file system, the non-editioned file system (fs_ne), is created to store files containing data that is needed across all file systems, such as log files.
What are the phases that make up the Online Patching cycle?
The Online Patching cycle consists of the following phases:
- Prepare a virtual copy (patch edition) of the running application (run edition).
- Apply patches to the patch edition of the application.
- Finalize the system in readiness for the cutover phase.
- Cutover to the patch edition and make it the new run edition.
- Cleanup obsolete definitions or data to recover space.
What are the space requirements for Online Patching?
Space required on the application tier file system is approximately double that of Release 12.1.3, to support the dual file system architecture. In the database there must be sufficient space to hold a duplicate copy of any code, seed data or table columns that are patched. Refer to Oracle E-Business Suite Installation Guide: Using Rapid Install for additional guidance.
Oracle E-Business Suite Release 12.2: Online Patching FAQ (Doc ID 1583902.1)