Sunday, February 15, 2026

Upgrading Enterprise Manager Cloud Control from 13.5 to 24.1 - 2

This is the second post on upgrading EMCC from 13.5 to 24.1. The previous post mentioned pre-req tasks to be carried out before the installation. The approach used in this case consists of two phase. First phase installs the 24.1 binaries and patch them. The existing 13.5 EM could be up and running at this stage. The second phase is the actual configuration of 24.1 EM and upgrade of the schemas in the repository. Prior to the second phase the existing 13.5 EM and agents must be shutdown. This two phase approach reduces the total downtime needed for upgrading.
It is possible to run the upgrade either in GUI mode or silent mode using the softwareOnlyWithPlugins_upgrade.rsp extracted from the installers (refer KB621611). In this case the GUI was chosen. The 24ai installer requires considerable amount of temporary space. Usually taken from /tmp location. If there is not enough space then in the default location give an alertnative location as tmp. To start the binary installation execute the following
./em13500_linux64.bin -Djava.io.tmpdir=/opt/tmp
This will open the GUI. Select upgrade existing EM and under it select the option upgrade software only and configure later.

Skip the software update download.

The upgrade is done on a RHEL8 (4.18.0-553) but OUI is checking for UEK 5.4. This failure is ignoreable.

Give new locations for 24ai.

Give repository DB connection details

Ensure following DB pre-req succeeds.

Upgrade will take care of some plugin by upgrading or migrating them depending on availability.

Review Space and install location.

Click the upgrade button to begin the upgrade.

When the upgrade completes run the allroot.sh.
# /opt/company/app/software/em/middleware24/oms_home/allroot.sh

Starting to execute allroot.sh .........

Starting to execute /opt/company/app/software/em/middleware24/oms_home/root.sh ......
Check /opt/company/app/software/em/middleware24/oms_home/install/root_ip-172-31-8-174.eu-west-1.compute.internal_2026-01-27_13-32-17-025234174.log for the output of root script
Finished execution of  /opt/company/app/software/em/middleware24/oms_home/root.sh ......


Starting to execute /opt/company/app/software/em/agent24/agent_24.1.0.0.0/root.sh ......

Finished product-specific root actions.
/etc exist
/opt/company/app/software/em/agent24/agent_24.1.0.0.0
Finished execution of  /opt/company/app/software/em/agent24/agent_24.1.0.0.0/root.sh ......
Once the allroot.sh is run click the OK button. This will complete the install of binaries and give instructions on the next step which is to configure the setup but do not run the ConfigureGC.sh until the binaries are patched. Click the close button and commence the patching.

Update the OMSpatcher before the patchnig (refer KB371380). Current patch level (before the 24RU patch applied)
opatch lspatches
37103277;FMW Thirdparty Bundle Patch 12.2.1.4.240925
37096063;OSS 19C BUNDLE PATCH 12.2.1.4.241001
37035947;OWSM BUNDLE PATCH 12.2.1.4.240908
37028738;ADF BUNDLE PATCH 12.2.1.4.240905
36964687;WebCenter Core Bundle Patch 12.2.1.4.240819
36851321;RDA release 24.4-20241015 for OFM 12.2.1.4 SPB
36789759;FMW PLATFORM BUNDLE PATCH 12.2.1.4.240812
36316422;OPSS Bundle Patch 12.2.1.4.240220
34065178;One-off
30152128;One-off
26626168;One-off
1221423;Coherence Cumulative Patch 12.2.1.4.23
37033394;OHS (NATIVE) DB19C BUNDLE PATCH 12.2.1.4.240906
36615359;DATABASE RELEASE UPDATE 19.24.0.0.0 FOR FMW DBCLIENT
34809489;One-off
37087476;WLS PATCH SET UPDATE 12.2.1.4.240922
35965629;ADR FOR WEBLOGIC SERVER 12.2.1.4.0 CPU JAN 2024
Analyze the patch
$ omspatcher apply -analyze -bitonly -silent
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       : /opt/company/app/software/em/middleware24/oms_home
Log file location  : /opt/company/app/software/em/middleware24/oms_home/cfgtoollogs/omspatcher/opatch2026-01-27_15-17-25PM_1.log

OMSPatcher log file: /opt/company/app/software/em/middleware24/oms_home/cfgtoollogs/omspatcher/38532004/omspatcher_2026-01-27_15-18-00PM_analyze.log

WARNING: OMSPatcher has been invoked with bitonly option but the System patch provided has deployment metadata.
Invocation in bitonly mode will prevent OMSPatcher from deploying artifacts.

Do you want to proceed? [y|n]
Y (auto-answered by -silent)
User Responded with: Y


Prereq "checkComponents" for patch 38527741 passed.

Prereq "checkComponents" for patch 38527764 passed.

Prereq "checkComponents" for patch 38527785 passed.

Prereq "checkComponents" for patch 38527758 passed.

Prereq "checkComponents" for patch 38527802 passed.

Prereq "checkComponents" for patch 38527828 passed.

Running apply prerequisite checks for sub-patch(es) "38527741,38527764,38527785,38527758,38527802" and Oracle Home "/opt/company/app/software/em/middleware24/oms_home"...
Sub-patch(es) "38527741,38527764,38527785,38527758,38527802" are successfully analyzed for Oracle Home "/opt/company/app/software/em/middleware24/oms_home"

Running apply prerequisite checks for sub-patch(es) "38527828" and Oracle Home "/opt/company/app/software/em/middleware24/ext_oms_home"...
Sub-patch(es) "38527828" are successfully analyzed for Oracle Home "/opt/company/app/software/em/middleware24/ext_oms_home"


Complete Summary
================


All log file names referenced below can be accessed from the directory "/opt/company/app/software/em/middleware24/oms_home/cfgtoollogs/omspatcher/2026-01-27_15-17-25PM_SystemPatch_38532004_1"

Prerequisites analysis summary:
-------------------------------

The following sub-patch(es) are applicable:

             Featureset                                    Sub-patches                                                                         Log file
             ----------                                    -----------                                                                         --------
  oracle.sysman.top.oms   38527741,38527764,38527785,38527758,38527802   38527741,38527764,38527785,38527758,38527802_opatch2026-01-27_15-19-04PM_2.log
  oracle.sysman.top.zdt                                       38527828                                       38527828_opatch2026-01-27_15-21-08PM_2.log


The following sub-patches are not needed by any component installed in the OMS system:
38527775,38527794,38527769,37616371,38527807,37990627


The following sub-patches are already applied to the OMS system:
38154809



--------------------------------------------------------------------------------
The following warnings have occurred during OPatch execution:
1)  OMSPatcher has been invoked with bitonly option but the System patch provided has deployment metadata.
Invocation in bitonly mode will prevent OMSPatcher from deploying artifacts.
2)  Sub-patch "38154809" skipped as it is already been applied to the "OMS" system.
--------------------------------------------------------------------------------
Log file location: /opt/company/app/software/em/middleware24/oms_home/cfgtoollogs/omspatcher/38532004/omspatcher_2026-01-27_15-18-00PM_analyze.log

OMSPatcher succeeded.

Apply the patch
$ omspatcher apply  -bitonly -silent
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       : /opt/company/app/software/em/middleware24/oms_home
Log file location  : /opt/company/app/software/em/middleware24/oms_home/cfgtoollogs/omspatcher/opatch2026-01-27_15-22-47PM_1.log

OMSPatcher log file: /opt/company/app/software/em/middleware24/oms_home/cfgtoollogs/omspatcher/38532004/omspatcher_2026-01-27_15-23-20PM_apply.log

WARNING: OMSPatcher has been invoked with bitonly option but the System patch provided has deployment metadata.
Invocation in bitonly mode will prevent OMSPatcher from deploying artifacts.

Do you want to proceed? [y|n]
Y (auto-answered by -silent)
User Responded with: Y


Prereq "checkComponents" for patch 38527741 passed.

Prereq "checkComponents" for patch 38527764 passed.

Prereq "checkComponents" for patch 38527785 passed.

Prereq "checkComponents" for patch 38527758 passed.

Prereq "checkComponents" for patch 38527802 passed.

Prereq "checkComponents" for patch 38527828 passed.

Running apply prerequisite checks for sub-patch(es) "38527741,38527764,38527785,38527758,38527802" and Oracle Home "/opt/company/app/software/em/middleware24/oms_home"...
Sub-patch(es) "38527741,38527764,38527785,38527758,38527802" are successfully analyzed for Oracle Home "/opt/company/app/software/em/middleware24/oms_home"

Running apply prerequisite checks for sub-patch(es) "38527828" and Oracle Home "/opt/company/app/software/em/middleware24/ext_oms_home"...
Sub-patch(es) "38527828" are successfully analyzed for Oracle Home "/opt/company/app/software/em/middleware24/ext_oms_home"

To continue, OMSPatcher will do the following:
[Patch and deploy artifacts]   :


Do you want to proceed? [y|n]
Y (auto-answered by -silent)
User Responded with: Y

Applying sub-patch(es) "38527741,38527758,38527764,38527785,38527802"
Properties file /opt/company/app/software/em/middleware24/oms_home/sysman/config/emInstanceMapping.properties not found. Exiting.
Properties file /opt/company/app/software/em/middleware24/oms_home/sysman/config/emInstanceMapping.properties not found. Exiting.
Coping /opt/company/app/software/em/middleware24/oms_home/oracle_common/modules/oracle.pki/oraclepki.jar,/opt/company/app/software/em/middleware24/oms_home/oracle_common/modules/oracle.osdt/osdt_core.jar,/opt/company/app/software/em/middleware24/oms_home/oracle_common/modules/oracle.osdt/osdt_cert.jar to /opt/company/app/software/em/middleware24/oms_home/oui/em
Properties file /opt/company/app/software/em/middleware24/oms_home/sysman/config/emInstanceMapping.properties not found. Exiting.
Failed to move file to deployed locationProperties file /opt/company/app/software/em/middleware24/oms_home/sysman/config/emInstanceMapping.properties not found. Exiting.
Failed to move file to deployed locationProperties file /opt/company/app/software/em/middleware24/oms_home/sysman/config/emInstanceMapping.properties not found. Exiting.
Properties file /opt/company/app/software/em/middleware24/oms_home/sysman/config/emInstanceMapping.properties or cumulative mapping files /opt/company/app/software/em/middleware24/oms_home/install/deploy_library_mapping.txt_delta or /opt/company/app/software/em/middleware24/oms_home/install/undeploy_library_mapping.txt_delta not found. Exiting.
Please monitor log file: /opt/company/app/software/em/middleware24/oms_home/cfgtoollogs/opatch/opatch2026-01-27_15-26-34PM_3.log


Applying sub-patch(es) "38527828"
Please monitor log file: /opt/company/app/software/em/middleware24/ext_oms_home/cfgtoollogs/opatch/opatch2026-01-27_15-30-06PM_4.log


Complete Summary
================


All log file names referenced below can be accessed from the directory "/opt/company/app/software/em/middleware24/oms_home/cfgtoollogs/omspatcher/2026-01-27_15-22-47PM_SystemPatch_38532004_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                                       38527828                                       38527828_opatch2026-01-27_15-30-06PM_4.log
  oracle.sysman.top.oms_24.1.0.0.0   38527741,38527758,38527764,38527785,38527802   38527741,38527758,38527764,38527785,38527802_opatch2026-01-27_15-26-34PM_3.log


The following sub-patches are not needed by any component installed in the OMS system:
38527775,38527794,38527769,37616371,38527807,37990627


The following sub-patches are already applied to the OMS system:
38154809



--------------------------------------------------------------------------------
The following warnings have occurred during OPatch execution:
1)  OMSPatcher has been invoked with bitonly option but the System patch provided has deployment metadata.
Invocation in bitonly mode will prevent OMSPatcher from deploying artifacts.
2)  Sub-patch "38154809" skipped as it is already been applied to the "OMS" system.
--------------------------------------------------------------------------------
Log file location: /opt/company/app/software/em/middleware24/oms_home/cfgtoollogs/omspatcher/38532004/omspatcher_2026-01-27_15-23-20PM_apply.log

Patches after the RU apply
opatch lspatches
38527802;Oracle Enterprise Manager for Systems Infrastructure 24ai Release 1 Plug-in Update 7 (24.1.1.7) for Oracle Management Service
38527785;Oracle Enterprise Manager for Exadata 24ai Release 1 Plug-in Update 7 (24.1.1.7) for Oracle Management Service
38527764;Oracle Enterprise Manager for Oracle Database 24ai Release 1 Plug-in Update 7 (24.1.1.7) for Oracle Management Service
38527758;Oracle Enterprise Manager for Fusion Middleware 24ai Release 1 Plug-in Update 7 (24.1.1.7) for Oracle Management Service
38527741;Oracle Enterprise Manager 24ai Release 1 Platform Update 7 (24.1.0.7) for Oracle Management Service
38154809;Oracle Enterprise Manager for Cloud Framework 24ai Release 1 Plug-in Update 5 (24.1.1.5) for Oracle Management Service
37103277;FMW Thirdparty Bundle Patch 12.2.1.4.240925
37096063;OSS 19C BUNDLE PATCH 12.2.1.4.241001
37035947;OWSM BUNDLE PATCH 12.2.1.4.240908
37028738;ADF BUNDLE PATCH 12.2.1.4.240905
36964687;WebCenter Core Bundle Patch 12.2.1.4.240819
36851321;RDA release 24.4-20241015 for OFM 12.2.1.4 SPB
36789759;FMW PLATFORM BUNDLE PATCH 12.2.1.4.240812
36316422;OPSS Bundle Patch 12.2.1.4.240220
34065178;One-off
30152128;One-off
26626168;One-off
1221423;Coherence Cumulative Patch 12.2.1.4.23
37033394;OHS (NATIVE) DB19C BUNDLE PATCH 12.2.1.4.240906
36615359;DATABASE RELEASE UPDATE 19.24.0.0.0 FOR FMW DBCLIENT
34809489;One-off
37087476;WLS PATCH SET UPDATE 12.2.1.4.240922
35965629;ADR FOR WEBLOGIC SERVER 12.2.1.4.0 CPU JAN 2024


Before running ConfigureGC.sh add a datafile to mgmt_tablespace tablespace. During the upgrade this went beyond 32GB. Upgrade will hang until space is added. Secondly if sysman login was disabled with
UPDATE MGMT_CREATED_USERS SET SYSTEM_USER='-1' WHERE user_name='SYSMAN'
then enable it with
UPDATE MGMT_CREATED_USERS SET SYSTEM_USER='1' WHERE user_name='SYSMAN'
Refer EMCC security guide for more on this. Stop OMS and agent and run the configureGC.sh.
emctl stop oms -all
emctl stop agent

$ $ORACLE_HOME/sysman/install/ConfigureGC.sh 
Select upgrade existing system

At this stage the DB modification will happen as such its a good idea to have a backup of the DB if one wasn't done before.

New to 24ai is that upgrades could be done with non-Sys user as well. In this case sys user was selected for upgrade.

As mentioned earlier for the PDB which is inheriting memory parameters from CDB the following warnings could be ignored.

The extend weblogic server domain step comes pre-populated with server,port and the weblgoic user names. Enter the password for the user and the base location.

The port configuration will come pre-populated with existing ports used for configuration.

Review and click configure button.

Configuration assitants show the progress of each step

At the end of the configuration the finish page shows the EM URL and port along with admin service information.


The OMS will be up and running.
emctl status oms
Oracle Enterprise Manager 24ai Release 1
Copyright (c) 1996, 2024 Oracle Corporation.  All rights reserved.
WebTier is Up
Oracle Management Server is Up
JVMD Engine is Up
[oracle@ip-172-31-8-174 ~]$ emctl status oms -details
Oracle Enterprise Manager 24ai Release 1
Copyright (c) 1996, 2024 Oracle Corporation.  All rights reserved.
Console Server Host        : ip-172-31-8-174.eu-west-1.compute.internal
HTTP Console Port          : 7788
HTTPS Console Port         : 7803
HTTP Upload Port           : 4889
HTTPS Upload Port          : 4903
EM Instance Home           : /opt/company/app/software/em/middleware24/gc_inst/em/EMGC_OMS1
OMS Log Directory Location : /opt/company/app/software/em/middleware24/gc_inst/em/EMGC_OMS1/sysman/log
OMS is not configured with SLB or virtual hostname
Agent Upload is locked.
OMS Console is locked.
Active CA ID: 1
Console URL: https://ip-172-31-8-174.eu-west-1.compute.internal:7803/em
Upload URL: https://ip-172-31-8-174.eu-west-1.compute.internal:4903/empbs/upload

WLS Domain Information
Domain Name            : GCDomain
Admin Server Host      : ip-172-31-8-174.eu-west-1.compute.internal
Admin Server HTTPS Port: 7102
Admin Server is RUNNING

Extended Domain Name            : EMExtDomain1
Extended Admin Server Host      : ip-172-31-8-174.eu-west-1.compute.internal
Extended Admin Server HTTPS Port: 7026
Extended Admin Server is RUNNING

Oracle Management Server Information
Managed Server Instance Name: EMGC_OMS1
Oracle Management Server Instance Host: ip-172-31-8-174.eu-west-1.compute.internal
WebTier is Up
Oracle Management Server is Up
JVMD Engine is Up
The EM key will be secured
emctl status emkey
Oracle Enterprise Manager 24ai Release 1
Copyright (c) 1996, 2024 Oracle Corporation.  All rights reserved.
Enter Enterprise Manager Root (SYSMAN) Password :
The EMKey is configured properly.
Agent is also upgraded 24ai and will be up and running.
emctl status agent
Oracle Enterprise Manager 24ai Release 1
Copyright (c) 1996, 2024 Oracle Corporation.  All rights reserved.
---------------------------------------------------------------
Agent Version          : 24.1.0.0.0
OMS Version            : 24.1.0.0.0
Protocol Version       : 12.1.0.1.0
Agent Home             : /opt/company/app/software/em/agent24/agent_inst
Agent Log Directory    : /opt/company/app/software/em/agent24/agent_inst/sysman/log
Agent Binaries         : /opt/company/app/software/em/agent24/agent_24.1.0.0.0
Core JAR Location      : /opt/company/app/software/em/agent24/agent_24.1.0.0.0/jlib
Agent Process ID       : 449292
Parent Process ID      : 449240
Agent URL              : https://ip-172-31-8-174.eu-west-1.compute.internal:3872/emd/main/
Local Agent URL in NAT : https://ip-172-31-8-174.eu-west-1.compute.internal:3872/emd/main/
Repository URL         : https://ip-172-31-8-174.eu-west-1.compute.internal:4903/empbs/upload
Started at             : 2026-01-27 17:33:37
Started by user        : oracle
Operating System       : Linux version 4.18.0-553.84.1.el8_10.x86_64 (amd64)
Number of Targets      : 50
Last Reload            : (none)
Last successful upload                       : 2026-01-27 17:39:46
Last attempted upload                        : 2026-01-27 17:39:46
Total Megabytes of XML files uploaded so far : 0.52
Number of XML files pending upload           : 0
Size of XML files pending upload(MB)         : 0
Available disk space on upload filesystem    : 8.58%
Collection Status                            : Collections enabled
Heartbeat Status                             : Ok
Last attempted heartbeat to OMS              : 2026-01-27 17:43:06
Last successful heartbeat to OMS             : 2026-01-27 17:43:06
Next scheduled heartbeat to OMS              : 2026-01-27 17:44:06

---------------------------------------------------------------
Agent is Running and Ready
However agent will have to be patched with relevant RU for agent. As it won't have those patches. Below output shows the patches on agent.
opatch lspatches
37121017;Non System patch Tracking bug to repackage 19.24 version of UCP patch as 24.1 EM Agent patch
37121014;Non System patch Tracking bug to repackage 19.24 version of JDBC patch as 24.1 EM Agent patch
37096063;OSS 19C BUNDLE PATCH 12.2.1.4.241001
37087476;WLS PATCH SET UPDATE 12.2.1.4.240922

OPatch succeeded.
If password verification function was set to null set it back to original value.

Login to the upgraded 24ai EMCC.

To remove the old 13.5 middleware home verify no processes are running out of it and detach it from inventory.
ps ax | grep  /middleware/
echo $ORACLE_HOME
/opt/xxx/app/software/em/middleware

$ORACLE_HOME/oui/bin/detachHome.sh -silent ORACLE_HOME=$ORACLE_HOME
Launcher log file is /opt/tmp/OraInstall2026-01-27_05-50-49PM/launcher2026-01-27_05-50-49PM.log.
Checking swap space: must be greater than 500 MB.   Actual 4095 MB    Passed
Checking if this platform requires a 64-bit JVM.   Actual 64    Passed (-d64 flag is not required)
detachHome failed.

The log(s) can be found here: /opt/tmp/OraInstall2026-01-27_05-50-49PM.
Though message says detachment fails the inventory.xml says the old home has been rmeoved.
more /opt/xxx/app/oraInventory/ContentsXML/inventory.xml
...
<HOME_LIST>
       <HOME NAME="oms13c1" LOC="/opt/company/app/software/em/middleware" TYPE="O" IDX="3" REMOVED="T"/>
<HOME_LISTgt;
Oracle documentation also states to detach oracle_common directory
$ORACLE_HOME/oui/bin/detachHome.sh -silent ORACLE_HOME=$ORACLE_HOME/oracle_common
But as there's no such entry in the inventory this fails and could be ignored.
Once detached from oracle inventory the old middleware home and instance base location could be removed.
ls
agent  gc_inst  gc_inst135  middleware  middleware135  swlib

rm -rf middleware gc_inst

ls
agent  gc_inst135  middleware135  swlib
The next post will show how to upgrade the central agent to 24.1.

Related Posts
Upgrading Enterprise Manager Cloud Control from 13.4 to 13.5 - 1
Upgrading Enterprise Manager Cloud Control from 13.4 to 13.5 - 2
Upgrading Enterprise Manager Cloud Control from 13.4 to 13.5 - 3
Installing Enterprise Manager Cloud Control 13c (13.4)
Converting EM Repository DB from Non-CDB to PDB
Adding Targets on EM Cloud Control 13c
Installing Enterprise Manager Cloud Control 13c (13.3)
Installing Grid Control 11gR1 and Deploying Agents
Upgrading Grid Control 11g to 12c - 1

Useful KB docs
(KB315275) EM 24ai: How to Upgrade OEM from 13.5 to 24.1
(KB371380) EM 24ai: How To Upgrade Enterprise Manager 24.1 OMSPatcher Utility to the Latest Version
(KB621611) EM 24ai: How to Upgrade OEM from 13.5 to 24.1 Using Silent Method