nabhesh-joshi-oracledba: Upgrade OEM Cloud Control from Version 13.2 to 13.4

Current OMS version:13.2.0.0

Repository database OEMPROD version: 12.2.0.1.0

New OMS version:13.4.0.0

Current home è /app/oracle/product/13cR2/Middleware

New home è /app/oracle/product/13cR4/Middleware

**OMS UPGRADE BACKUP PLAN

Oracle recommends that you back up the Middleware Home, the Management Repository, Central inventory, Software library, Management Agent. In case the upgrade fails, you can always restore using the backup.

REPOSITORY DATABASE OEMPROD:

Create a guaranteed restore point

SQL>alter database flashback on;

SQL>create restore point before_oms_upgrade guarantee flashback database;

OMS :

Take tar backup of OMS home.

tar -czvf /backup/OMS13CR4/OMS_AGENT_BACKUP/OMS_HOME.tar.gz /app/oracle/product/13cR2/Middleware

root@oraem ]# ls -ltrh /backup/OMS13CR4/OMS_AGENT_BACKUP/OMS_HOME.tar.gz

-rw-r--r-- 1 root root 17G Sep 9 22:22 /backup/OMS13CR4/OMS_AGENT_BACKUP/OMS_HOME.tar.gz

Take tar backup of central agent

tar -czvf /backup/OMS13CR4/OMS_AGENT_BACKUP/agent13c.tar.gz /app/oracle/product/agent/

[root@oraem ~]# ls -ltrh /backup/OMS13CR4/OMS_AGENT_BACKUP/agent13c.tar.gz

-rw-r--r-- 1 root root 1.7G Sep 9 22:12 /backup/OMS13CR4/OMS_AGENT_BACKUP/agent13c.tar.gz

[root@oraem ~]#

3. Take configuration backup.

$OMS_HOME/bin/emctl exportconfig oms -dir /backup/OMS13CR4/OMSCONIGBKP

[oracle@oraem Middleware]$ emctl exportconfig oms -dir /backup/OMS13CR4/OMSCONIGBKP

Oracle Enterprise Manager Cloud Control 13c Release 2

Enter Enterprise Manager Root (SYSMAN) Password :

ExportConfig started...

Backup directory is /backup/OMS13CR4/OMSCONIGBKP

Machine is Admin Server host. Performing Admin Server backup...

Exporting emoms properties...

Exporting secure properties...

Export has determined that the OMS is not fronted

by an SLB. The local hostname was NOT exported.

The exported data can be imported on any host but

resecure of all agents will be required. Please

see the EM Advanced Configuration Guide for more

details.

Exporting configuration for pluggable modules...

Preparing archive file...

Backup has been written to file: /backup/OMS13CR4/OMSCONIGBKP/opf_ADMIN_20200909_231731.bka

The export file contains sensitive data.

You must keep it secure.

ExportConfig completed successfully!

[oracle@oraem Middleware]$

PRE-IMAGE OF OEM CONSOLE

1.OMS UPGRADE PRE-CHECK

Ensure that the host on which the OMS is being upgraded meets the hardware requirements

RAM - 12GB
Hard Disk Space - 35 GB
Temporary Directory Hard Disk Space - 14GB
Oracle WebLogic Server JVM Heap Size - 4GB (Default is 3GB)

1. 2.Verify that all the OMS (including Standby) have the same version of Plugins deployed. Execute the following in the repository database,

connected as SYSMAN user:

Connected.

SQL> set serveroutput on

SQL> declare

2 oms_guids mgmt_medium_string_array := mgmt_medium_string_array();

3 oms_names mgmt_medium_string_array := mgmt_medium_string_array();

4 mismatches smp_emd_nvpair_array := smp_emd_nvpair_array();

5 begin

6 select host_url, em_plugin_util.get_guid_from_name(unique_oms_name)

7 bulk collect into oms_names, oms_guids

8 from gc_oms_info;

9 for j in 1..oms_guids.count

10 loop

11 dbms_output.put_line('Checking mismatch for OMS ' || oms_names(j));

12 mismatches := smp_emd_nvpair_array();

13 em_plugin_inventory.get_plugin_mismatch(oms_guids(j), mismatches);

14 if mismatches is null or mismatches.count = 0

15 then

16 dbms_output.put_line('No mismatch found for OMS ' || oms_names(j));

17 else

18 dbms_output.put_line('Mismatch found for OMS ' || oms_names(j));

19 for i in 1..mismatches.count

20 loop

21 dbms_output.put_line('Plug-in on repository: ' || nvl(mismatches(i).name, 'None') ||

22 ', Plug-in on OMS: ' || nvl(mismatches(i).value, 'None'));

23 end loop;

24 end if;

25 end loop;

26 end;

27 /

Checking mismatch for OMS oraem.palmcoastd.com:4889_Management_Service

No mismatch found for OMS oraem.palmcoastd.com:4889_Management_Service

PL/SQL procedure successfully completed.

****NO ACTION NEEDED***

If you have a large number of PropogateTarget jobs, then the Repository Upgrade can consume very long time or stuck while executing "upgrade/post_jobtype_upgrade.sql"

Check if there are large number of jobs that are stuck:

SQL> SELECT job_type, status, cnt

FROM (

SELECT job_type, status, count(*) as cnt

FROM MGMT_JOB_EXEC_SUMMARY join MGMT_JOB_TYPE_INFO using (job_type_id)

WHERE status NOT IN(3,4,5,8,18,19,23)

group by job_type, status

order by 3, 1, 2

)

where cnt > 10000; 2 3 4 5 6 7 8 9

no rows selected

**** NO ACTION NEEDED ****

If you have any of the following plugins, have them downloaded from here and stage them on the OMS_HOST. Initiate the upgrade using: em13400_<platform>.bin PLUGIN_LOCATION=<path where the plugins are staged>

Enterprise Manager for Times Ten

Enterprise Manager for People Soft

Enterprise Manager for Oracle Unified Directory

Enterprise Manager for Utilities (TUGBU)

Enterprise Manager for Golden Gate

Enterprise Manager for Database Appliance

Enterprise Manager for Audit Vault and Database Firewall

Enterprise Manager for EBS

[oracle@oraem bin]$ ./emcli login -username=sysman

Enter password :

[oracle@oraem bin]$ ./emcli sync

Synchronized successfully

[oracle@oraem bin]$ ./emcli list_plugins_on_server

OMS name is oraem.palmcoastd.com:4889_Management_Service

Plug-in Name Plugin-id Version [revision]

Oracle Cloud Framework oracle.sysman.cfw 13.2.1.0.0

Oracle Database oracle.sysman.db 13.2.2.0.0

Oracle Fusion Middleware oracle.sysman.emas 13.2.1.0.0

Systems Infrastructure oracle.sysman.si 13.2.1.0.0

Oracle Exadata oracle.sysman.xa 13.2.1.0.0

[oracle@oraem bin]$

SQL> SELECT epv.plugin_id, epv.version FROM em_plugin_version epv, em_current_deployed_plugin ecp WHERE epv.plugin_type NOT IN ( 'BUILT_IN_TARGET_TYPE' , 'INSTALL_HOME') AND ecp.dest_type='2' AND epv.plugin_version_id = ecp.plugin_version_id;

PLUGIN_ID VERSION

------------------------------ --------------------------------

oracle.sysman.cfw 13.2.1.0.0

oracle.sysman.emas 13.2.1.0.0

oracle.sysman.si 13.2.1.0.0

oracle.sysman.db 13.2.2.0.0

oracle.sysman.xa 13.2.1.0.0

**** NO ACTION NEEDED ****

Ensure that the ulimit is updated to the following values before Upgrade:

softnofiles : 30000

file-max : 65536

[oracle@oraem bin]$ cat /etc/security/limits.conf |grep soft |grep nofile

# oracle-rdbms-server-11gR2-preinstall setting for nofile soft limit is 1024

oracle soft nofile 1024

[oracle@oraem bin]$

[oracle@oraem bin]$ cat /etc/sysctl.conf |grep file

# To override those settings, enter new settings here, or in an /etc/sysctl.d/<name>.conf file

# oracle-rdbms-server-11gR2-preinstall setting for fs.file-max is 6815744

fs.file-max = 6815744

[oracle@oraem bin]$

***ACTION NEEDED ***

[root@oraem .patch_storage]# cat /etc/security/limits.conf |grep soft |grep nofile

# oracle-rdbms-server-11gR2-preinstall setting for nofile soft limit is 1024

#oracle soft nofile 1024

oracle soft nofile 30000 è DONE

Ensure that the CLASSPATH environment variable is unset prior to starting the upgrade.

Reference: 13.4: OMS Install/Upgrade Fails During BIP Configuration (Doc ID 2634802.1)

[oracle@oraem bin]$ . oraenv

ORACLE_SID = [oemprod] ?

The Oracle base remains unchanged with value /app/oracle

[oracle@oraem bin]$ env |grep PATCH

[oracle@oraem bin]$ env |grep PATH

LD_LIBRARY_PATH=/app/oracle/product/12cr1/db_12102/lib

PATH=/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/home/oracle/.local/bin:/home/oracle/bin:/app/oracle/product/12cr1/db_12102/bin

[oracle@oraem bin]$ env |grep CLASSPATH

[oracle@oraem bin]$

**** NO ACTION NEEDED ****

SQL> show user

USER is "SYSMAN"

SQL> select * from EM_SWLIB_TS_ENT_SUBTYPES_E st where st.SUBTYPE_ID = '450' AND st.name = 'SUB_OracleGSM';

no rows selected

If this query returns any rows, please follow the instructions from the document Note 2670368.1

If no rows are returned, proceed with the upgrade.

**** NO ACTION NEEDED ****

Execute the following query in the repository as SYS user:

SQL> show user

USER is "SYS"

SQL> select * from sysman_opss.jps_dn where parentdn like '%cn=roles%' and rdn like 'cn=%\ %';

no rows selected

SQL>

If this query returns any rows, please create an SR with Oracle Support. If no rows are returned, continue with the upgrade.

**** NO ACTION NEEDED ****

Run Pre-requisite

[oracle@oraem ~]$ cd /backup/OMS13CR4

[oracle@oraem OMS13CR4]$ chmod u+x em13400_linux64.bin

[oracle@oraem OMS13CR4]$ ls -ltrh

total 12G

-rwxr--r-- 1 oracle oinstall 1.6G Aug 22 15:40 em13400_linux64.bin

-rw-r--r-- 1 oracle oinstall 2.0G Aug 23 09:49 em13400_linux64-2.zip

-rw-r--r-- 1 oracle oinstall 2.0G Aug 23 10:03 em13400_linux64-3.zip

-rw-r--r-- 1 oracle oinstall 771M Aug 23 10:12 em13400_linux64-5.zip

-rw-r--r-- 1 oracle oinstall 2.0G Aug 23 10:18 em13400_linux64-4.zip

-rw-r--r-- 1 oracle oinstall 1.8G Aug 23 10:28 em13400_linux64-7.zip

-rw-r--r-- 1 oracle oinstall 2.0G Aug 23 11:16 em13400_linux64-6.zip

[oracle@oraem OMS13CR4]$ ./em13400_linux64.bin -J-Djava.io.tmpdir=/backup/tmp/ EMPREREQ_KIT=true

Launcher log file is /backup/tmp/OraInstall2020-08-23_11-24-27AM/launcher2020-08-23_11-24-27AM.log.

Extracting the installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Done

Checking monitor: must be configured to display at least 256 colors. Actual 16777216 Passed

Checking swap space: must be greater than 512 MB. Actual 12071 MB Passed

Checking if this platform requires a 64-bit JVM. Actual 64 Passed (64-bit not required)

Preparing to launch the Oracle Universal Installer from /backup/tmp/OraInstall2020-08-23_11-24-27AM

====Prereq Config Location main===

/backup/tmp/OraInstall2020-08-23_11-24-27AM/stage/prereq

EMGCInstaller args -scratchPath

EMGCInstaller args /backup/tmp/OraInstall2020-08-23_11-24-27AM

EMGCInstaller args -sourceType

EMGCInstaller args network

EMGCInstaller args -timestamp

EMGCInstaller args 2020-08-23_11-24-27AM

EMGCInstaller args -paramFile

EMGCInstaller args /backup/tmp/sfx_231j7D/Disk1/install/linux64/oraparam.ini

EMGCInstaller args EMPREREQ_KIT=true

EMGCInstaller args -nocleanUpOnExit

DiskLoc inside SourceLoc/backup/tmp

EMFileLoc:/backup/tmp/OraInstall2020-08-23_11-24-27AM/oui/em/

ScratchPathValue :/backup/tmp/OraInstall2020-08-23_11-24-27AM

Manual

It is an error message and you must manually fix it before moving ahead.

Auto

It is an error message and you can ignore it since EM has predefined corrective actions to fix it.

For improved SQL performance all the adaptive features parameters should be unset prior to the upgrade.

alter system set "_optimizer_nlj_hj_adaptive_join"= FALSE scope=both;

alter system set "_optimizer_strans_adaptive_pruning" = FALSE scope=both;

alter system set "_px_adaptive_dist_method" = OFF scope=both;

alter system set "_sql_plan_directive_mgmt_control" = 0 scope=both;

alter system set "_optimizer_dsdir_usage_control" = 0 scope=both;

alter system set "_optimizer_use_feedback" = FALSE scope=both;

alter system set "_optimizer_gather_feedback" = FALSE scope=both;

alter system set "_optimizer_performance_feedback" = OFF scope=both;

alter system set _allow_insert_with_update_check=true scope=both;

alter system set job_queue_processes=0 scope=both;

alter system set shared_pool_size=1g scope=both;

alter trigger GSMADMIN_INTERNAL.GSMLOGOFF disable;

EXEC DBMS_AUTO_TASK_ADMIN.DISABLE(client_name=>'auto optimizer stats collection', operation=>NULL, window_name=>NULL);

10. Copy the emkey using the following commands. à DONE

[oracle@oraem OMS13CR4]$ emctl status emkey

Oracle Enterprise Manager Cloud Control 13c Release 2

Enter Enterprise Manager Root (SYSMAN) Password :

The EMKey is configured properly.

[oracle@oraem OMS13CR4]$ emctl config emkey -copy_to_repos

Oracle Enterprise Manager Cloud Control 13c Release 2

Enter Enterprise Manager Root (SYSMAN) Password :

The EMKey has been copied to the Management Repository. This operation will cause the EMKey to become unsecure.

After the required operation has been completed, secure the EMKey by running "emctl config emkey -remove_from_repos".

****UPGRADE OMS****

1. Shutdown the OMS and Agent, Stop the JVMD and ADP engines

$OMS_HOME/bin/emctl stop oms -all

[oracle@oraem product]$ emctl stop oms -all

Oracle Enterprise Manager Cloud Control 13c Release 2

Stopping Oracle Management Server...

WebTier Successfully Stopped

Oracle Management Server Successfully Stopped

Oracle Management Server is Down

JVMD Engine is Down

Stopping BI Publisher Server...

BI Publisher Server Successfully Stopped

AdminServer Successfully Stopped

BI Publisher Server is Down

$AGENT_HOME/bin/emctl stop agent

[oracle@oraem product]$ emctl stop agent

Oracle Enterprise Manager Cloud Control 13c Release 2

Stopping agent ... stopped.

$OMS_HOME/bin/emctl extended oms jvmd stop -all

[oracle@oraem product]$ emctl extended oms jvmd stop -all

Oracle Enterprise Manager Cloud Control 13c Release 2

No verb found to be registered with emctl extensibles framework

$OMS_HOME/bin/emctl extended oms adp stop -all

[oracle@oraem product]$ emctl extended oms adp stop -all

Oracle Enterprise Manager Cloud Control 13c Release 2

No verb found to be registered with emctl extensibles framework

2. Run installer

cd /backup/OMS13CR4

unset CLASSPATH

./em13400_linux64.bin -J-Djava.io.tmpdir=/backup/tmp/

[root@oraem oracle]# /app/oracle/product/13cR4/Middleware/allroot.sh

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

Starting to execute /app/oracle/product/13cR4/Middleware/root.sh ......

Performing root user operation.

The following environment variables are set as:

ORACLE_OWNER= oracle

ORACLE_HOME= /app/oracle/product/13cR4/Middleware

Enter the full pathname of the local bin directory: [/usr/local/bin]:

The contents of "dbhome" have not changed. No need to overwrite.

The file "oraenv" already exists in /usr/local/bin. Overwrite it? (y/n)

[n]: y

Copying oraenv to /usr/local/bin ...

The contents of "coraenv" have not changed. No need to overwrite.

Entries will be added to the /etc/oratab file as needed by

Database Configuration Assistant when a database is created

Finished running generic part of root script.

Now product-specific root actions will be performed.

/etc exist

/app/oracle/product/13cR4/Middleware

Finished execution of /app/oracle/product/13cR4/Middleware/root.sh ......

[root@oraem oracle]#

OEM UPGRADED TO 13.4

POST UPGRADE TASK

End blackout

After ending the blackout, the OEM host and OMS related targets will still show under blackout.

Follow the solution given in the Doc ID 2641816.1

Solution

[oracle@oraem emd]$ emctl stop agent

Oracle Enterprise Manager Cloud Control 13c Release 2

Stopping agent ... stopped.

[oracle@oraem emd]$ emctl getproperty agent -name "SSLCipherSuites"

Oracle Enterprise Manager Cloud Control 13c Release 2

SSLCipherSuites is unset; default value is SSL_RSA_WITH_RC4_128_MD5:SSL_RSA_WITH_RC4_128_SHA:SSL_RSA_WITH_3DES_EDE_CBC_SHA

[oracle@oraem emd]$ emctl setproperty agent -name "SSLCipherSuites" -value "SSL_RSA_WITH_AES_128_CBC_SHA:SSL_RSA_WITH_AES_256_CBC_SHA:TLS_RSA_WITH_AES_128_CBC_SHA256:TLS_RSA_WITH_AES_256_CBC_SHA256:TLS_RSA_WITH_AES_128_GCM_SHA256:TLS_RSA_WITH_AES_256_GCM_SHA384:TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA:TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA:TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384:TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256:TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384:TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256:TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA:TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA:TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256:TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384:TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256:TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384"

Oracle Enterprise Manager Cloud Control 13c Release 2

EMD setproperty succeeded

[oracle@oraem emd]$ emctl start agent

Oracle Enterprise Manager Cloud Control 13c Release 2

Starting agent ........................... started.

[oracle@oraem emd]$ emctl upload agent

Oracle Enterprise Manager Cloud Control 13c Release 2

---------------------------------------------------------------

EMD upload completed successfully

[oracle@oraem emd]$ emctl pingOMS

Oracle Enterprise Manager Cloud Control 13c Release 2

---------------------------------------------------------------

EMD pingOMS completed successfully

Now OEM host and OMS related target status will get clear.

Some OMS related target will still show DOWN on console

Follow Doc ID 1914829.1

Go to each of the affected target pages:

select the Oracle Management Service drop down menu (Top Left) > Target Setup > Monitoring Configuration > click on Save.

Now All OMS related targets are GREEN.

Connect to Repository database and execute below

1. SQL> alter trigger GSMADMIN_INTERNAL.GSMLOGOFF enable;

Trigger altered.

2. drop restore point before_oms_upgrade;

3. alter database flashback off;

UPGRADE AGENT

From the Setup menu à select Manage Cloud Control à then select Upgrade Agents.

For Job Name, accept the default job name, or enter a unique job name à

Click Add to select the Management Agents you want to upgrade à Click Submit.

[root@oraem ~]# /app/oracle/product/agent/agent_13.4.0.0.0/root.sh

Finished product-specific root actions.

/etc exist

[root@oraem ~]#

During the agent upgrade if you see issues while creating the blackout, follow the Doc ID 2641816.1

Agents Communication Issues After Upgrade from Enterprise Manager 13c Release 2 to 13c Release 4, In order to fix this issue, please follow the action plan from the document: 13.4: Upgrading 13.2 Agents to 13.4 Fails While Creating Blackout With Error: java.lang.Throwable: java.security.PrivilegedActionException: oracle.sysman.emSDK.agent.comm.exception.VerifyConnectionException: unable to connect to http server (Doc ID 2641816.1)]

****************APPLY OMS RU***************

Patch 31604791 Oracle Enterprise Manager 13c Release 4 Update 5 (13.4.0.5) for Oracle Management Service

Upgrade OMSPatcher

Take a backup

$ mv <OMS ORACLE_HOME>/OMSPatcher <OMS ORACLE_HOME>/OMSPatcher_old

$ unzip /backup/OMS13CR4/p19999993_134000_Generic.zip -d /app/oracle/product/13cR4/Middleware/

2. $ORACLE_HOME/OMSPatcher/omspatcher version

3. shut down the OMS

$ emctl stop oms

4. Apply RU

cd /backup/OMS13CR4/31604791

$ omspatcher apply

5. Start the OMS by running the following command:

$ emctl start oms

6.Run the following command on all the emcli installations:

$ emcli sync

*******APPLY AGENT PATCH******

Patch 31544641 Oracle Enterprise Manager 13c Release 4 Platform Update 5 (13.4.0.5) for Oracle Management Agent

$ORACLE_HOME/bin/emctl stop agent

cd /backup/OMS13CR4/31544641

$ORACLE_HOME/OPatch/opatch napply

$ORACLE_HOME/bin/emctl start agent

$ opatch lsinventory

********CLEAUP OLD 13CR2 HOME******

Detach the old OMS home.

/app/oracle/product/13cR2/Middleware/oui/bin/runInstaller -detachHome -force -allDepHomes -silent ORACLE_HOME= /app/oracle/product/13cR2/Middleware -waitForCompletion -invPtrLoc <OLD_OMS_HOME>/oraInst.loc

Detach the Oracle common directory.

/app/oracle/product/13cR2/Middleware/oui/bin/runInstaller -detachHome -force -allDepHomes -silent ORACLE_HOME=/app/oracle/product/13cR2/Middleware/oracle_common -waitForCompletion -invPtrLoc /app/oracle/product/13cR2/Middleware/oracle_common/oraInst.loc

Check whether any processes are running from the old middleware home.

ps -ef | grep /app/oracle/product/13cR2/Middleware

ps -ef | grep -I oms12c

If no processes are running from the old middleware home, then delete the old middleware home.

rm -rf /app/oracle/product/13cR2/Middleware

******ROLLBACK STEPS*****

Will do the rollback from the rman and tar backup.

1.Rollback OMS home

cd /app/oracle/product/13cR2/Middleware

tar -xzvf /OMS_HOME.tar.gz

start the oms 13.2

2. Rollback 13.2 agent

cd /app/oracle/product/agent

tar -xzvf /agent13c.tar.gz

start the agent 13.2

3.Restore database from rman backup.

Use the backup pieces taken in backup plan to restore.

connect target /;

startup nomount;

set nocfau;

restore controlfile from '<path>/oemprod/ctl_backup_1598291314862';

alter database mount;

restore database;

recover database until time "to_date('09-SEP-2020 10:52:34','DD-MON-YYYY HH24:MI:SS')";

alter database open resetlogs;

exit;

1 comment:

Anonymous27 April 2022 at 19:58
Thanks for sharing. I have upgrading 13cr2 to 13cr4 .
In the last part at start oms I'm getting below:

Oracle Management Server is not functioning because of the following reason:
Plugin's Repository version is not compatible with Plugin's OMS version. Check server log files.
Check the following log files:
EM log files: /u01/app/gc_inst2/em/EMGC_OMS1/sysman/log/emctl.log, emoms.trc, emoms_pbs.trc
JVMD Engine is Up
BI Publisher Server is Up

Checking the plugin information in repository and OMS:

PluginId:Version:Revision deployed on Repository is : oracle.dba.odba:13.2.4.0.0:0 (Oracle Database Appliance)
PluginId:Version:Revision deployed on OMS is : (null)

Any idea ? download the latest ODA Plugin compatible with the OMS version ?

Wednesday, 6 January 2021

Upgrade OEM Cloud Control from Version 13.2 to 13.4

1 comment: