Patch Import and Installation

Patching is a three-step process*:

  1. Download patches from My Oracle Support (MOS): This step is performed through the My Oracle Support Plug-in within Oracle Enterprise Manager from the top-level menu, choose Enterprise > Provisioning and Patching > Patching & Updates.

    Select the Enterprise menu, Provisioning and Patching then Patching & Updates to download patches from My Oracle Support.
  2. Import the downloaded patches: This process allows you to import downloaded patches which are subsequently unpackaged into a format that is compatible with Enterprise Manager for Oracle Utilities's installation process.
  3. Install the imported patches: This process allows you to import downloaded patches and install them into a target environment, updating relevant files in $SPLEBASE. If you deploy manually to the web server, you must perform this step after the installation process completes.

Patch Import/Installation Notes

  • In addition to the procedures described in this topic, follow the steps in the Patching Prerequisite topic before installing patches in Enterprise Manager for Oracle Utilities Release 24.1.1.0.0 and later.

    Important: Installation of Service Packs for OUAF products is supported in this release. Review the document Whitepaper: Service Pack Compliance before installing any service pack to make sure the service pack is packaged in a compliant manner.
  • Read-write access to the download directory is required.
  • For patches containing single fixes and hot fixes: Application server patch components are installed using the standard patch install script. Database patch components are installed using a Java version of the standard CDXPatch.exe utility.
  • Patches containing service packs using the new SP model are now supported. These type of patches contain a file called Metadata.xml, which is used by the plug-in to install the service pack.
  • During patch installation and patch migration, the installation job copies the individual patch directories from the download staging directory to a directory on the target environment ($SPLEBASE/oem/patch/install/tmp/YYYY-MM-DD-HH-MI-SS). The subdirectories are sorted by install sequence, e.g., 001-gf, 002-gf, 003-sfs. The job output clearly states the directories from which patch installation occurs.
  • During service pack installation, make sure the service pack zip file is the sole content of the download directory.
  • During any installation process—service pack, single fixes, rollups—WebLogic environments are shut down automatically using the command-line utility spl.sh/spl.cmd. Non-WebLogic environments must be shut down manually.
  • Due to packaging differences, only standard single fixes, group fixes and service packs using the new service pack model are supported. An error is generated if you choose an old service pack or rollup for import, or if the single fix or group fix is packaged in a non-standard manner.