Since last week, Release Update 07 for Oracle Enterprise Manager 24ai has been published. Finding it, however, was a bit challenging at first. The MOS note “Overview of the Enterprise Manager Proactive Patch Program” (previously 822485.1) was still not updated, and search queries like “RU07” or “Enterprise Manager RU” returned no useful results in My Oracle Support prior to the platform’s maintenance window this weekend.

Fortunately, this has now been corrected, and the RU appears in search results as expected. I’m excited to explore what has changed - especially in the AskEM functionality.

For other new features delivered in this RU, click here: https://docs.oracle.com/en/enterprise-manager/cloud-control/enterprise-manager-cloud-control/24.1/emcon/new-features-release.html#GUID-B9DC7492-9BB4-4D66-97AB-7509EE119068

Search for this note in My Oracle Support platform: Enterprise Manager 24ai Main Release Update List (Includes Plug-ins) - KA1271.

The Oracle Management Service (OMS) patch can be applied using the Traditional Patching method or, if your environment includes multiple Oracle Management Servers, the Zero Downtime Patching (ZDT) method.
Interestingly, the ZDT workflow - deploy and apply - also works in environments with a single OMS, even though it is primarily designed for multi-OMS setups. For specific steps and requirements, refer to the patch README. Or, do it offline.

For updating the Management Agent, use the Patches & Updates feature within Oracle Enterprise Manager. And follow-up as example with Golden Images.

Patch Numbers

OMSPatcher Version

Ensure, OMSPatcher is on version 13.9.24.9.0 . If not, follow My Oracle Support note 3080815.1 to update OMSPatcher. Example for my EM24ai installation on Oracle Linux 9:

--set ORACLE_HOME
export ORACLE_HOME=/u01/app/oracle/middleware/oms_home

--verify version
/u01/app/oracle/middleware/oms_home/OMSPatcher/omspatcher version
OMSPatcher Version: 13.9.24.8.0
OPlan Version: 12.2.0.1.16
OsysModel build: Tue Apr 28 18:16:31 PDT 2020

OMSPatcher succeeded.

--go to directory and save old content
cd /u01/app/oracle/middleware/oms_home
mv OMSPatcher OMSPatcher_old

--copy archive file from new release to current location
cp /u01/app/oracle/stage/p19999993_241000_Generic.zip .
unzip p19999993_241000_Generic.zip 
rm p19999993_241000_Generic.zip

--verify version
/u01/app/oracle/middleware/oms_home/OMSPatcher/omspatcher version
OMSPatcher Version: 13.9.24.9.0
OPlan Version: 12.2.0.1.16
OsysModel build: Tue Apr 28 18:16:31 PDT 2020

OMSPatcher succeeded.

Apply Oracle Enterprise Manager 24ai Release 1 Update 7 - ZDT Method

The patch has been successfully transferred to the target server and placed in the staging directory under /u01. After extraction, the patch files are ready for deployment.

To streamline the process, I use a predefined properties file, which eliminates the need to manually enter WebLogic credentials, URLs, and other configuration parameters during installation.

How to create the properties file? I described the steps in this post: https://www.martinberger.com/2025/04/24ai-enterprise-manager-cloud-control-base-platform-periodic-release-update-ru-01-on-the-way-to-zdt/.

Set ORACLE_HOME and go to directory

export ORACLE_HOME=/u01/app/oracle/middleware/oms_home
cd /u01/app/oracle/stage/38532004

Analyze

$ORACLE_HOME/OMSPatcher/omspatcher deploy -analyze -property_file /u01/app/oracle/middleware/wlskeys/24ai.properties

Deploy

$ORACLE_HOME/OMSPatcher/omspatcher deploy -property_file /u01/app/oracle/middleware/wlskeys/24ai.properties

Update

$ORACLE_HOME/OMSPatcher/omspatcher update -property_file /u01/app/oracle/middleware/wlskeys/24ai.properties

Status

In my single‑OMS setup, the patching process took about one and a half hours.

$ORACLE_HOME/OMSPatcher/omspatcher status
OMSPatcher Automation Tool
Copyright (c) 2024, Oracle Corporation.  All rights reserved.

OMSPatcher version : 13.9.24.9.0
OUI version        : 13.9.4.0.0
Running from       : /u01/app/oracle/middleware/oms_home
Log file location  : /u01/app/oracle/middleware/oms_home/cfgtoollogs/omspatcher/opatch2026-01-16_21-03-13PM_1.log

Patch ID: 38532004
Action: Update
Deployment Mode: Rapid Platform Update
Update Status: Successful
Deploy Status: Completed
Start Time: Fri Jan 16 20:19:02 CET 2026
End Time: Fri Jan 16 20:52:28 CET 2026
Deploy Execution Time: 58 Minutes
Update Execution Time: 33 Minutes

OMSPatcher succeeded.

After patching, the OMS starts up normally, and no additional commands are required.

Verification