Since April 19th the first release update (RU) for Oracle Enterprise Manager 24ai is ready to apply. This release update contains several bug fixes and prepares the environment for later Zero Downtime Patching (ZDT). The new architecture with additional WebLogic servers is already here and installed. In this blog post I show you how to apply the first release update.
My Setup is a Single-OMS with a 19.24 repository running on Oracle Linux 9. The Oracle Enterprise Manager 24ai repository is configured traditional by SYS permissions (non-SYS is possible now) and the schema name is SYSMAN. Steps followed the README from the patch and the Administrator Guide in Section Zero Downtime Patching (Online patching) .
A note about Zero Downtime Patching (I expected to use this method from now): According the release notes, ZDT starts after this first patch: This feature is available starting with Oracle Enterprise Manager 24ai Release 1 Update 1 (24.1.0.1). In my trial, the ZDT magic did not happen, starting means it should work with the next release update, 24.1.0.2. Actually we still have downtime when patching the Oracle Enterprise Manager OMS component. Or did I miss anything? Let me know if it worked for you.
A few log files were shortened for readability, these lines are marked by a <REDACTED> tag, if you want to see the complete output, just contact me via Bluesky (martinberger.bsky.social) or LinkedIn (martin-berger-ch).
My Oracle Support Notes and Documents
- EM 24ai: How To Upgrade Enterprise Manager 24.1 OMSPatcher Utility to the Latest Version (Doc ID 3080815.1)
- EM 24ai: OMSPatcher Best Practice: How to Avoid Patching Operation from Getting Timed-out or Aborted? (Doc ID 3080816.1)
- 24ai Enterprise Manager Cloud Control Base Platform Periodic Release Update (RU) 01 (Doc ID 3050841.1)
- Enterprise Manager 24ai Main Release Update List (Includes Plug-ins) (Doc ID 3050869.2)
- EM 24ai: System Architecture Explained (Doc ID 3042864.1)
- Overview of the Enterprise Manager Proactive Patch Program (Doc ID 822485.1)
- Release Schedule of Enterprise Manager Releases and Patchsets (24ai, 13c, 12c) (Doc ID 793512.1)
- Patch 37466946: Oracle Enterprise Manager 24c Release 1 Update 1 ( 24.1.0.1 ) for Oracle Management Service
Numbers and Directories
| My ORACLE_HOME | /u01/app/oracle/middleware/oms_home/ |
| My Stage Directory | /u01/app/oracle/stage |
| OMSPatcher Patch Number | 19999993 |
| OMS Release Update (RU) 01 Patch Number | 37466946 |
| Agent Release Update (RU) 01 Patch Number | 37466937 |
| Hostname | trinity.internal |
Prerequisites
- Patch the OMSPatcher to version 13.9.24.2.0
- Creating a Property File
- Extract the patch 37466946 locally
- Install mandatory one-off patch bundled with OMSPatcher utility
- Run OMSPatcher for analysis with omspatcher deploy -analyze
- Run OMSPatcher with omspatcher deploy
- Run update phase patching with omspatcher update
- Execute post-checks
- Update monitoring agents
Patch the OMSPatcher to version 13.9.24.2.0
OMSPatcher is downloaded from My Oracle Support and transferred to the local stage directory /u01/app/oracle/stage. Check the current version, set ORACLE_HOME first, rename the old OMSPatcher directory in ORACLE_HOME, and extract the new version. All steps are execute as OS user oracle.
--set ORACLE_HOME
$ export ORACLE_HOME=/u01/app/oracle/middleware/oms_home
--check current version 13.9.24.1.0
$ $ORACLE_HOME/OMSPatcher/omspatcher version
OMSPatcher Version: 13.9.24.1.0
OPlan Version: 12.2.0.1.16
OsysModel build: Tue Apr 28 18:16:31 PDT 2020
--rename existing directory
$ cd $ORACLE_HOME
$ mv OMSPatcher OMSPatcher_old
--copy new OMSPatcher file to ORACLE_HOME and extract
$ cp /u01/app/oracle/stage/p19999993_141000_Generic.zip .
$ unzip p19999993_141000_Generic.zip
-- verify new version
$ $ORACLE_HOME/OMSPatcher/omspatcher version
OMSPatcher Version: 13.9.24.2.0
OPlan Version: 12.2.0.1.16
OsysModel build: Tue Apr 28 18:16:31 PDT 2020
OMSPatcher succeeded.Creating a Property File
The automated patching functionality using omspatcher requires the WebLogic Administration Server URL and credentials for operations. To avoid repeatedly entering credentials, update the property file, as OPatch supports input through this method. How to create the required files is included in the appendix of patch readme.
Attention: Take care about the location for the files as they contain sensitive information.
--create directory for keys and properties
$ mkdir /u01/app/oracle/middleware/wlskeys
$ cd u01/app/oracle/middleware/wlskeys
--create keyfile and configfile by wlskeys.sh, check for proper WLS URL, username and password your are prompted
$ $ORACLE_HOME/OMSPatcher/wlskeys/createkeys.sh -oh $ORACLE_HOME -location /u01/app/oracle/middleware/wlskeys
The oraclehome passed is valid.
The wls url is t3s://trinity.internal:7102
Please enter weblogic admin server username : weblogic
Please enter weblogic admin server password :
The cfgFile is /u01/app/oracle/middleware/wlskeys/config
The keyFile is /u01/app/oracle/middleware/wlskeys/key
Initializing WebLogic Scripting Tool (WLST) ...
<REDACTED>
<REDACTED>
<REDACTED>
Creating the key file can reduce the security of your system if it is not kept in a secured location after it is created. Creating new key...
The username and password that were used for this WebLogic Server connection are stored in /u01/app/oracle/middleware/wlskeys/config and /u01/app/oracle/middleware/wlskeys/key.
Disconnected from weblogic server: EMGC_ADMINSERVER
0
User configuration file created: /u01/app/oracle/middleware/wlskeys/config
User key file created: /u01/app/oracle/middleware/wlskeys/key
'createkeys' succeeded.
$ cd /u01/app/oracle/middleware/wlskeys
--verify created files
$ ll
-rw-r-----. 1 oracle oinstall 234 Apr 16 20:24 config
-rw-r-----. 1 oracle oinstall 80 Apr 16 20:24 key
--create the property file with this content - adapt path and user settings according your environment
$ cat 24ai.properties
AdminServerURL=t3s://trinity.internal:7102
AdminConfigFile=/u01/app/oracle/middleware/wlskeys/config
AdminKeyFile=/u01/app/oracle/middleware/wlskeys/key
dbUser=sys
dbPassword=<REDACTED>
Sysman_pwd=<REDACTED>
Extract the patch 37466946 locally
The Release Update 01 patch file is downloaded from My Oracle Support and transferred to the local stage directory /u01/app/oracle/stage. Extract the file in the stage directory.
--check for file availability
$ cd /u01/app/oracle/stage
$ ls -la
total 1307796
drwxr-xr-x. 2 oracle oinstall 42 Apr 22 12:00 .
drwxr-xr-x. 13 oracle oinstall 174 Feb 17 08:57 ..
-rw-r--r--. 1 oracle oinstall 1339180890 Apr 22 11:59 p37466946_241000_Generic.zip
--extract file
$ unzip p37466946_241000_Generic.zipInstall mandatory one-off patch bundled with OMSPatcher utility
This one-off patch prepares the Oracle Management Server for the new Zero Downtime Patching functionality and is mandatory. If you run the omspatcher deploy -analyze command and the patch is not applied, you get an information and the command how to execute.
Attention: The Oracle Enterprise Manager 24ai components are restarted during this process.
--run omspatcher deploy -analyze and get the command to patch omspatcher
$ $ORACLE_HOME/OMSPatcher/omspatcher deploy -analyze -property_file /u01/app/oracle/middleware/wlskeys/24ai.properties
OMSPatcher Automation Tool
Copyright (c) 2024, Oracle Corporation. All rights reserved.
OMSPatcher version : 13.9.24.2.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/opatch2025-04-16_20-59-38PM_1.log
Before proceeding with the release update patch, you must first apply the mandatory one-off patch bundled with the OMSPatcher utility by following these steps:
1. Ensure that you shutdown the OMS by running the following command::
emctl stop oms.
Note: In case of a multi-OMS environment, shut down all the OMSes. .
2. Apply the Mandatory One-Off Patch:
Run the following command: /u01/app/oracle/middleware/oms_home/OMSPatcher/omspatcher apply /u01/app/oracle/middleware/oms_home/OMSPatcher/patches/37703206 -oh /u01/app/oracle/middleware/oms_home
3. Multi-OMS Environments:
The patching process will automatically submit a job to patch all additional OMS instances.
Once the mandatory one-off patch has been successfully applied to all OMS instances, proceed with applying the release update patch in Zero Downtime (ZDT) patching mode.
OMSPatcher log file: /u01/app/oracle/middleware/oms_home/cfgtoollogs/omspatcher/37466946/omspatcher_2025-04-16_21-00-06PM_analyze.log
Enter SYS or Non-SYS (Admin User) username: SYS
Enter 'sys' password :
Checking if current repository database is a supported version
Current repository database version is supported
Prereq "checkComponents" for patch 37465460 passed.
<REDACTED>
<REDACTED>
<REDACTED>
The following sub-patches are not needed by any component installed in the OMS system:
37465809,37465890,37465499
Log file location: /u01/app/oracle/middleware/oms_home/cfgtoollogs/omspatcher/37466946/omspatcher_2025-04-16_21-00-06PM_analyze.log
OMSPatcher succeeded.
--apply omspatcher patch
$ $ORACLE_HOME/OMSPatcher/omspatcher apply $ORACLE_HOME/OMSPatcher/patches/37703206 -oh $ORACLE_HOME
OMSPatcher Automation Tool
Copyright (c) 2024, Oracle Corporation. All rights reserved.
OMSPatcher version : 13.9.24.2.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/opatch2025-04-18_20-36-20PM_1.log
OMSPatcher log file: /u01/app/oracle/middleware/oms_home/cfgtoollogs/omspatcher/37703206/omspatcher_2025-04-18_20-36-32PM_apply.log
Please enter OMS weblogic admin server URL(t3s://trinity.internal:7102):>
Please enter OMS weblogic admin server username(weblogic):>
Please enter OMS weblogic admin server password:>
<REDACTED>
<REDACTED>
<REDACTED>
To continue, OMSPatcher will do the following:
[Patch and deploy artifacts] : Apply sub-patch(es) [ 37609320 37581979 ]
Apply sub-patch(es) [ 37609320 37581979 ]
Apply RCU artifact with patch "/u01/app/oracle/middleware/oms_home/.omspatcher_storage/37609320_Mar_14_2025_11_13_30/original_patch"
Do you want to proceed? [y|n]
y
User Responded with: Y
Stopping all the services on primary OMS.....
Please monitor log file: /u01/app/oracle/middleware/oms_home/cfgtoollogs/omspatcher/2025-04-18_20-41-14PM_SystemPatch_37703206_8/stop_oms_all_2025-04-18_20-41-14PM.log
Stopping the Central agent .....
<REDACTED>
<REDACTED>
<REDACTED>
The job_queue_processes parameter is set to 0 in the repository database. Resetting the job_queue_processes parameter to its original value 80 in the repository database to start the OMS.
Registering the end OP ......
DB user 'sys' is allowed to perform endOP patching operation.
Running the post apply sql .....
Starting the oms
Please monitor log file: /u01/app/oracle/middleware/oms_home/cfgtoollogs/omspatcher/2025-04-18_20-45-13PM_SystemPatch_37703206_21/start_oms_2025-04-18_20-45-13PM.log
<REDACTED>
<REDACTED>
<REDACTED>
Log file location: /u01/app/oracle/middleware/oms_home/cfgtoollogs/omspatcher/37703206/omspatcher_2025-04-18_20-36-32PM_apply.log
OMSPatcher succeeded.
--verify all components are up and running, tail on provided monitoring logfile
$ tail -f $ORACLE_HOME/cfgtoollogs/omspatcher/2025-04-18_20-45-13PM_SystemPatch_37703206_21/start_oms_2025-04-18_20-45-13PM.log
[Apr 18, 2025 8:45:13 PM] Oracle Enterprise Manager 24ai Release 1
[Apr 18, 2025 8:45:13 PM] Copyright (c) 1996, 2024 Oracle Corporation. All rights reserved.
[Apr 18, 2025 8:45:14 PM] Starting Oracle Management Server...
[Apr 18, 2025 8:48:17 PM] WebTier Successfully Started
[Apr 18, 2025 8:48:24 PM] Oracle Management Server Successfully Started
[Apr 18, 2025 8:48:26 PM] Oracle Management Server is Up
[Apr 18, 2025 8:48:26 PM] JVMD Engine is UpRun OMSPatcher for analysis with omspatcher deploy -analyze
With the -analyze flag, OMSPatcher verifies if the existing setup is ready for patching or reports any missing components or one-off patches. Check the output and provided logfiles. Use the property_file to avoid typing URLs and passwords. There is a logfile to control the start of the Oracle Enterprise Manager components like JVMD, WebTier etc.
-- run omspatcher deploy -analyze
$ $ORACLE_HOME/OMSPatcher/omspatcher deploy -analyze -property_file /u01/app/oracle/middleware/wlskeys/24ai.properties
OMSPatcher Automation Tool
Copyright (c) 2024, Oracle Corporation. All rights reserved.
OMSPatcher version : 13.9.24.2.0
OUI version : 13.9.4.0.0
Running from : /u01/app/oracle/middleware/oms_home
<REDACTED>
<REDACTED>
<REDACTED>
Configuration Validation: Success
<REDACTED>
<REDACTED>
<REDACTED>
Complete Summary
================
All log file names referenced below can be accessed from the directory "/u01/app/oracle/middleware/oms_home/cfgtoollogs/omspatcher/2025-04-16_20-59-38PM_SystemPatch_37466946_1"
Prerequisites analysis summary:
-------------------------------
The following sub-patch(es) are applicable:
Featureset Sub-patches Log file
---------- ----------- --------
oracle.sysman.top.oms 37465460,37465562,37465480,37465938,37465857,37465903 37465460,37465562,37465480,37465938,37465857,37465903_opatch2025-04-16_21-01-56PM_2.log
oracle.sysman.top.zdt 37519950 37519950_opatch2025-04-16_21-03-24PM_2.log
The following sub-patches are not needed by any component installed in the OMS system:
37465809,37465890,37465499
Log file location: /u01/app/oracle/middleware/oms_home/cfgtoollogs/omspatcher/37466946/omspatcher_2025-04-16_21-00-06PM_analyze.log
OMSPatcher succeeded.Run OMSPatcher with omspatcher deploy
After the successful check, the environment is ready to deploy the Release Update (RU) 01. Run this command for deploy phase patching.
-- run omspatcher deploy
$ $ORACLE_HOME/OMSPatcher/omspatcher deploy -property_file /u01/app/oracle/middleware/wlskeys/24ai.properties
OMSPatcher Automation Tool
Copyright (c) 2024, Oracle Corporation. All rights reserved.
OMSPatcher version : 13.9.24.2.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/opatch2025-04-18_20-52-25PM_1.log
Repository Create Utility (RCU) component patch 37609320 exist in the current Oracle Home.
OMSPatcher log file: /u01/app/oracle/middleware/oms_home/cfgtoollogs/omspatcher/37466946/omspatcher_2025-04-18_20-52-53PM_apply.log
<REDACTED>
<REDACTED>
<REDACTED>
Prereq "checkComponents" for patch 37465480 passed.
Prereq "checkComponents" for patch 37465903 passed.
Prereq "checkComponents" for patch 37519950 passed.
The Clonehome does not exist or is not a vaild one. Creating one now
Clone home creation started -- Start Time(2025-04-18_20-54-23)
Creating the home for the patching -- Start Time (2025-04-18_20-54-23)
Copy the bits from /u01/app/oracle/middleware/oms_home to /u01/app/oracle/middleware/cloneOMSHome_24100 -- Start Time(2025-04-18_20-54-23)
.Copy the bits from /u01/app/oracle/middleware/ext_oms_home to /u01/app/oracle/middleware/cloneExtOMSHome_24100 -- Start Time(2025-04-18_20-54-23)
....................................................
Completed the bits copy to /u01/app/oracle/middleware/cloneExtOMSHome_24100 -- End Time(2025-04-18_20-54-40)
..............
................................................................................................
Completed the bits copy to /u01/app/oracle/middleware/cloneOMSHome_24100 -- End Time(2025-04-18_20-56-57)
Completed creating clone home /u01/app/oracle/middleware/cloneOMSHome_24100 -- End Time(2025-04-18_20-56-59)
Prereq "checkComponents" for patch 37465460 passed.
Prereq "checkComponents" for patch 37465938 passed.
Prereq "checkComponents" for patch 37465562 passed.
Prereq "checkComponents" for patch 37465857 passed.
<REDACTED>
<REDACTED>
<REDACTED>
Apply RCU artifact with patch "/u01/app/oracle/middleware/cloneOMSHome_24100/.omspatcher_storage/37465903_Apr_9_2025_21_26_16/original_patch";
Register MRS artifact "omsPropertyDef";
Register MRS artifact "targetType";
Register MRS artifact "default_collection";
Register MRS artifact "jobTypes";
Register MRS artifact "systemStencil";
Register MRS artifact "discovery";
Register MRS artifact "namedQuery";
Register MRS artifact "storeTargetType";
Register MRS artifact "swlib";
Register MRS artifact "gccompliance"
Do you want to proceed? [y|n]
Could not recognize input. Please re-enter.
y
User Responded with: Y
Creating the edition in the repository .....
<REDACTED>
<REDACTED>
<REDACTED>
Updating repository with RCU reference file "/u01/app/oracle/middleware/cloneOMSHome_24100/.omspatcher_storage/37465480_Apr_9_2025_21_25_33/original_patch" for plugin home "/u01/app/oracle/middleware/cloneOMSHome_24100/plugins/oracle.sysman.emas.oms.plugin_24.1.1.0.0"
Updating repository with RCU reference file "/u01/app/oracle/middleware/cloneOMSHome_24100/.omspatcher_storage/37465903_Apr_9_2025_21_26_16/original_patch" for plugin home "/u01/app/oracle/middleware/cloneOMSHome_24100/plugins/oracle.sysman.si.oms.plugin_24.1.1.0.0"
Registering service "omsPropertyDef" with register file "/u01/app/oracle/middleware/cloneOMSHome_24100/sysman/metadata/omsProperties/definition/OMSPropDefinition.xml" for plugin id as "core"...
Please monitor log file: /u01/app/oracle/middleware/cloneOMSHome_24100/cfgtoollogs/omspatcher/2025-04-18_20-52-25PM_SystemPatch_37466946_1/emctl_register_omsPropertyDef_2025-04-18_21-19-02PM.log
<REDACTED>
<REDACTED>
<REDACTED>
Complete Summary
================
All log file names referenced below can be accessed from the directory "/u01/app/oracle/middleware/cloneOMSHome_24100/cfgtoollogs/omspatcher/2025-04-18_20-52-25PM_SystemPatch_37466946_1"
Copying the clone home logs to orginal home. From /u01/app/oracle/middleware/cloneOMSHome_24100/cfgtoollogs/omspatcher/2025-04-18_20-52-25PM_SystemPatch_37466946_1 To /u01/app/oracle/middleware/oms_home/cfgtoollogs/omspatcher/predowntime_2025-04-18_20-52-25PM_SystemPatch_37466946_1
Patching summary:
-----------------
Binaries of the following sub-patch(es) have been applied successfully:
Featureset Sub-patches Log file
---------- ----------- --------
oracle.sysman.top.zdt_24.1.0.0.0 37519950 37519950_opatch2025-04-18_21-09-36PM_4.log
oracle.sysman.top.oms_24.1.0.0.0 37465460,37465480,37465562,37465857,37465903,37465938 37465460,37465480,37465562,37465857,37465903,37465938_opatch2025-04-18_21-05-58PM_3.log
<REDACTED>
<REDACTED>
<REDACTED>
Log file location: /u01/app/oracle/middleware/oms_home/cfgtoollogs/omspatcher/37466946/omspatcher_2025-04-18_20-52-53PM_apply.log
OMSPatcher succeeded.
Run update phase patching with omspatcher update
During the deploy phase, two new directories called cloneExtOMSHome_24100 and cloneOMSHome_24100 are created and patched.
Attention: The Oracle Enterprise Manager 24ai components are restarted during this process.
--list directories in $ORACLE_HOME
$ cd $ORACLE_HOME
$ ll
total 20
drwxr-x---. 9 oracle oinstall 140 Apr 18 20:52 .
drwxr-xr-x. 13 oracle oinstall 174 Feb 17 08:57 ..
drwxr-x---. 19 oracle oinstall 4096 Apr 18 21:09 cloneExtOMSHome_24100
drwxr-x---. 84 oracle oinstall 4096 Apr 18 21:08 cloneOMSHome_24100
drwxr-x---. 19 oracle oinstall 4096 Apr 21 17:32 ext_oms_home
drwxr--r--. 4 oracle oinstall 37 Feb 17 09:59 gc_inst
drwxr-x---. 84 oracle oinstall 4096 Apr 21 17:32 oms_home
drwxr-x---. 75 oracle oinstall 4096 Apr 22 10:43 swlib
drwxr-xr-x. 2 oracle oinstall 54 Apr 16 20:59 wlskeysWith the update command, these directories will be used now.
-- run omspatcher update
$ $ORACLE_HOME/OMSPatcher/omspatcher update -property_file /u01/app/oracle/middleware/wlskeys/24ai.properties
OMSPatcher Automation Tool
Copyright (c) 2024, Oracle Corporation. All rights reserved.
OMSPatcher version : 13.9.24.2.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/opatch2025-04-18_21-29-59PM_1.log
OMSPatcher log file: /u01/app/oracle/middleware/oms_home/cfgtoollogs/omspatcher/37466946/omspatcher_2025-04-18_21-30-00PM_apply.log
[Info:Previous action was performed by user:'sys']
Enter 'sys' password :
Prereq "checkComponents" for patch 37465460 passed.
Prereq "checkComponents" for patch 37465938 passed.
Prereq "checkComponents" for patch 37465562 passed.
Prereq "checkComponents" for patch 37465857 passed.
Prereq "checkComponents" for patch 37465480 passed.
Prereq "checkComponents" for patch 37465903 passed.
Prereq "checkComponents" for patch 37519950 passed.
Running apply prerequisite checks for sub-patch(es) "37465460,37465562,37465480,37465938,37465857,37465903" and Oracle Home "/u01/app/oracle/middleware/oms_home"...
Sub-patch(es) "37465460,37465562,37465480,37465938,37465857,37465903" are successfully analyzed for Oracle Home "/u01/app/oracle/middleware/oms_home"
Running apply prerequisite checks for sub-patch(es) "37519950" and Oracle Home "/u01/app/oracle/middleware/ext_oms_home"...
Sub-patch(es) "37519950" are successfully analyzed for Oracle Home "/u01/app/oracle/middleware/ext_oms_home"
To continue, OMSPatcher will do the following:
[Patch and deploy artifacts] : Apply sub-patch(es) [ 37465460 37465480 37465562 37465857 37465903 37465938 37519950 ]
Apply sub-patch(es) [ 37465460 37465480 37465562 37465857 37465903 37465938 37519950 ]
Apply RCU artifact with patch "/u01/app/oracle/middleware/oms_home/.omspatcher_storage/37465562_Apr_9_2025_21_24_54/original_patch";
Register MRS artifact "assoc";
Register MRS artifact "procedures";
Register MRS artifact "EcmMetadataOnlyRegistration";
Register MRS artifact "namedQuery"
Stopping all the services on primary OMS.....
Please monitor log file: /u01/app/oracle/middleware/oms_home/cfgtoollogs/omspatcher/2025-04-18_21-37-00PM_SystemPatch_37466946_6/stop_oms_all_2025-04-18_21-37-00PM.log
Applying sub-patch(es) "37465460,37465480,37465562,37465857,37465903,37465938"
Please monitor log file: /u01/app/oracle/middleware/oms_home/cfgtoollogs/opatch/opatch2025-04-18_21-37-14PM_4.log
Applying sub-patch(es) "37519950"
Please monitor log file: /u01/app/oracle/middleware/ext_oms_home/cfgtoollogs/opatch/opatch2025-04-18_21-40-39PM_5.log
Starting the ADMIN .....
Please monitor log file: /u01/app/oracle/middleware/oms_home/cfgtoollogs/omspatcher/2025-04-18_21-40-55PM_SystemPatch_37466946_9/start_admin_2025-04-18_21-40-55PM.log
Configure API Gateway .....
Please monitor log file: /u01/app/oracle/middleware/oms_home/cfgtoollogs/omspatcher/2025-04-18_21-42-04PM_SystemPatch_37466946_10/config_apigateway_2025-04-18_21-42-04PM.log
Setting the job queue to zero in ZDT .....
Updating repository with RCU reference file "/u01/app/oracle/middleware/oms_home/.omspatcher_storage/37465562_Apr_9_2025_21_24_54/original_patch" for plugin home "/u01/app/oracle/middleware/oms_home/plugins/oracle.sysman.db.oms.plugin_24.1.1.0.0"
Registering service "assoc" with register file "/u01/app/oracle/middleware/oms_home/plugins/oracle.sysman.xa.oms.plugin_24.1.1.0.0/metadata/assoc/exa_infra_private_cloud_allowed_pairs.xml" for plugin id as "oracle.sysman.xa"...
Please monitor log file: /u01/app/oracle/middleware/oms_home/cfgtoollogs/omspatcher/2025-04-18_21-42-04PM_SystemPatch_37466946_10/emctl_register_assoc_2025-04-18_21-42-23PM.log
Registering service "procedures" with register file "/u01/app/oracle/middleware/oms_home/plugins/oracle.sysman.db.oms.plugin_24.1.1.0.0/metadata/procedures/BackupConfigAM.xml" for plugin id as "oracle.sysman.db"...
Please monitor log file: /u01/app/oracle/middleware/oms_home/cfgtoollogs/omspatcher/2025-04-18_21-42-04PM_SystemPatch_37466946_10/emctl_register_procedures_2025-04-18_21-42-33PM.log
Registering service "procedures" with register file "/u01/app/oracle/middleware/oms_home/plugins/oracle.sysman.xa.oms.plugin_24.1.1.0.0/metadata/procedures/ExaAHFScheduleAutorun.xml" for plugin id as "oracle.sysman.xa"...
Please monitor log file: /u01/app/oracle/middleware/oms_home/cfgtoollogs/omspatcher/2025-04-18_21-42-04PM_SystemPatch_37466946_10/emctl_register_procedures_2025-04-18_21-42-38PM.log
Registering service "EcmMetadataOnlyRegistration" with register file "/u01/app/oracle/middleware/oms_home/plugins/oracle.sysman.db.oms.plugin_24.1.1.0.0/metadata/snapshot/db_oracle_security_ecm_metadata.xml" for plugin id as "oracle.sysman.db"...
Please monitor log file: /u01/app/oracle/middleware/oms_home/cfgtoollogs/omspatcher/2025-04-18_21-42-04PM_SystemPatch_37466946_10/emctl_register_EcmMetadataOnlyRegistration_2025-04-18_21-42-42PM.log
Registering service "EcmMetadataOnlyRegistration" with register file "/u01/app/oracle/middleware/oms_home/plugins/oracle.sysman.xa.oms.plugin_24.1.1.0.0/metadata/snapshot/oracle_cloud_vm_cluster_ecm.xml" for plugin id as "oracle.sysman.xa"...
Please monitor log file: /u01/app/oracle/middleware/oms_home/cfgtoollogs/omspatcher/2025-04-18_21-42-04PM_SystemPatch_37466946_10/emctl_register_EcmMetadataOnlyRegistration_2025-04-18_21-42-47PM.log
Registering service "namedQuery" with register file "/u01/app/oracle/middleware/oms_home/sysman/metadata/namedQuery/core-uifwk-getDashboardPrivGrants.xml" for plugin id as "core"...
Please monitor log file: /u01/app/oracle/middleware/oms_home/cfgtoollogs/omspatcher/2025-04-18_21-42-04PM_SystemPatch_37466946_10/emctl_register_namedQuery_2025-04-18_21-42-50PM.log
Registering service "namedQuery" with register file "/u01/app/oracle/middleware/oms_home/plugins/oracle.sysman.db.oms.plugin_24.1.1.0.0/metadata/namedQuery/emdb-recoverycatalogs-configured-dbs.xml" for plugin id as "oracle.sysman.db"...
Please monitor log file: /u01/app/oracle/middleware/oms_home/cfgtoollogs/omspatcher/2025-04-18_21-42-04PM_SystemPatch_37466946_10/emctl_register_namedQuery_2025-04-18_21-42-54PM.log
Registering service "namedQuery" with register file "/u01/app/oracle/middleware/oms_home/plugins/oracle.sysman.xa.oms.plugin_24.1.1.0.0/metadata/namedQuery/ahf_management_named_query.xml" for plugin id as "oracle.sysman.xa"...
Please monitor log file: /u01/app/oracle/middleware/oms_home/cfgtoollogs/omspatcher/2025-04-18_21-42-04PM_SystemPatch_37466946_10/emctl_register_namedQuery_2025-04-18_21-42-57PM.log
Adding disable the jobs
Running recompile
Releasing the LCM Lock .....
Setting the job queue to zero in ZDT .....
Switching the edition in the repository .....
Setting the default edition for the batch1 .....
Running enable the jobs
Resetting the patching flag .....
Resetting the job queue process .....
The job_queue_processes parameter is set to 0 in the repository database. Resetting the job_queue_processes parameter to its original value 80 in the repository database to start the OMS.
Registering the end OP ......
DB user 'sys' is allowed to perform endOP patching operation.
Running the post apply sql .....
Starting the oms
Please monitor log file: /u01/app/oracle/middleware/oms_home/cfgtoollogs/omspatcher/2025-04-18_21-44-42PM_SystemPatch_37466946_32/start_oms_2025-04-18_21-44-42PM.log
Setting the zdt mode NORMAL
Please monitor log file: /u01/app/oracle/middleware/oms_home/cfgtoollogs/omspatcher/2025-04-18_21-47-18PM_SystemPatch_37466946_33/set-zdtmode_2025-04-18_21-47-18PM.log
Setting the default edition for the batch2 .....
Complete Summary
================
Patching summary:
-----------------
Binaries of the following sub-patch(es) have been applied successfully:
Featureset Sub-patches Log file
---------- ----------- --------
oracle.sysman.top.zdt_24.1.0.0.0 37519950 37519950_opatch2025-04-18_21-40-39PM_5.log
oracle.sysman.top.oms_24.1.0.0.0 37465460,37465480,37465562,37465857,37465903,37465938 37465460,37465480,37465562,37465857,37465903,37465938_opatch2025-04-18_21-37-14PM_4.log
The following sub-patches are not needed by any component installed in the OMS system:
37465809,37465890,37465499
Deployment summary:
-------------------
The following artifact(s) have been successfully deployed:
Artifacts Log file
--------- --------
SQL rcu_applypatch_original_patch_2025-04-18_21-42-11PM.log
MRS-assoc emctl_register_assoc_2025-04-18_21-42-23PM.log
MRS-procedures emctl_register_procedures_2025-04-18_21-42-33PM.log
MRS-procedures emctl_register_procedures_2025-04-18_21-42-38PM.log
MRS-EcmMetadataOnlyRegistration emctl_register_EcmMetadataOnlyRegistration_2025-04-18_21-42-42PM.log
MRS-EcmMetadataOnlyRegistration emctl_register_EcmMetadataOnlyRegistration_2025-04-18_21-42-47PM.log
MRS-namedQuery emctl_register_namedQuery_2025-04-18_21-42-50PM.log
MRS-namedQuery emctl_register_namedQuery_2025-04-18_21-42-54PM.log
MRS-namedQuery emctl_register_namedQuery_2025-04-18_21-42-57PM.log
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
The following patches could not be applied during OPatch execution:
**********************************************************************************
Patch Reason
********* *********
37465809 The Plugin or Core Component "oracle.sysman.emct.oms.plugin with version 24.1.1.0.0" for which the patch is intended is not deployed in your Enterprise Manager system.
37465890 The Plugin or Core Component "oracle.sysman.ssa.oms.plugin with version 24.1.1.0.0" for which the patch is intended is not deployed in your Enterprise Manager system.
37465499 The Plugin or Core Component "oracle.sysman.am.oms.plugin with version 24.1.1.0.0" for which the patch is intended is not deployed in your Enterprise Manager system.
37465809 The Plugin or Core Component "oracle.sysman.emct.oms.plugin with version 24.1.1.0.0" for which the patch is intended is not deployed in your Enterprise Manager system.
37465890 The Plugin or Core Component "oracle.sysman.ssa.oms.plugin with version 24.1.1.0.0" for which the patch is intended is not deployed in your Enterprise Manager system.
37465499 The Plugin or Core Component "oracle.sysman.am.oms.plugin with version 24.1.1.0.0" for which the patch is intended is not deployed in your Enterprise Manager system.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Log file location: /u01/app/oracle/middleware/oms_home/cfgtoollogs/omspatcher/37466946/omspatcher_2025-04-18_21-30-00PM_apply.log
OMSPatcher succeeded.Execute post-checks
Verify all components are up and running. Login into the Oracle Enterprise Manager 24ai and click on About Enterprise Manager, it shows now Enterprise Manager 24ai Release 1 Update 1.
Update monitoring agents
You can apply patch 37466937 Oracle Enterprise Manager 24c Release 1 Update 1 ( 24.1.0.1 ) for Oracle Management Agent by Enterprise Manager Patching and Provisioning (what I prefer) or manually with the agentpatcher command. Both methods are available in the readme file of the agent patch.
Summary
This was Release Update (RU) 01, all preparation steps to leverage the Zero Downtime Patching methods are completed. I have a single instance only, but the process was smooth. I am still missing AI functionalities, let’s see what the next Release Update 02 brings.