The enviornment used for this upgrade test started off as a EM 13.5. It was then upgraded to 24ai and blog posts are based on this upgrade. However, if the initial installation was a EM 13.4 and then upgraded to 13.5 followed by an upgrade to 24ai then it is possible to hit the bug 39359223. After the testing as shown here two environments were upgraded to 24ai that started their life as 13.4. Upgrade completed without any issue but no incidents get generated after the upgrade (even when artificially created an incident). Raised SR resulted in the bug 39359223. It seems upgrading from 13.4 -> 13.5 -> 24ai could be hitting an unknown issues (similar to one mentioned in KB639677). SR status is "Development Working" and no ETA on a solution. It is best to create the test environment with the same initial version and then do the subsequent upgrades before the 24ai upgrade. Because depending on initial version there could be issues after the upgrade.
This is the first post on upgrading EM Cloud Control (EMCC) from 13.5 to 24.1. The upgrade steps mentioned here have been tried on a system that has the repository database in a PDB. This post looks at the prerequisite work needed before the upgrade could begin. It is not an extensive look at all the pre-req steps. For complete list of pre-req steps refer the cloud control upgrade guide. Also useful is the MOS doc KB315275. One of the first thing to be done as part of pre-req work is to apply the latest patches for both repository database and OMS and related components. The repository database had RU 19.29 applied while OMS was patched with RU 13.5.0.28. Document KB590189 mentiones minimum RU of 24ai must be applied to upgrade from 13.5.0.28. This fact is mentioned when pre-req is run and also during configuration phase.
With this in mind download the latest RU for 24ai. In this case 24.1.0.7 was used. This will be applied to the 24ai binaries during the upgrade. As a pre-req it is enough to download RU and the OPatch version released with it. Documentaion (KB371380) only mentions updating the omspatcher but patching fails with
Prerequisite check "CheckMinimumOPatchVersion" failed.This is mentioned in KB540933 and KB253309. If this error occurs then update the OPatch.
Other noteworthy snippets from documentation are
Enterprise Manager 13c Release 5 Update 22 (13.5.0.22) is the minimum release update required for upgrading to Enteprise Manager 24ai Release 1.
If you have any earlier releases of Management Agent, then before upgrading the OMS to 24ai Release 1, make sure you upgrade the Management Agents of other earlier releases to 13c Release 5 using the Agent Upgrade Console that is present within the Enterprise Manager Console.
You must ensure that SQL ALG is disabled in firewall. If not, the Enterprise Manager Upgrade process may terminate/hang in same operation for a long time.
If you have events setup for maximum memory usage limit, then you must disable them before upgrade.
For example, alter system set event='10261 trace name context forever, level 3145728','10262 trace name context forever, level 3145728' scope=spfile;
Manually Restarting the OMS and the Management Agent After Upgrading to Enterprise Manager 24ai Release 1
If you install the OMS and the Oracle Database, which houses the Management Repository, on the same host, then when you reboot the host, the OMS and the Management Agent installed with it will not automatically start up. You will have to manually start them.
Most of the pre-req work is similar to 13.5. Only additional once seems to be the undeploying of CSA plugin which is flagged during pre-req check.
This could be undeployed with following emcli commands.
emcli login -username=sysman emcli sync emcli undeploy_plugin_from_agent -plugin="oracle.sysman.csa:13.5.0.0.0" -agent_names="ip-172-31-8-174.eu-west-1.compute.internal:3872" emcli get_plugin_deployment_status -plugin=oracle.sysman.csa Plug-in Deployment/Undeployment Status Destination : Management Agent - ip-172-31-8-174.eu-west-1.compute.internal:3872 Plug-in Name : Oracle CSA Version : 13.5.0.0.0 ID : oracle.sysman.csa Content : Plug-in Action : Undeployment Status : Success Steps Info: ---------------------------------------- ------------------------- ------------------------- ---------- Step Start Time End Time Status ---------------------------------------- ------------------------- ------------------------- ---------- Submit job for undeployment 1/26/26 12:39:24 PM UTC 1/26/26 12:39:24 PM UTC Success Initialize 1/26/26 12:39:29 PM UTC 1/26/26 12:39:29 PM UTC Success Delete target 1/26/26 12:39:29 PM UTC 1/26/26 12:39:29 PM UTC Success Deconfigure plug-in from Management Agent 1/26/26 12:39:29 PM UTC 1/26/26 12:39:44 PM UTC Success Update inventory 1/26/26 12:39:29 PM UTC 1/26/26 12:39:44 PM UTC Success ---------------------------------------- ------------------------- ------------------------- ---------- Destination : Management Agent - ip-172-31-8-174.eu-west-1.compute.internal:3872 Plug-in Name : Oracle CSA Version : 13.5.0.0.0 ID : oracle.sysman.csa Content : Discovery Action : Undeployment Status : Success Steps Info: ---------------------------------------- ------------------------- ------------------------- ---------- Step Start Time End Time Status ---------------------------------------- ------------------------- ------------------------- ---------- Initialize 1/26/26 12:39:29 PM UTC 1/26/26 12:39:29 PM UTC Success Delete target 1/26/26 12:39:29 PM UTC 1/26/26 12:39:29 PM UTC Success Deconfigure plug-in from Management Agent 1/26/26 12:39:44 PM UTC 1/26/26 12:40:52 PM UTC Success Update inventory 1/26/26 12:39:44 PM UTC 1/26/26 12:40:52 PM UTC Success ---------------------------------------- ------------------------- ------------------------- ----------
Other checks are securing the em key (same as 13.5)
emctl status emkey emctl config emkey -copy_to_repos emctl status emkeyGrane execute on dbms_random to public if revoked as a security measure.
grant execute on DBMS_RANDOM to DBSNMP container=all;Remove the password verification function.
alter profile default limit password_verify_function null;To check the upgrade readiness extract the response files from the installer.
./em24100_linux64.bin -getResponseFileTemplates -outputLoc /opt/installs/em/24.1/rsp -Djava.io.tmpdir=/opt/tmpEdit the emprereqkit_upgrade.rsp file. Below is an example of minimum fields required to be populated.
#------------------------------------------------------------------# # Name : UNIX_GROUP_NAME # Type : string # Description : UNIX group name. # Example : UNIX_GROUP_NAME=dba #------------------------------------------------------------------# UNIX_GROUP_NAME=oinstall #------------------------------------------------------------------# # Name : OLD_BASE_DIR # Type : string # Description : Old middleware Home that you want to upgrade.This is applicable when ONE_SYSTEM=true. #------------------------------------------------------------------# OLD_BASE_DIR=/opt/company/app/software/em/middleware #------------------------------------------------------------------# # Name : ONE_SYSTEM # Type : boolean # Description : can be true or false. Setting this variable to true indicates # ONE_SYSTEM.Setting to false indicates "TWO_SYSTEM". #------------------------------------------------------------------# ONE_SYSTEM=true #------------------------------------------------------------------# # Name : SYS_PASSWORD # Type : string # Description : Password of DBA user used to create repository schema. # Example : SYS_PASSWORD=password #------------------------------------------------------------------# SYS_PASSWORD=pwd_here #------------------------------------------------------------------# # Name : SYSMAN_PASSWORD # Type : string # Description : Password for sysman user. #------------------------------------------------------------------# SYSMAN_PASSWORD=pwd_here #------------------------------------------------------------------# # Name : b_upgrade # Type : boolean # Description : To Specify whether it is Normal Install or Upgrade. #------------------------------------------------------------------# b_upgrade=true #------------------------------------------------------------------# # Name : EM_INSTALL_TYPE # Type : string # Description : Type of Grid Control install being performed. #------------------------------------------------------------------# EM_INSTALL_TYPE=NOSEED #------------------------------------------------------------------# # Name : INSTALL_WITH_NON_SYS_USER # Type : boolean # Description : Set true if Install/Upgrade need to be done by non sys user.If this is set as true make sure to proivde dbUser and dbPassword values. #------------------------------------------------------------------# INSTALL_WITH_NON_SYS_USER=falseRun the pre-req check.
./em24100_linux64.bin EMPREREQ_KIT=true -silent -responseFile /opt/installs/em/24.1/rsp/emprereqkit_upgrade.rspBeside any auto-fixable items such as job_queue_processes there shouldn't be any failed items. Since repository is in a PDB the pre-req check memory parameters at PDB level. If these are not set and allowed to be inherited from CDB level then memory parameters could be flagged during pre-req check. These warnings could be ignored.
When the pre-req is at this stage the EM is ready for uprade which will be done using the recommended way which is "Upgrade Software Only with Plug-ins and Configure Later". Steps for this will be shown in the next post.
Related Posts
Upgrading Enterprise Manager Cloud Control from 13.5 to 24.1 - 2
Upgrading Enterprise Manager Cloud Control from 13.5 to 24.1 - 3
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
(KB590189) EM 24ai: Checklist For Upgrading Enterprise Manager Cloud Control from Version 13.5 to 24.1
(KB315275) EM 24ai: How to Upgrade OEM from 13.5 to 24.1
(KB540933) EM 24ai :Upgrade from 13.5 RU27 failing "Checking the patch compatible Version"
(KB253309) EM 24ai :Upgrade from 13.5 RU25 failing "Checking the patch compatible Version"
(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
(KB274749) EM 24ai:Upgrade Is Failing At OMSCA Step "Error reading trustStore Wallet"
