1. Objective
- Upgrade OMS from 13.5 to 24ai.
- OMS is initially in 13.5.2.24 version : I have upgrdaed it to 13.5.0.28
- The OMS server is oms_server
- The current 13.5 OMS is installed under /.../middleware/oms13500
- The upgraded 24ai OMS will be installed under /.../middleware/oms24ai
- The new Instance local home is /.../middleware/gc_24ai
2. Principe
1. Install the OMS using
"Upgrade software only with plug-ins and Configure Later" 2. Complete the OMS
installation and execute the allroot.sh 3. Upgrade the OMSPatcher on
the 24ai OMS_HOME following the instructions in the document: 4. Upgrade OPatch on 24ai
OMS_HOME 5. Download and Stage the RU
patch that needs to be applied, on the OMS host. 6. Apply the Patch on the OMS
following the instructions: NOTE:
7. The OMS can now be
configured by executing the script:
|
3. PreUpgrade
Checklist For Upgrading Enterprise Manager Cloud Control from Version 13.5 to 24.1
To upgrade to EM 24.1, your OMS must be at least version 13.5 with RU 22. If it's currently below 13.5.0.0.0, you must first upgrade it to version 13.5.0.0.0 with RU 22. Please check the respective checklist KB296283 and upgrade guide 2820181.2
|
o Release Update |
o Minimum Upgrade Path to Version 24ai |
|
o 13.5 RU 29 |
o 24ai RU 08 or later |
|
o 13.5 RU28 |
o 24ai RU06 or later |
|
o 13.5 RU 27 |
o 24ai RU 04 or later |
|
o 13.5 RU 26 |
o 24ai RU 02 or later |
|
o 13.5 RU 25 |
o 24ai RU 01 or later |
|
o 13.5 RU 22 through RU 24 |
o 24.1 Base Release or later |
|
Prerequisite |
Applies to Install/Upgrade |
Description |
|
Basic Policy Requirements |
Upgrade |
Ensures that valid policy exists for MGMT_TARGETS. To manually verify this, run the following query: select 'EM_TARGET_POLICY' from dual where not exists (select policy_name from dba_policies where object_owner=’SYSMAN' and pf_owner='SYSMAN' and object_name='MGMT_TARGETS') The query must not return any rows. |
|
Active Jobs Requirements |
Upgrade |
Ensures that there are no background DBMS jobs currently running in the Repository Database. To manually verify this, run the following query: select count(*) FROM dba_jobs_running run_job,gv$session sess WHERE sess.sid=run_job.sid AND sess.schemaname='SYSMAN' If the result of the query is 0 then there are no active DBMS jobs, if result is not 0 then wait for the active jobs to complete. |
|
Checks if GVM Performance collection job is running |
Upgrade |
Ensures that the GVM Performance Metric Collection job is stopped and deleted. To manually verify if a job named GVMPERFMETRICCOLL exists, run the following query: select count(*) from mgmt_job where job_name = 'GVMPERFMETRICCOLL' and job_type = 'UpdateGVMPerfMetric' If it exists, then stop and delete. |
|
Valid Reference Requirements |
Upgrade |
Ensures that all entries for execution_id in MGMT_JOB_EXECUTION either point to a valid entry in MGMT_JOB_EXEC_SUMMARY, or are NULL. To manually verify this, run the following query. The query must not return any rows. SELECT COUNT(1) FROM MGMT_JOB_EXECUTION e WHERE NOT EXISTS (SELECT 1 FROM MGMT_JOB_EXEC_SUMMARY s WHERE s.execution_id = e.execution_id) AND execution_id IS NOT NULL |
|
Job Type Uniqueness Requirements |
Upgrade |
Ensures that there are no duplicate entries in MGMT_JOB_TYPE_INFO for the following set of columns: job_type, job_type_owner, major_version, minor_version1, minor_version2. To manually verify this, run the following query. The query must not return any rows. SELECT job_type FROM MGMT_JOB_TYPE_INFO GROUP BY job_type, job_type_owner, major_version, minor_version1, minor_version2 HAVING COUNT(1) > 1 |
|
SQL Plan Baseline Capture Parameter Requirements |
Install, Upgrade |
Ensures that the parameter optimizer_capture_sql_plan_baselines is set to FALSE (or default). The SQL plan baseline capture must never be turned on for the Management Repository. Enterprise Manager heavily depends on updated CBO statistics. If stale CBO statistics exist, the SQL plan baseline capture could cause bad execution plans to be used for critical functionality. |
|
Current Availability Index Requirements |
Install, Upgrade |
Set the current availability index to EM_CURRENT_AVAILABILITY_PK. |
|
My Oracle Support User Name Size Requirements |
Upgrade |
Ensures that the My Oracle Support user name is not longer than 239 characters. If it is, then you cannot upgrade. |
|
ARU User Name Size Requirements |
Upgrade |
Ensures that the ARU user name is not longer than 239 characters. If it is, you cannot upgrade. |
|
DBMS Package Requirements |
Install, Upgrade |
Ensures that you compile the required DBMS packages. To manually compile the packages, sign in to the database, where the Management Repository is configured, as SYS user, and run the following query to retrieve the list of invalid DBMS packages: SELECT object_name, object_type FROM all_objects WHERE status = 'INVALID' AND object_name LIKE 'DBMS%' If the package is invalid, run the following query:
ALTER PACKAGE <PACKAGE_NAME> COMPILE
ALTER PACKAGE <PACKAGE_NAME> COMPILE BODY If the packages do not compile successfully, contact Oracle Support.
alter PACKAGE sys.DBMS_AUDIT_UTIL compile; alter PACKAGE sys.DBMS_AUDIT_UTIL compile body; |
|
Snapshot Log Requirements |
Upgrade |
Ensures that the snapshot logs are deleted from the tables. |
|
Connector Configuration Table Requirements |
Upgrade |
Ensures that there is no bad data in the connector configuration table. If there is any, then run the following query to clean the table. delete from mgmt_cntr_config where connector_guid is null or connector_type_guid is null; commit; |
|
Compatible Instance Parameter Requirements |
Install, Upgrade |
Ensures that the compatible instance parameter is set to the same version value as the database instance of the Management Repository. Any other value might result in unexpected problems, poor performance, or both. |
|
Primary Key and Foreign Key Requirements |
Upgrade |
Ensures that Primary Key and Foreign keys are not disabled. To manually verify this, run the following query: select count(*) from (select constraint_name, table_name from DBA_CONSTRAINTS where owner = 'SYSMAN' and (constraint_type = 'P' or constraint_type = 'R') and status = 'DISABLED') If the result is not 0, then use the following query to enable the constraint: alter table SYSMAN.<TABLE_NAME> modify constraint <CONSTRAINT_NAME> enable If the constraints cannot be enabled for any reason, contact Oracle Support.
select 'alter table SYSMAN.'||table_name || ' modify constraint '|| constraint_name || ' enable;' from DBA_CONSTRAINTS where owner = 'SYSMAN' and (constraint_type = 'P' or constraint_type = 'R') and status = 'DISABLED'; |
|
Enable Queue Requirements |
Upgrade |
Ensures that queues are enabled in the Repository Database. To manually verify this, run the following query: select count(*) from dba_queues where owner = 'SYSMAN' and queue_type like '%NORMAL_QUEUE%' and (enqueue_enabled like '%NO%' OR dequeue_enabled like '%NO%'); If result is not 0, use the following query to retrieve the list of disabled queue names: select name, queue_table from dba_queues where owner = 'SYSMAN' and upper(queue_type) not like 'EXCEPTION_QUEUE' and (upper(enqueue_enabled) NOT LIKE '%YES%' OR upper(dequeue_enabled) NOT LIKE '%YES%') Execute the following SQL statement to enable the queue: begin dbms_aqadm.start_queue('<disabled_queue_name>'); end; If the queue cannot be started, contact Oracle Support. |
|
Trigger Requirements |
Upgrade |
Ensures that all the triggers in the Repository Database are not disabled. To manually verify this, run the following query: select count(*) from (select trigger_name, trigger_type, table_name from DBA_TRIGGERS where table_owner = 'SYSMAN' and status = 'DISABLED'); If result is not 0, then enable the trigger. |
|
SYSTEM tablespace requirement |
Install and Upgrade |
Ensures that the SYSTEM tablespace has at least one datafile set to autoextensible. To manually verify this, run the following query: select count(*) from dba_data_files where tablespace_name = 'SYSTEM' and autoextensible = 'YES'; If the result is 0, then add a new datafile with the autoextend attribute to the SYSTEM tablespace so it has at least one listed in the DBA_DATA_FILES view with autoextensible equal to 'YES'. Contact Oracle Support if there are any errors |
|
emkey requirement |
Upgrade |
Ensures that the emkey is copied to the repository. To manually verify this, run the following query: select COUNT(*) from sysman.mgmt_repos_time_coefficient If the result of the query is not 1, then copy the emkey.ora file from another OMS or backup machine to the ORACLE_HOME/sysman/config directory. Configure the emkey.ora file by running emctl config emkey -copy_to_repos -sysman_pwd <sysman_pwd>. |
|
EM_USER_CONTEXT requirements |
Upgrade |
Ensures that EM_USER_CONTEXT is present in the repository. To manually verify this, run the following query: select count(*) from dba_context where schema='SYSMAN' and upper(namespace)='EM_USER_CONTEXT'; If the query result is 0, check that the procedure SETEMUSERCONTEXT is valid by executing the following query: select status from all_objects where object_name='SETEMUSERCONTEXT' and owner='SYSMAN' The above query must return 'VALID'. Then run: alter session set current_schema='SYSMAN'; Create or replace context EM_USER_CONTEXT using SETEMUSERCONTEXT; If the context cannot be created for any reason, contact Oracle Support. |
|
Audit Master table requirement |
Upgrade |
Ensures that there are no abnormal conditions stored in the Audit Master Table. To manually verify this, run the following query: select count(*) from sysman.mgmt_audit_master; If the query result is not 1 then, contact Oracle Support to analyze the Enterprise Manager repository before attempting to perform the patch/upgrade. |
|
|
|
|
|
Database Edition Requirements |
Install |
Ensures that you are using Oracle Enterprise Database edition to install Enterprise Manager. To manually verify this, sign in to the database as SYS user and run the following query: select count(1) from PRODUCT_COMPONENT_VERSION where PRODUCT like '%Oracle Database%' and instr(PRODUCT,'Enterprise Edition')>0; The result of the above query should not be 0. |
|
Existing database not to have previous Enterprise Manager's details in schema_version_registry table |
Install |
Ensures that existing database does not have previous Enterprise Manager's details in schema_version_registry table. To manually verify this, sign in to the database as SYS user and run the following query: select count(1) from SCHEMA_VERSION_REGISTRY where comp_name in ('Authorization Policy Manager','Metadata Services','Oracle Platform Security Services') If the result of the above query is not 0 then delete the entries from SCHEMA_VERSION_REGISTRY using the following query: Delete from SCHEMA_VERSION_REGISTRY where comp_name in ('Authorization Policy Manager','Metadata Services','Oracle Platform Security Services','OracleBI and EPM','Service Table'); |
|
….. |
…. |
…. |
|
Existing database Not to have tablespaces of previous Enterprise Manager |
Install |
Ensures that your existing, certified Oracle Database does not have tablespaces of previous Enterprise Manager. To manually verify if the database contains such table spaces, run the following query: select count(1) from dba_tablespaces where TABLESPACE_NAME in ('MGMT_ECM_DEPOT_TS','MGMT_TABLESPACE','MGMT_AD4J_TS') If the result of the above query is not 0, then you can drop these table spaces otherwise new Enterprise Manager will reuse it. |
|
Existing database not to have public synonym on the tables owned by any of the following Enterprise Manager Repository schemas: SYSMAN', SYSMAN_MDS,MGMT_VIEW,SYSMAN122130_OPSS and SYSMAN_RO |
Install |
Ensures that your existing, certified Oracle Database does NOT have any public synonyms on the tables owned by any of the following schemas: SYSMAN, SYSMAN_MDS,MGMT_VIEW,SYSMAN122130_OPSS and SYSMAN_RO To manually verify whether your database has the public synonyms owned by Enterprise Manager database schemas, sign in to the database as SYS user and run the following query: select count(1) from dba_synonyms where table_owner in ('SYSMAN','SYSMAN_MDS','MGMT_VIEW','SYSMAN122130_OPSS','SYSMAN_RO') If the result of this query is not 0, then the database has these public synonyms, so drop them and de-install the Enterprise Manager software that had created these schemas. For instructions, see the Oracle Enterprise Manager Advanced Installation and Configuration Guide. |
4. OMS 24ai : Software
4.1 software_only.rsp
|
Generating the Response File to Upgrade Software Only with Plug-ins in Silent Mode
/.../em24100_linux64.bin -getResponseFileTemplates -J-Djava.io.tmpdir=/.../tmp -getResponseFileTemplates -outputLoc /../tmp/ RESPONSEFILE_VERSION=2.2.1.0.0
UNIX_GROUP_NAME=oinstall
INSTALL_UPDATES_SELECTION=skip
STAGE_LOCATION=<string>
MYORACLESUPPORT_USERNAME_FOR_SOFTWAREUPDATES=<string>
MYORACLESUPPORT_PASSWORD_FOR_SOFTWAREUPDATES=<string>
ORACLE_MIDDLEWARE_HOME_LOCATION=/.../middleware/oms24ai
AGENT_BASE_DIR=/.../oma
ORACLE_HOSTNAME=oms_server
PLUGIN_SELECTION={}
b_upgrade=false
EM_INSTALL_TYPE=NOSEED
CONFIGURATION_TYPE=LATER |
4.2 Silent Software Only Install
|
/.../em24100_linux64.bin -silent -responseFile /../tmp/software_only.rsp
…..
End of install phases. Applying stack patches. This might take a while. Stack Patches got applied Successfully. .Prompt for the allroot.sh
Warning: You must run the following configuration scripts as the "root" user. /../oms24ai/oms_home/allroot.sh To execute the configuration scripts: 1. Open a new terminal window. 2. Login in as "root". 3. Run the scripts.
Successfully installed Enterprise Manager Cloud Control. ...Starting to execute allroot.sh .........
|
At this step, the OMS is installed with software only and the version is 24.0.0.1
I have to upgrade it to 24.0.0.8 (the last versi at this moment) : Patch 38735203
4.3 Opatch - OMSpatcher : get the last version
|
OPatch
How To Download And Install The Latest OPatch(6880880) Version KB88313
export ORACLE_HOME=/.../middleware/oms24ai/oms_home cd /.../middleware/oms24ai/oms_home mv OPatch OPatch_old
/.../jdk/bin/java -Djava.io.tmpdir=/.../tmp -jar /.../6880880/opatch_generic.jar -silent oracle_home=$ORACLE_HOME -invPtrLoc /.../oraInst.loc /.../middleware/oms24ai/oms_home/OPatch $ ./opatch version OPatch Version: 13.9.4.2.22 OPatch succeeded.
OMSPatcher EM 24ai: How To Upgrade Enterprise Manager 24.1 OMSPatcher Utility to the Latest Version Note KB371380
export ORACLE_HOME=/../middleware/oms24ai/oms_home
cp p19999993_241000_Generic.zip /.../middleware/oms24ai/oms_home cd /.../middleware/oms24ai/oms_home mv OMSPatcher OMSPatcher_OLD unzip p19999993_241000_Generic.zip
/.../middleware/oms24ai/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. |
4.4 Patch 38735203: Oracle Enterprise Manager 24ai Release 1 Update 8 (24.1.0.8) for Oracle Management Service
Enterprise Manager 24ai Main Release Update List (Includes Plug-ins) KA1271
|
Enterprise Manager 24ai Main Release Update List (Includes Plug-ins) KA1271
export ORACLE_HOME=/.../middleware/oms24ai/oms_home cd /.../patch_oms24ai_RU08/38735203
Analyse /.../patch_oms24ai_RU08/38735203 $ $ORACLE_HOME/OMSPatcher/omspatcher apply -analyze -bitonly OMSPatcher Automation Tool Copyright (c) 2024, Oracle Corporation. All rights reserved.
OMSPatcher version : 13.9.24.11.0 OUI version : 13.9.4.0.0
OMSPatcher log file: /.../middleware/oms24ai/oms_home/cfgtoollogs/omspatcher/38735203/omspatcher_2026-04-28_10-58-23AM_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 User Responded with: Y
Prereq "checkComponents" for patch 38733813 passed.
Prereq "checkComponents" for patch 38733821 passed.
Prereq "checkComponents" for patch 38733833 passed.
Prereq "checkComponents" for patch 38733818 passed.
Prereq "checkComponents" for patch 38733839 passed.
Prereq "checkComponents" for patch 38733854 passed. ...
OMSPatcher succeeded. Apply export ORACLE_HOME=/.../middleware/oms24ai/oms_home /.../patch_oms24ai_RU08/38735203 $ $ORACLE_HOME/OMSPatcher/omspatcher apply -bitonly OMSPatcher Automation Tool Copyright (c) 2024, Oracle Corporation. All rights reserved.
OMSPatcher version : 13.9.24.11.0 OUI version : 13.9.4.0.0 Running from : /.../middleware/oms24ai/oms_home Log file location : /.../middleware/oms24ai/oms_home/cfgtoollogs/omspatcher/opatch2026-04-28_11-03-11AM_1.log
Do you want to proceed? [y|n] y User Responded with: Y
Prereq "checkComponents" for patch 38733813 passed.
Prereq "checkComponents" for patch 38733821 passed.
Prereq "checkComponents" for patch 38733833 passed.
Prereq "checkComponents" for patch 38733818 passed.
Prereq "checkComponents" for patch 38733839 passed.
Prereq "checkComponents" for patch 38733854 passed.
Running apply prerequisite checks for sub-patch(es) "38733813,38733821,38733833,38733818,38733839" and Oracle Home "/.../middleware/oms24ai/oms_home"... Sub-patch(es) "38733813,38733821,38733833,38733818,38733839" are successfully analyzed for Oracle Home "/.../middleware/oms24ai/oms_home" .... Do you want to proceed? [y|n] y User Responded with: Y
Applying sub-patch(es) "38733813,38733818,38733821,38733833,38733839" ...
OMSPatcher succeeded. |
5. Upgrade to 24ai
5.1 Upgrade healthCheck emprereqkit_upgrade.rsp
|
#################################################################### ## ## ## Copyright (c) 2015 Oracle. All rights reserved. ## ## ## ## Specify values for the variables listed below to customize ## # ####################################################################
RESPONSEFILE_VERSION=2.2.1.0.0
UNIX_GROUP_NAME=oinstall
OLD_BASE_DIR=/…/middleware/oms13500
ONE_SYSTEM=true
SYS_PASSWORD=xxxxxxxx
dbUser=YYYYYY
dbPassword=xxxxxxxx
SYSMAN_PASSWORD=xxxxxxxx
Is_oneWaySSL=<string>
TRUSTSTORE_LOCATION=<string>
TRUSTSTORE_PASSWORD=<string>
Is_twoWaySSL=<string>
KEYSTORE_LOCATION=<string>
KEYSTORE_PASSWORD=<string>
b_upgrade=true
EM_INSTALL_TYPE=NOSEED
INSTALL_WITH_NON_SYS_USER=true |
5.2 Upgrade healthCheck
|
export ORACLE_HOME=/…/middleware/oms24ai/oms_home/ export JAVA_HOME=/…/middleware/oms24ai/oms_home/oracle_common/jdk export PATH=$JAVA_HOME/bin:$PATH ./em24100_linux64.bin EMPREREQ_KIT=true -silent -responseFile /…/tmp/emprereqkit_upgrade.rsp -J-Djava.io.tmpdir=/…/tmp
Extracting the installer . . . . . . . . . . . . . . . . Done Checking swap space: must be greater than 512 MB. Actual 4095 MB Passed …
|
Example of output ..Enterprise Management Prereq Report: correct if necessary
|
Name |
Status ⇅ |
Type ⇅ |
Recommendation |
Auto Fixable |
|
Check execution_db column for constraint violations. |
Succeeded |
Contact
Oracle Support |
||
|
Check the processes instance parameter value |
Succeeded |
The
processes instance parameter needs to be set to at least 600. |
||
|
Check the pga_aggregate_target instance parameter value. ......... |
Warning |
Manual |
The
pga_aggregate_target instance parameter should be set to at least 1340000000
bytes. |
5.2 Update OMR
5.2.1 Restore Point
On the repository database (the OMR database) create a restore point ...
|
SQL> CREATE RESTORE POINT before_upgrade GUARANTEE FLASHBACK DATABASE; |
5.2.2 Remove DIAGKIT
Check if the Diagkit is present during upgrade Warning Manual Remove Diagkit objects and tables before upgrade
EM 13C: Application of RU Fails With GC_DIAG2_EXT And GC_DIAG3_EXT PACKAGE BODY Invalid KB383596 connect to the OMR Database: export ORACLE_SID=… . oraenv
mkdir $ORACLE_HOME/emdiag Install repvfy ...
invalid ... SYSMAN PACKAGE BODY GC_DIAG2_EXT SYSMAN PACKAGE BODY GC_DIAG3_EXT cd $ORACLE_HOME/emdiag/bin
./repvfy deinstall -tns xxxx -pwd yyyy
|
5.2.2 emcli verify_swlib
|
<OMS_HOME>/bin/emcli login -username=sysman <OMS_HOME>/bin/emcli sync |
5.2.2 Copy emkey
|
echo $ORACLE_HOME /…/middleware/oms13500 · Copy key
emctl config emkey -remove_from_repos
emctl config emkey -copy_to_repos Verif : select COUNT(*) from sysman.mgmt_repos_time_coefficient; ð 1
|
5.2.3 OMR update
--at the PDB level alter trigger GSMADMIN_INTERNAL.GSMLOGOFF disable; alter system set pga_aggregate_target=1G scope=spfile; alter system set job_queue_processes =0 scope=both; alter system set "session_cached_cursors"=200 scope=spfile; alter system set "shared_pool_size"=629145600 scope=spfile ; alter PACKAGE SYS.DBMS_AUDIT_UTIL compile; alter PACKAGE SYS.DBMS_AUDIT_UTIL compile body; drop PUBLIC SYNONYM DBA_DV_STATUS; drop PROCEDURE sys.PRO_COMPTE_NON_CON_1AN; drop view sys.DBA_DV_STATUS; @?/rdbms/admin/utlrp.sql select owner, object_name, object_type from dba_objects where status ='INVALID';
--at the root level alter trigger GSMADMIN_INTERNAL.GSMLOGOFF disable; alter system reset large_pool_size scope=both; alter system set pga_aggregate_target=1G scope=both sid='*'; alter system set job_queue_processes =0 scope=both; --undo alter system set job_queue_processes = 1000 scope=both; alter system set parallel_max_servers =1 scope=both; --undo alter system set parallel_max_servers =160 scope=both; alter system set parallel_min_servers =1 scope=both; --undo alter system set parallel_min_servers =16 scope=both; alter system reset "_optimizer_gather_feedback" scope=both sid='*'; alter system reset "_optimizer_nlj_hj_adaptive_join" scope=both sid='*'; alter system reset "_optimizer_strans_adaptive_pruning" scope=both sid='*'; alter system reset "_px_adaptive_dist_method" scope=both sid='*'; alter system reset "_sql_plan_directive_mgmt_control" scope=both sid='*'; alter system reset "_optimizer_dsdir_usage_control" scope=both sid='*'; alter system reset "_optimizer_use_feedback" scope=both sid='*'; alter system reset "_optimizer_gather_feedback" scope=both sid='*'; alter system reset "_optimizer_performance_feedback" scope=both sid='*'; alter system set "_allow_insert_with_update_check"=true scope=both sid='*'; alter system set "session_cached_cursors"=210 scope=spfile sid='*' ; alter system set "shared_pool_size"=629145600 scope=spfile sid='*' ;
@?/rdbms/admin/utlrp.sql alter PACKAGE SYS.DBMS_AUDIT_UTIL compile; alter PACKAGE SYS.DBMS_AUDIT_UTIL compile body; shutdown immediate startup select owner, object_name, object_type from dba_objects where status ='INVALID'; |
5.3 Upgrade OMS
5.3.1 upgrade.rsp
|
RESPONSEFILE_VERSION=2.2.1.0.0
UNIX_GROUP_NAME=oinstall
INVENTORY_LOCATION=/…/oracle/oraInventory
INSTALL_UPDATES_SELECTION=skip
STAGE_LOCATION=<string>
MYORACLESUPPORT_USERNAME_FOR_SOFTWAREUPDATES=<string>
MYORACLESUPPORT_PASSWORD_FOR_SOFTWAREUPDATES=<string>
ORACLE_MIDDLEWARE_HOME_LOCATION=/…/middleware/oms24ai
ORACLE_INSTANCE_HOME_LOCATION= /…/middleware/gc_24ai
OLD_BASE_DIR=/…/middleware/oms13500
ORACLE_HOSTNAME=oms_server
ONE_SYSTEM=true
AGENT_BASE_DIR=/…/oma
OLD_DATABASE_CONNECTION_DESCRIPTION=<string>
OLD_DATABASE_SYSMAN_PASSWORD=<string>
WLS_ADMIN_SERVER_USERNAME=weblogic
WLS_ADMIN_SERVER_PASSWORD=xxxxxx
WLS_ADMIN_SERVER_CONFIRM_PASSWORD=xxxxxx
NODE_MANAGER_PASSWORD=xxxxxx
NODE_MANAGER_CONFIRM_PASSWORD=xxxxxx
WLS_ADMIN_SERVER_PASSWORD=xxxxxx
JVM_DIAGNOSTICS_TABLESPACE_LOCATION=<string>
DATABASE_HOSTNAME=<OMR_SERVER>
LISTENER_PORT=1521
SERVICENAME_OR_SID=yyyyyyy
SYS_PASSWORD=xxxxxxx
dbUser=<string>
dbPassword=<string>
SYSMAN_PASSWORD=xxxxxx
Is_oneWaySSL=<string>
TRUSTSTORE_LOCATION=<string>
TRUSTSTORE_PASSWORD=<string>
Is_twoWaySSL=<string>
KEYSTORE_LOCATION=<string>
KEYSTORE_PASSWORD=<string>
EMPREREQ_AUTO_CORRECTION=false
INSTALL_WITH_NON_SYS_USER=false
REPOSITORY_BACKUP_DONE=true
PLUGIN_SELECTION={}
b_upgrade=true
EM_INSTALL_TYPE=NOSEED |
5.3.2 Launch the upgrade
|
export ORACLE_HOME=/…/middleware/oms24ai/oms_home to use an other tmp directory instead of /tmp : cp $ORACLE_HOME/sysman/install/ConfigureGC.sh $ORACLE_HOME/sysman/install/ConfigureGC.old.sh change $ORACLE_HOME/sysman/install/ConfigureGC.sh as :#INSTALLER_JAVA_OPTIONS="-mx1024m -Doracle.installer.appendjre=true" INSTALLER_JAVA_OPTIONS="-mx1024m -Doracle.installer.appendjre=true -Djava.io.tmpdir=/…/tmp"
Upgrade …
$ORACLE_HOME/sysman/install/ConfigureGC.sh -silent -responseFile /.../tmp/upgrade.rsp
Starting of OMS is successful. Starting export oms config... Executing command: /.../middleware/oms24ai/oms_home//bin/emctl exportconfig oms -dir /.../middleware/gc_inst_24ai/em/EMGC_OMS1/sysman/backup
Export config of OMS is successful.
Object is = 1 Detaching the old OMS home from the central inventory.
Detached the old oms Home from Central Inventory
2026-06-15_10-40-18AM: Configuration Assistant "Start Oracle Management Service" has Succeeded.
2026-06-15_10-40-18AM: Configuration Assistant "Agent Upgrade And Configuration" is in progress.
java.io.IOException: Cannot run program "/.../oma/agent_24.1.0.0.0/sysman/install/agentPostInstall.sh": error=2, No such file or directory at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048) at java.lang.Runtime.exec(Runtime.java:593) at java.lang.Runtime.exec(Runtime.java:423) at java.lang.Runtime.exec(Runtime.java:320) at oracle.sysman.upgrade.AgentUpgradeConfiguration.execCommand(AgentUpgradeConfiguration.java:425) at oracle.sysman.upgrade.AgentUpgradeConfiguration.postInstall(AgentUpgradeConfiguration.java:881) at oracle.sysman.upgrade.AgentUpgradeConfiguration.perform(AgentUpgradeConfiguration.java:245) at oracle.sysman.upgrade.AgentUpgradeConfiguration$RunPlug.run(AgentUpgradeConfiguration.java:786) Caused by: java.io.IOException: error=2, No such file or directory at java.lang.UNIXProcess.forkAndExec(Native Method) at java.lang.UNIXProcess.<init>(UNIXProcess.java:247) at java.lang.ProcessImpl.start(ProcessImpl.java:134) at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029) ... 7 more java.io.IOException: Cannot run program "/.../oma/agent_24.1.0.0.0/oracle_common/jdk/bin/java": error=2, No such file or directory at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048) at oracle.sysman.upgrade.AgentUpgradeConfiguration.perform(AgentUpgradeConfiguration.java:322) at oracle.sysman.upgrade.AgentUpgradeConfiguration$RunPlug.run(AgentUpgradeConfiguration.java:786) Caused by: java.io.IOException: error=2, No such file or directory at java.lang.UNIXProcess.forkAndExec(Native Method) at java.lang.UNIXProcess.<init>(UNIXProcess.java:247) at java.lang.ProcessImpl.start(ProcessImpl.java:134) at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029) ... 2 more AgentUpgradeConfiguration:agent configuration has been started
*** The installation was Successful. ***
At the end emcli get_targets must be ok, if it is not the case:
Use the following steps to perform the partition maintenance and re-submit all mandatory DBMS scheduler jobs related to the EM repository: SQL> connect / as sysdba (+pdb) SQL> alter system set job_queue_processes = 0; SQL> connect sysman/<password> SQL> exec emd_maintenance.remove_em_dbms_jobs; SQL>exec gc_interval_partition_mgr.partition_maintenance; SQL> @/…/sysman/admin/emdrep/sql/core/latest/admin/admin_recompile_invalid.sql SYSMAN
SQL> connect / as sysdba (+pdb) SQL> alter system set job_queue_processes = 1000; SQL> connect sysman/<password> SQL> exec emd_maintenance.submit_em_dbms_jobs; SQL> commit;
|
5.4 PostUpgrade
5.4.1 OMR update
|
alter trigger GSMADMIN_INTERNAL.GSMLOGOFF enable; (+PDB)
|
5.5 Apply Holistic patch - Agent patch
The OMS version is 24.0.0.8, we have to apply the Holistic patch 39267110 and the agent patch 38735209
- OEM 24AI: How To Apply/Rollback Holistic Patch On OEM 24.1 - KB487128
§ Enterprise Manager 24ai Main Release Update List (Includes Plug-ins) KA1271
