As Oracle annouced that new Oracle Enterprise Manager 13.4 release is now available for download!
To download it, you can either visit the Oracle Enterprise Manager downloads page or visit the Oracle Software Delivery Cloud.
We are going to upgrade from OEM 13.3 to OEM 13.4 with repository database 12.2.0.1.
Prerequisites for Upgrading to Enterprise Manager Cloud Control 13c Release 4
Database Patch Requirements
Ensure that you apply the latest PSU on the supported database.
It is mandatory to apply the latest DB PSU on the supported database before upgrading to Enterprise Manager Cloud Control 13.4.0.0.
Database Jan 2020 Release Update : 12.2.0.1.200114 (30593149)
To know how to apply latest PSU
[oracle@oemserver 30593149]$ opatch lspatches 30593149;Database Jan 2020 Release Update : 12.2.0.1.200114 (30593149) OPatch succeeded. [oracle@oemserver 30593149]$
Optimizer Adaptive Features Disabling Requirements
alter system set "_optimizer_nlj_hj_adaptive_join"= FALSE scope=both sid='*'; alter system set "_optimizer_strans_adaptive_pruning" = FALSE scope=both sid='*'; alter system set "_px_adaptive_dist_method" = OFF scope=both sid='*'; alter system set "_sql_plan_directive_mgmt_control" = 0 scope=both sid='*'; alter system set "_optimizer_dsdir_usage_control" = 0 scope=both sid='*'; alter system set "_optimizer_use_feedback" = FALSE scope=both sid='*'; alter system set "_optimizer_gather_feedback" = FALSE scope=both sid='*'; alter system set "_optimizer_performance_feedback" = OFF scope=both sid='*'; alter system set _allow_insert_with_update_check=true scope=both; alter system set job_queue_processes=0 scope=both;
Repository Table Snapshot Verification Requirements
SELECT COUNT (trigger_name) FROM sys.dba_triggers WHERE TRIGGERING_EVENT LIKE 'LOGON%' AND status='ENABLED'; SELECT trigger_name FROM sys.dba_triggers WHERE TRIGGERING_EVENT LIKE 'LOGON%' AND status='ENABLED'; SELECT COUNT (trigger_name) FROM sys.dba_triggers WHERE TRIGGERING_EVENT LIKE 'LOGOFF%' AND status='ENABLED'; SELECT trigger_name FROM sys.dba_triggers WHERE TRIGGERING_EVENT LIKE 'LOGOFF%' AND status='ENABLED'; Example alter trigger gsmadmin_internal.gsmlogoff disable; Drop snapshot log on em-violations;
EMKEY Copy Requirements
[oracle@oemserver ~]$ $OMS_HOME/bin/emctl config emkey -copy_to_repos Oracle Enterprise Manager Cloud Control 13c Release 3 Copyright (c) 1996, 2018 Oracle Corporation. All rights reserved. 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".
[oracle@oemserver ~]$ $OMS_HOME/bin/emctl status emkey Oracle Enterprise Manager Cloud Control 13c Release 3 Copyright (c) 1996, 2018 Oracle Corporation. All rights reserved. Enter Enterprise Manager Root (SYSMAN) Password : The EMKey is configured properly, but is not secure. Secure the EMKey by running "emctl config emkey -remove_from_repos".
OMS Backup Requirements
- Take a backup at OS level with tar.
- Take configuration backup.
[oracle@oemserver ~]$ $OMS_HOME/bin/emctl exportconfig oms -dir /u01/sw/dump Oracle Enterprise Manager Cloud Control 13c Release 3 Copyright (c) 1996, 2018 Oracle Corporation. All rights reserved. Enter Enterprise Manager Root (SYSMAN) Password : ExportConfig started... Backup directory is /u01/sw/dump 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 moredetails. Exporting configuration for pluggable modules... Preparing archive file... Backup has been written to file: /u01/sw/dump/opf_ADMIN_20200224_222406.bka The export file contains sensitive data. You must keep it secure. ExportConfig completed successfully!
Management Agent and OMS Shutdown Requirements
[oracle@oemserver ~]$ $OMS_HOME/bin/emctl status oms Oracle Enterprise Manager Cloud Control 13c Release 3 Copyright (c) 1996, 2018 Oracle Corporation. All rights reserved. WebTier is Up Oracle Management Server is Up JVMD Engine is Up BI Publisher Server is Up
[oracle@oemserver ~]$ $OMS_HOME/bin/emctl stop oms -all Oracle Enterprise Manager Cloud Control 13c Release 3 Copyright (c) 1996, 2018 Oracle Corporation. All rights reserved. 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
[oracle@oemserver ~]$ $AGENT_HOME/bin/emctl stop agent Oracle Enterprise Manager Cloud Control 13c Release 3 Copyright (c) 1996, 2018 Oracle Corporation. All rights reserved. Stopping agent ... stopped.
Then once the oms and the management agent are stopped, you can create one directory for new middleware home and go the directory and run the installer.
[oracle@oemserver sw]$ mkdir -p /u01/app/oracle/middleware_new [oracle@oemserver sw]$ cd oem_13.4/ -- where software has been download [oracle@oemserver oem_13.4]$ ls em13400_linux64-2.zip em13400_linux64-3.zip em13400_linux64-4.zip em13400_linux64-5.zip em13400_linux64-6.zip em13400_linux64-7.zip em13400_linux64.bin [oracle@oemserver oem_13.4]$ chmod u+x em13400_linux64.bin [oracle@oemserver oem_13.4]$ ./em13400_linux64.bin
I do not want to receive the security updates, so uncheck the box and click on “Next“.
Select “Skip” as I will completed all prerequisite and click on “Next“.
Make sure that all prerequisite should be succeeded and click on “Next“.
Note: I am ignoring the warning due to RAM crunch on my system.
Select the option ” Upgrade an existing EM System” and click on “Next“.
Enter the new location for middleware home which we created earlier and click on “Next“.
Confirm that you have backed up the Management Repository. As a prerequisite, you must back up the Management Repository before starting the upgrade process. If you have not already taken a backup, then do so immediately, and then return to the installer to continue with the upgrade.
Provide the SYS password and SYSMAN password and click on “Next“.
Review the plug-ins and click on “Next“.
Select the plug-ins which you want to use and click on “Next“.
Fill the detail for admin server and weblogic username & password and click on “Next“.
Check the “Enable BI Publisher” if you are using and click on “Next“.
Set the port if you are required and click on “Next“.
Review all the provided information and click on “Upgrade“.
Monitor the progress and keep checking the database as well & errors in logs.
At the end of the upgrade, you have to run connected as root from the new OMS home the shell root.sh.
Check the details for URL and click on “Close”
Check the version OEM and status of OMS after login to console.
You also check the version from command line.
[oracle@oemserver ~]$ $OMS_HOME/bin/emctl status oms Oracle Enterprise Manager Cloud Control 13c Release 4 Copyright (c) 1996, 2020 Oracle Corporation. All rights reserved. WebTier is Up Oracle Management Server is Up JVMD Engine is Up BI Publisher Server is Up [oracle@oemserver ~]$
After OMS upgrade has been completed. Now, we can upgrade the agents.
- 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.
Postupgrade steps after Upgrading to Enterprise Manager Cloud Control 13c Release 4.
- Delete the old OMS HOME
- Remove emkey copy.
[oracle@oemserver ~]$ $OMS_HOME/bin/emctl config emkey -remove_from_repos Oracle Enterprise Manager Cloud Control 13c Release 4 Copyright (c) 1996, 2020 Oracle Corporation. All rights reserved. Enter Enterprise Manager Root (SYSMAN) Password : The EMKey has already been removed from the Management Repository. [oracle@oemserver ~]$
- Reset Optimizer Adaptive Features for Oracle Database
alter system set job_queue_processes=100 scope=both; 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='*';
Enjoy Oracle Enterprise Manager 13c Release 4!Thank you for giving your valuable time to read the above information.
If you want to be updated with all our articles send us the Invitation or Follow us:
Skant Gupta’s LinkedIn: www.linkedin.com/in/skantali/
LinkedIn Group: Oracle Cloud DBAAS
Facebook Page: OracleHelp
Hi Guru,
I am going to upgrade multi OMS i.e. two nodes active/active. so do I have to perform 2 OMS upgrades on each node ?
Regrds
Sunil Kumar