Blog Feed

Provision Oracle Databases With Ansible and Enterprise Manager 13c

In this post I want to show you how Oracle Enterprise Manager 13c using the Cloud Management pack, can be easily integrated with DevOps automation and orchestration tools like Ansible in order to provision Oracle Databases.

These can be either single instance, multi-tenant container databases, pluggable databases, schemas or databases running on high availability clusters and Dataguard configurations. EM 13c implements pre-checks, best practices and processes to provision all these configurations in a secure, automated and controlled fashion.

We have created an step by step laboratory in the Oracle LiveLabs framework. This lab contains a demo environment and a workbook that guide through all the steps. This lab shows you how to provision a PDB using Ansible and Oracle Enterprise Manager 13c. It also shows you how to shutdown, start, resize and check the status of the PDB using Ansible.

With this kind of integration, enterprises can close the loop in terms of DevOps or CI/CD pipeline provisioning. They can provision the Virtual Machines, Application and Oracle Databases automatically.

Follow the link below for the Oracle LiveLabs demo.

click here…

Thanks,
Alfredo

Oracle Enterprise Manager 13c: Extensibility and Interoperability for DevOps

DevOps adoption helps customers to automate and standardize processes, accelerate software delivery while keeping control of the operations, monitoring and lifecycle management of the environment. Enterprises select a tool or toolset in order to support desired business goals. However, these selected tools often require deeper automation from specialized management tools like Oracle Enterprise Manager 13c.

Oracle Enterprise Manager 13c by making use of the Database Lifecycle Management and the Cloud Management packs, enables Database Administrators, Developers and DevOps teams to automate the monitoring and management of the Oracle Database. Some of the use cases inlclude:

  • Monitoring Setup Automation
  • Provision Oracle Databases
  • Database Lifecycle Automation
  • Automated Database Cloning
  • Metering and Chargeback
  • Mask Sensitive Data
DevOps Tools and Oracle Enterprise Manager 13c

Monitoring Setup Automation

Monitoring begins as soon as you deploy the Oracle Enterprise Manager agent to the target environment. There are several tasks performed by the administrator in order to achieve the desired level of monitoring for a particular target. Using DevOps orchestration tools combined with EM 13c, customers can automate the monitoring setup right after the OS environment is provisioned.

In a previous post I went through the details on how to deploy the EM Agent using Ansible.

click here…

Provision Oracle Databases

DevOps orchestration tools like Ansible, Chef, Terraform, etc., can easily integrate with EM 13c in order to provision Oracle databases. These can be either single instance, multi-tenant container databases, pluggable databases, schemas or databases running on high availability clusters and Dataguard configurations. EM 13c implements pre-checks, best practices and processes to provision all these configurations in a secure, automated and controlled fashion.

click here…

Database Lifecycle Automation

Once provisioned, Oracle databases need to be well maintained and secured by regularly applying patches and eventually upgraded to a higher release.  All these database lifecycle activity tasks can be automated by integrating EM 13c with orchestration DevOps tools. Oracle’s Database Lifecycle Management pack enables customers to streamline these tasks using their DevOps workflows.

click here…

Automated Database Cloning

Oracle EM 13c help to automate the process of cloning databases using different options as a source. Like RMAN backups, snapshots or live data. EM 13c Snap Clone simplifies the cloning process by creating space efficient clones. DevOps orchestration tools can make use of this functionality to provision fully functional copies of Oracle databases in minutes by cloning databases while keeping the storage needs to a minimum.

Metering and Chargeback

DevOps tools automate the delivery of Oracle databases, however the lack of accurate costing of usage may result in no knowledge of consumption trends affecting the ability to measure the business value of IT investments. EM 13c Chargeback tools can be enabled so resource usage and allocation of databases provisioned in conjunction with DevOps tools is properly tracked and presented through comprehensive reports to business units. Chargeback enables consumers to adjust their IT consumption and utilization rates, hence driving consumer accountability.

Data Masking

DevOps teams often require databases to be provisioned with data cloned from production sources or asking for continuous refresh from these sources. Database and security organizations are required to limit exposure of sensitive information while delivering database environments. EM 13c enables administrators to provide to DevOps teams an automated and secure method that is easily integrated with orchestration tools. Data masking works on sensitive data by replacing it with realistic but scrubbed data based on masking rules.

I will cover more step by step examples of these use cases in future posts.

Thanks,
Alfredo

How To Patch Oracle Enterprise Manager 13.5 RU1

Oracle Enterprise Manager (EM) 13.5 RU1 was released last week.

Click here…

In this post, I want to show you how to apply this RU to your Oracle Enterprise Manager environment.

Let me start by describing the environment that I’m using for this. Oracle Enterprise Manager 13.5 can be deployed both on-premises or in the Oracle Cloud (OCI). Oracle Enterprise Manager 13.5 is available in the OCI’s Marketplace. You have the ability to choose from both single-instance and multi-node EM deployment. This makes the process really straightforward and you can have an environment up and running with couple of clicks.

click here…

First of all. You need to download patch 332835392 that contains EM 13.5 RU1. I strongly recommend to take a look at MOS note 822485.1. This Note contains all the information about available RU’s and patches for your EM.

There are some pre-requisites needed before you can patch your EM.

  • The Oracle database hosting the EM repository (OMR) needs to be 19.11 or 19.12
  • OMSPatcher must be 13.9.5.0.0 or higher

The EM installation that comes from the OCI’s Marketplace already has 19.11 database for the OMR. However, I decided to apply patch 32904851. If you check the amount of patches included between RU11 and RU12, it’s a considerably list. Therefore, is a good idea to apply RU12 for the OMR.

Upgrading OMSPatcher to 13.9.5.0.0 was very straight forward. Follow MOS note 2809842.1 for additional information.

Let’s now patch EM with RU1. I analyzed the patch first.

omspatcher apply -analyze -invPtrLoc /u01/app//em135/middleware/oraInst.loc  OMSPatcher.OMS_DISABLE_HOST_CHECK=true
OMSPatcher Automation Tool
Copyright (c) 2017, Oracle Corporation.  All rights reserved.


OMSPatcher version : 13.9.5.0.0
OUI version        : 13.9.4.0.0
Running from       : /u01/app//em135/middleware
Log file location  : /u01/app//em135/middleware/cfgtoollogs/omspatcher/opatch2021-10-05_13-02-57PM_1.log

OMSPatcher log file: /u01/app//em135/middleware/cfgtoollogs/omspatcher/32835392/omspatcher_2021-10-05_13-02-59PM_analy

Please enter OMS weblogic admin server URL(t3s://emcc.marketplace.com:7102):>
Please enter OMS weblogic admin server username(weblogic):>
Please enter OMS weblogic admin server password:>

Enter SYS Password :
Checking if current repository database is a supported version
Current repository database version is supported


Prereq "checkComponents" for patch 32835403 passed.

Prereq "checkComponents" for patch 32941631 passed.

Prereq "checkComponents" for patch 32941696 passed.

Prereq "checkComponents" for patch 32941706 passed.
WARNING: Could not apply the patch "32860349" because the "oracle.sysman.empa.oms.plugin with version 13.5.1.0.0" cor

Prereq "checkComponents" for patch 32941575 passed.

Prereq "checkComponents" for patch 32941713 passed.

Prereq "checkComponents" for patch 32840049 passed.

Prereq "checkComponents" for patch 32835412 passed.
WARNING: Could not apply the patch "32941609" because the "oracle.sysman.bda.oms.plugin with version 13.5.1.0.0" core

Prereq "checkComponents" for patch 32941618 passed.
WARNING: Could not apply the patch "32941662" because the "oracle.sysman.emfa.oms.plugin with version 13.5.1.0.0" cor

Prereq "checkComponents" for patch 32941645 passed.

Prereq "checkComponents" for patch 32941673 passed.

Configuration Validation: Success


Running apply prerequisite checks for sub-patch(es) "32941713,32941618,32941631,32941696,32840049,32941645,32835403,3
Sub-patch(es) "32941713,32941618,32941631,32941696,32840049,32941645,32835403,32941673,32941706,32941575,32835412" are successfully analyzed for Oracle Home "/u01/app//em135/middleware"


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


All log file names referenced below can be accessed from the directory "/u01/app//em135/middleware/cfgtoollogs/omspatcher/2021-10-05_13-02-57PM_SystemPatch_32835392_1"

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

The following sub-patch(es) are applicable:

             Featureset                                                                                          Sub-patches                                                                                                                               Log file
             ----------                                                                                          -----------                                                                                                                               --------
  oracle.sysman.top.oms   32941713,32941618,32941631,32941696,32840049,32941645,32835403,32941673,32941706,32941575,32835412   32941713,32941618,32941631,32941696,32840049,32941645,32835403,32941673,32941706,32941575,32835412_opatch2021-10-05_13-03-28PM_1.log


The following sub-patches are incompatible with components installed in the OMS system:
32860349,32941609,32941662



--------------------------------------------------------------------------------
The following warnings have occurred during OPatch execution:
1)  Could not apply the patch "32860349" because the "oracle.sysman.empa.oms.plugin with version 13.5.1.0.0" core component of the "OMS" or the plug-in for which the patch is intended is either not deployed or deployed with another version in your Enterprise Manager system.
2)  Could not apply the patch "32941609" because the "oracle.sysman.bda.oms.plugin with version 13.5.1.0.0" core component of the "OMS" or the plug-in for which the patch is intended is either not deployed or deployed with another version in your Enterprise Manager system.
3)  Could not apply the patch "32941662" because the "oracle.sysman.emfa.oms.plugin with version 13.5.1.0.0" core component of the "OMS" or the plug-in for which the patch is intended is either not deployed or deployed with another version in your Enterprise Manager system.
--------------------------------------------------------------------------------
OMSPatcher Session completed with warnings.
Log file location: /u01/app//em135/middleware/cfgtoollogs/omspatcher/32835392/omspatcher_2021-10-05_13-02-59PM_analyze.log

OMSPatcher completed with warnings.

There are some warning for plug-ins that I don’t have deployed in my EM. I can proceed with applying RU1.

Run the following command in the Repository Database as the SYS user.

alter system set job_queue_processes=0 scope=both sid='*';

Run the following command in the Repository Database as the SYSMAN user.

exec emd_maintenance.remove_em_dbms_jobs;

commit;

Shutdown the OMS.

emctl stop oms

Apply RU1.

omspatcher apply -invPtrLoc /u01/app//em135/middleware/oraInst.loc  OMSPatcher.OMS_DISABLE_HOST_CHECK=true
OMSPatcher Automation Tool
Copyright (c) 2017, Oracle Corporation.  All rights reserved.


OMSPatcher version : 13.9.5.0.0
OUI version        : 13.9.4.0.0
Running from       : /u01/app//em135/middleware
Log file location  : /u01/app//em135/middleware/cfgtoollogs/omspatcher/opatch2021-10-05_13-10-26PM_1.log

OMSPatcher log file: /u01/app//em135/middleware/cfgtoollogs/omspatcher/32835392/omspatcher_2021-10-05_13-10-29PM_deploy.log

Please enter OMS weblogic admin server URL(t3s://emcc.marketplace.com:7102):>
Please enter OMS weblogic admin server username(weblogic):>
Please enter OMS weblogic admin server password:>

Enter SYS Password :
Checking if current repository database is a supported version
Current repository database version is supported


Prereq "checkComponents" for patch 32835403 passed.

Prereq "checkComponents" for patch 32941631 passed.

Prereq "checkComponents" for patch 32941696 passed.

Prereq "checkComponents" for patch 32941706 passed.
WARNING: Could not apply the patch "32860349" because the "oracle.sysman.empa.oms.plugin with version 13.5.1.0.0" core component of the "OMS" or the plug-in for which the patch is intended is either not deployed or deployed with another version in your Enterprise Manager system.

Prereq "checkComponents" for patch 32941575 passed.

Prereq "checkComponents" for patch 32941713 passed.

Prereq "checkComponents" for patch 32840049 passed.

Prereq "checkComponents" for patch 32835412 passed.
WARNING: Could not apply the patch "32941609" because the "oracle.sysman.bda.oms.plugin with version 13.5.1.0.0" core component of the "OMS" or the plug-in for which the patch is intended is either not deployed or deployed with another version in your Enterprise Manager system.

Prereq "checkComponents" for patch 32941618 passed.
WARNING: Could not apply the patch "32941662" because the "oracle.sysman.emfa.oms.plugin with version 13.5.1.0.0" core component of the "OMS" or the plug-in for which the patch is intended is either not deployed or deployed with another version in your Enterprise Manager system.

Prereq "checkComponents" for patch 32941645 passed.

Prereq "checkComponents" for patch 32941673 passed.

Configuration Validation: Success


Running apply prerequisite checks for sub-patch(es) "32941713,32941618,32941631,32941696,32840049,32941645,32835403,32941673,32941706,32941575,32835412" and Oracle Home "/u01/app//em135/middleware"...
Sub-patch(es) "32941713,32941618,32941631,32941696,32840049,32941645,32835403,32941673,32941706,32941575,32835412" are successfully analyzed for Oracle Home "/u01/app//em135/middleware"

To continue, OMSPatcher will do the following:
[Patch and deploy artifacts]   : Apply sub-patch(es) [ 32835403 32835412 32840049 32941575 32941618 32941631 32941645 32941673 32941696 32941706 32941713 ]
                                 Apply RCU artifact with patch "/u01/app//em135/middleware/.omspatcher_storage/32835403_Sep_16_2021_10_02_49/original_patch";
                                 Apply RCU artifact with patch "/u01/app//em135/middleware/.omspatcher_storage/32941631_Sep_16_2021_10_19_23/original_patch";
                                 Apply RCU artifact with patch "/u01/app//em135/middleware/.omspatcher_storage/32941696_Sep_16_2021_10_19_25/original_patch";
                                 Apply RCU artifact with patch "/u01/app//em135/middleware/.omspatcher_storage/32941706_Sep_16_2021_10_19_27/original_patch";
                                 Apply RCU artifact with patch "/u01/app//em135/middleware/.omspatcher_storage/32941575_Sep_16_2021_10_19_31/original_patch";
                                 Apply RCU artifact with patch "/u01/app//em135/middleware/.omspatcher_storage/32941713_Sep_16_2021_10_19_40/original_patch";
                                 Apply RCU artifact with patch "/u01/app//em135/middleware/.omspatcher_storage/32840049_Sep_16_2021_10_19_42/original_patch";
                                 Apply RCU artifact with patch "/u01/app//em135/middleware/.omspatcher_storage/32835412_Sep_16_2021_10_20_01/original_patch";
                                 Apply RCU artifact with patch "/u01/app//em135/middleware/.omspatcher_storage/32941618_Sep_16_2021_10_20_35/original_patch";
                                 Apply RCU artifact with patch "/u01/app//em135/middleware/.omspatcher_storage/32941645_Sep_16_2021_10_20_39/original_patch";
                                 Apply RCU artifact with patch "/u01/app//em135/middleware/.omspatcher_storage/32941673_Sep_16_2021_10_20_42/original_patch";
                                 Register MRS artifact "commands";
                                 Register MRS artifact "targetType";
                                 Register MRS artifact "storeTargetType";
                                 Register MRS artifact "default_collection";
                                 Register MRS artifact "omsPropertyDef";
                                 Register MRS artifact "jobTypes";
                                 Register MRS artifact "SecurityClassManager";
                                 Register MRS artifact "swlib";
                                 Register MRS artifact "procedures";
                                 Register MRS artifact "systemStencil";
                                 Register MRS artifact "discovery";
                                 Register MRS artifact "gccompliance";
                                 Register MRS artifact "derivedAssocs"


Do you want to proceed? [y|n]
y
User Responded with: Y
Stopping the OMS.....
Please monitor log file: /u01/app//em135/middleware/cfgtoollogs/omspatcher/2021-10-05_13-53-40PM_SystemPatch_32835392_9/stop_oms_2021-10-05_13-53-40PM.log


Applying sub-patch(es) "32835403,32835412,32840049,32941575,32941618,32941631,32941645,32941673,32941696,32941706,32941713"
Please monitor log file: /u01/app//em135/middleware/cfgtoollogs/opatch/opatch2021-10-05_13-10-58PM_1.log


Updating repository with RCU reference file "/u01/app//em135/middleware/.omspatcher_storage/32835403_Sep_16_2021_10_02_49/original_patch"

Updating repository with RCU reference file "/u01/app//em135/middleware/.omspatcher_storage/32941631_Sep_16_2021_10_19_23/original_patch" for plugin home "/u01/app//em135/middleware/plugins/oracle.sysman.cfw.oms.plugin_13.5.1.0.0"

Updating repository with RCU reference file "/u01/app//em135/middleware/.omspatcher_storage/32941696_Sep_16_2021_10_19_25/original_patch" for plugin home "/u01/app//em135/middleware/plugins/oracle.sysman.smf.oms.plugin_13.5.1.0.0"

Updating repository with RCU reference file "/u01/app//em135/middleware/.omspatcher_storage/32941706_Sep_16_2021_10_19_27/original_patch" for plugin home "/u01/app//em135/middleware/plugins/oracle.sysman.vt.oms.plugin_13.5.1.0.0"

Updating repository with RCU reference file "/u01/app//em135/middleware/.omspatcher_storage/32941575_Sep_16_2021_10_19_31/original_patch" for plugin home "/u01/app//em135/middleware/plugins/oracle.sysman.si.oms.plugin_13.5.1.0.0"

Updating repository with RCU reference file "/u01/app//em135/middleware/.omspatcher_storage/32941713_Sep_16_2021_10_19_40/original_patch" for plugin home "/u01/app//em135/middleware/plugins/oracle.sysman.am.oms.plugin_13.5.1.0.0"

Updating repository with RCU reference file "/u01/app//em135/middleware/.omspatcher_storage/32840049_Sep_16_2021_10_19_42/original_patch" for plugin home "/u01/app//em135/middleware/plugins/oracle.sysman.emas.oms.plugin_13.5.1.0.0"

Updating repository with RCU reference file "/u01/app//em135/middleware/.omspatcher_storage/32835412_Sep_16_2021_10_20_01/original_patch" for plugin home "/u01/app//em135/middleware/plugins/oracle.sysman.db.oms.plugin_13.5.1.0.0"

Updating repository with RCU reference file "/u01/app//em135/middleware/.omspatcher_storage/32941618_Sep_16_2021_10_20_35/original_patch" for plugin home "/u01/app//em135/middleware/plugins/oracle.sysman.emct.oms.plugin_13.5.1.0.0"

Updating repository with RCU reference file "/u01/app//em135/middleware/.omspatcher_storage/32941645_Sep_16_2021_10_20_39/original_patch" for plugin home "/u01/app//em135/middleware/plugins/oracle.sysman.ssa.oms.plugin_13.5.1.0.0"

Updating repository with RCU reference file "/u01/app//em135/middleware/.omspatcher_storage/32941673_Sep_16_2021_10_20_42/original_patch" for plugin home "/u01/app//em135/middleware/plugins/oracle.sysman.xa.oms.plugin_13.5.1.0.0"

Registering service "commands" with register file "/u01/app//em135/middleware/sysman/metadata/commands/commands.xml" for plugin id as "core"...
Please monitor log file: /u01/app//em135/middleware/cfgtoollogs/omspatcher/2021-10-05_13-53-40PM_SystemPatch_32835392_9/emctl_register_commands_2021-10-05_14-08-58PM.log


Registering service "commands" with register file "/u01/app//em135/middleware/plugins/oracle.sysman.db.oms.plugin_13.5.1.0.0/metadata/commands/commands.xml" for plugin id as "oracle.sysman.db"...
Please monitor log file: /u01/app//em135/middleware/cfgtoollogs/omspatcher/2021-10-05_13-53-40PM_SystemPatch_32835392_9/emctl_register_commands_2021-10-05_14-09-06PM.log


Registering service "targetType" with register file "/u01/app//em135/middleware/sysman/builtinplugins/oracle.sysman.oh/metadata/targetType/oracle_home.xml" for plugin id as "core"...
Please monitor log file: /u01/app//em135/middleware/cfgtoollogs/omspatcher/2021-10-05_13-53-40PM_SystemPatch_32835392_9/emctl_register_targetType_2021-10-05_14-09-15PM.log


Registering service "targetType" with register file "/u01/app//em135/middleware/plugins/oracle.sysman.am.oms.plugin_13.5.1.0.0/patched_metadata/13.5.1.0.0/targetType/32941713/oracle_dblra.xml" for plugin id as "oracle.sysman.am"...
Please monitor log file: /u01/app//em135/middleware/cfgtoollogs/omspatcher/2021-10-05_13-53-40PM_SystemPatch_32835392_9/emctl_register_targetType_2021-10-05_14-09-53PM.log


Registering service "targetType" with register file "/u01/app//em135/middleware/plugins/oracle.sysman.db.oms.plugin_13.5.1.0.0/patched_metadata/13.5.1.0.0/targetType/32835412/oracle_cman.xml" for plugin id as "oracle.sysman.db"...
Please monitor log file: /u01/app//em135/middleware/cfgtoollogs/omspatcher/2021-10-05_13-53-40PM_SystemPatch_32835392_9/emctl_register_targetType_2021-10-05_14-10-06PM.log


Registering service "storeTargetType" with register file "/u01/app//em135/middleware/sysman/metadata/targetType/host.xml" for plugin id as "core"...
Please monitor log file: /u01/app//em135/middleware/cfgtoollogs/omspatcher/2021-10-05_13-53-40PM_SystemPatch_32835392_9/emctl_register_storeTargetType_2021-10-05_14-12-18PM.log


Registering service "storeTargetType" with register file "/u01/app//em135/middleware/plugins/oracle.sysman.am.oms.plugin_13.5.1.0.0/patched_metadata/13.5.1.0.0/targetType/32941713/oracle_dblra.xml" for plugin id as "oracle.sysman.am"...
Please monitor log file: /u01/app//em135/middleware/cfgtoollogs/omspatcher/2021-10-05_13-53-40PM_SystemPatch_32835392_9/emctl_register_storeTargetType_2021-10-05_14-12-29PM.log


Registering service "storeTargetType" with register file "/u01/app//em135/middleware/plugins/oracle.sysman.db.oms.plugin_13.5.1.0.0/patched_metadata/13.5.1.0.0/targetType/32835412/oracle_cloud_adw.xml" for plugin id as "oracle.sysman.db"...
Please monitor log file: /u01/app//em135/middleware/cfgtoollogs/omspatcher/2021-10-05_13-53-40PM_SystemPatch_32835392_9/emctl_register_storeTargetType_2021-10-05_14-12-38PM.log


Registering service "default_collection" with register file "/u01/app//em135/middleware/sysman/metadata/default_collection/oracle_emd.xml" for plugin id as "core"...
Please monitor log file: /u01/app//em135/middleware/cfgtoollogs/omspatcher/2021-10-05_13-53-40PM_SystemPatch_32835392_9/emctl_register_default_collection_2021-10-05_14-12-49PM.log


Registering service "default_collection" with register file "/u01/app//em135/middleware/plugins/oracle.sysman.am.oms.plugin_13.5.1.0.0/patched_metadata/13.5.1.0.0/default_collection/32941713/oracle_dblra.xml" for plugin id as "oracle.sysman.am"...
Please monitor log file: /u01/app//em135/middleware/cfgtoollogs/omspatcher/2021-10-05_13-53-40PM_SystemPatch_32835392_9/emctl_register_default_collection_2021-10-05_14-13-12PM.log


Registering service "default_collection" with register file "/u01/app//em135/middleware/plugins/oracle.sysman.db.oms.plugin_13.5.1.0.0/patched_metadata/13.5.1.0.0/default_collection/32835412/oracle_cman.xml" for plugin id as "oracle.sysman.db"...
Please monitor log file: /u01/app//em135/middleware/cfgtoollogs/omspatcher/2021-10-05_13-53-40PM_SystemPatch_32835392_9/emctl_register_default_collection_2021-10-05_14-13-21PM.log


Registering service "omsPropertyDef" with register file "/u01/app//em135/middleware/sysman/metadata/omsProperties/definition/OMSPropDefinition.xml" for plugin id as "core"...
Please monitor log file: /u01/app//em135/middleware/cfgtoollogs/omspatcher/2021-10-05_13-53-40PM_SystemPatch_32835392_9/emctl_register_omsPropertyDef_2021-10-05_14-13-59PM.log


Registering service "jobTypes" with register file "/u01/app//em135/middleware/sysman/metadata/jobTypes/agentpatch/DeployPatchesOnAgent.xml" for plugin id as "core"...
Please monitor log file: /u01/app//em135/middleware/cfgtoollogs/omspatcher/2021-10-05_13-53-40PM_SystemPatch_32835392_9/emctl_register_jobTypes_2021-10-05_14-14-08PM.log


Registering service "jobTypes" with register file "/u01/app//em135/middleware/plugins/oracle.sysman.db.oms.plugin_13.5.1.0.0/metadata/jobTypes/NGCreateCRSCloneComponent.xml" for plugin id as "oracle.sysman.db"...
Please monitor log file: /u01/app//em135/middleware/cfgtoollogs/omspatcher/2021-10-05_13-53-40PM_SystemPatch_32835392_9/emctl_register_jobTypes_2021-10-05_14-14-21PM.log


Registering service "jobTypes" with register file "/u01/app//em135/middleware/plugins/oracle.sysman.db.oms.plugin_13.5.1.0.0/metadata/jobTypes/GEFExtractAgent.xml" for plugin id as "oracle.sysman.db"...
Please monitor log file: /u01/app//em135/middleware/cfgtoollogs/omspatcher/2021-10-05_13-53-40PM_SystemPatch_32835392_9/emctl_register_jobTypes_2021-10-05_14-14-37PM.log


Registering service "SecurityClassManager" with register file "/u01/app//em135/middleware/sysman/metadata/security/SecurityClass/dashboard_security_class.xml" for plugin id as "core"...
Please monitor log file: /u01/app//em135/middleware/cfgtoollogs/omspatcher/2021-10-05_13-53-40PM_SystemPatch_32835392_9/emctl_register_SecurityClassManager_2021-10-05_14-14-47PM.log


Registering service "swlib" with register file "/u01/app//em135/middleware/sysman/metadata/swlib/patch" for plugin id as "core"...
Please monitor log file: /u01/app//em135/middleware/cfgtoollogs/omspatcher/2021-10-05_13-53-40PM_SystemPatch_32835392_9/emctl_register_swlib_2021-10-05_14-14-56PM.log


Registering service "swlib" with register file "/u01/app//em135/middleware/plugins/oracle.sysman.db.oms.plugin_13.5.1.0.0/metadata/swlib/dbprovision/dbprov" for plugin id as "oracle.sysman.db"...
Please monitor log file: /u01/app//em135/middleware/cfgtoollogs/omspatcher/2021-10-05_13-53-40PM_SystemPatch_32835392_9/emctl_register_swlib_2021-10-05_14-15-09PM.log


Registering service "procedures" with register file "/u01/app//em135/middleware/plugins/oracle.sysman.cfw.oms.plugin_13.5.1.0.0/metadata/procedures/CfwOPCDiscoveryDP.xml" for plugin id as "oracle.sysman.cfw"...
Please monitor log file: /u01/app//em135/middleware/cfgtoollogs/omspatcher/2021-10-05_13-53-40PM_SystemPatch_32835392_9/emctl_register_procedures_2021-10-05_14-15-28PM.log


Registering service "procedures" with register file "/u01/app//em135/middleware/plugins/oracle.sysman.db.oms.plugin_13.5.1.0.0/metadata/procedures/CloudDataMigration.xml" for plugin id as "oracle.sysman.db"...
Please monitor log file: /u01/app//em135/middleware/cfgtoollogs/omspatcher/2021-10-05_13-53-40PM_SystemPatch_32835392_9/emctl_register_procedures_2021-10-05_14-15-38PM.log


Registering service "procedures" with register file "/u01/app//em135/middleware/plugins/oracle.sysman.ssa.oms.plugin_13.5.1.0.0/metadata/procedures/RegisterPDB.xml" for plugin id as "oracle.sysman.ssa"...
Please monitor log file: /u01/app//em135/middleware/cfgtoollogs/omspatcher/2021-10-05_13-53-40PM_SystemPatch_32835392_9/emctl_register_procedures_2021-10-05_14-15-56PM.log


Registering service "procedures" with register file "/u01/app//em135/middleware/plugins/oracle.sysman.xa.oms.plugin_13.5.1.0.0/metadata/procedures/XaCreateCluster.xml" for plugin id as "oracle.sysman.xa"...
Please monitor log file: /u01/app//em135/middleware/cfgtoollogs/omspatcher/2021-10-05_13-53-40PM_SystemPatch_32835392_9/emctl_register_procedures_2021-10-05_14-16-07PM.log


Registering service "systemStencil" with register file "/u01/app//em135/middleware/plugins/oracle.sysman.am.oms.plugin_13.5.1.0.0/patched_metadata/13.5.1.0.0/systemStencil/32941713/oracle_dblra.xml" for plugin id as "oracle.sysman.am"...
Please monitor log file: /u01/app//em135/middleware/cfgtoollogs/omspatcher/2021-10-05_13-53-40PM_SystemPatch_32835392_9/emctl_register_systemStencil_2021-10-05_14-16-17PM.log


Registering service "systemStencil" with register file "/u01/app//em135/middleware/plugins/oracle.sysman.db.oms.plugin_13.5.1.0.0/patched_metadata/13.5.1.0.0/systemStencil/32835412/rac_database.xml" for plugin id as "oracle.sysman.db"...
Please monitor log file: /u01/app//em135/middleware/cfgtoollogs/omspatcher/2021-10-05_13-53-40PM_SystemPatch_32835392_9/emctl_register_systemStencil_2021-10-05_14-16-26PM.log


Registering service "discovery" with register file "/u01/app//em135/middleware/plugins/oracle.sysman.db.oms.plugin_13.5.1.0.0/metadata/discovery/db_discovery.xml" for plugin id as "oracle.sysman.db"...
Please monitor log file: /u01/app//em135/middleware/cfgtoollogs/omspatcher/2021-10-05_13-53-40PM_SystemPatch_32835392_9/emctl_register_discovery_2021-10-05_14-16-35PM.log


Registering service "gccompliance" with register file "/u01/app//em135/middleware/plugins/oracle.sysman.db.oms.plugin_13.5.1.0.0/metadata/gccompliance/cis19c.xml" for plugin id as "oracle.sysman.db"...
Please monitor log file: /u01/app//em135/middleware/cfgtoollogs/omspatcher/2021-10-05_13-53-40PM_SystemPatch_32835392_9/emctl_register_gccompliance_2021-10-05_14-16-43PM.log


Registering service "derivedAssocs" with register file "/u01/app//em135/middleware/plugins/oracle.sysman.db.oms.plugin_13.5.1.0.0/metadata/derivedAssocs/dg_assoc_rules.xml" for plugin id as "oracle.sysman.db"...
Please monitor log file: /u01/app//em135/middleware/cfgtoollogs/omspatcher/2021-10-05_13-53-40PM_SystemPatch_32835392_9/emctl_register_derivedAssocs_2021-10-05_14-17-04PM.log

The job_queue_processes parameter is set to 0 in the repository database. Resetting the job_queue_processes parameter to default value 50 in the repository database to start the OMS. If 50 is not your default value for the job_queue_processes parameter, you should reset it to the preferred value post OMS patching.
Starting the oms
Please monitor log file: /u01/app//em135/middleware/cfgtoollogs/omspatcher/2021-10-05_14-17-24PM_SystemPatch_32835392_52/start_oms_2021-10-05_14-17-24PM.log


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


All log file names referenced below can be accessed from the directory "/u01/app//em135/middleware/cfgtoollogs/omspatcher/2021-10-05_14-17-24PM_SystemPatch_32835392_52"

Patching summary:
-----------------

Binaries of the following sub-patch(es) have been applied successfully:

                        Featureset                                                                                          Sub-patches                                                                                                                               Log file
                        ----------                                                                                          -----------                                                                                                                               --------
  oracle.sysman.top.oms_13.5.0.0.0   32835403,32835412,32840049,32941575,32941618,32941631,32941645,32941673,32941696,32941706,32941713   32835403,32835412,32840049,32941575,32941618,32941631,32941645,32941673,32941696,32941706,32941713_opatch2021-10-05_13-10-58PM_1.log


The following sub-patches are incompatible with components installed in the OMS system:
32860349,32941609,32941662

Deployment summary:
-------------------

The following artifact(s) have been successfully deployed:

                 Artifacts                                                        Log file
                 ---------                                                        --------
                       SQL         rcu_applypatch_original_patch_2021-10-05_14-00-14PM.log
                       SQL         rcu_applypatch_original_patch_2021-10-05_14-03-10PM.log
                       SQL         rcu_applypatch_original_patch_2021-10-05_14-03-48PM.log
                       SQL         rcu_applypatch_original_patch_2021-10-05_14-04-21PM.log
                       SQL         rcu_applypatch_original_patch_2021-10-05_14-04-53PM.log
                       SQL         rcu_applypatch_original_patch_2021-10-05_14-05-22PM.log
                       SQL         rcu_applypatch_original_patch_2021-10-05_14-05-56PM.log
                       SQL         rcu_applypatch_original_patch_2021-10-05_14-06-30PM.log
                       SQL         rcu_applypatch_original_patch_2021-10-05_14-07-11PM.log
                       SQL         rcu_applypatch_original_patch_2021-10-05_14-07-57PM.log
                       SQL         rcu_applypatch_original_patch_2021-10-05_14-08-28PM.log
              MRS-commands               emctl_register_commands_2021-10-05_14-08-58PM.log
              MRS-commands               emctl_register_commands_2021-10-05_14-09-06PM.log
            MRS-targetType             emctl_register_targetType_2021-10-05_14-09-15PM.log
            MRS-targetType             emctl_register_targetType_2021-10-05_14-09-53PM.log
            MRS-targetType             emctl_register_targetType_2021-10-05_14-10-06PM.log
       MRS-storeTargetType        emctl_register_storeTargetType_2021-10-05_14-12-18PM.log
       MRS-storeTargetType        emctl_register_storeTargetType_2021-10-05_14-12-29PM.log
       MRS-storeTargetType        emctl_register_storeTargetType_2021-10-05_14-12-38PM.log
    MRS-default_collection     emctl_register_default_collection_2021-10-05_14-12-49PM.log
    MRS-default_collection     emctl_register_default_collection_2021-10-05_14-13-12PM.log
    MRS-default_collection     emctl_register_default_collection_2021-10-05_14-13-21PM.log
        MRS-omsPropertyDef         emctl_register_omsPropertyDef_2021-10-05_14-13-59PM.log
              MRS-jobTypes               emctl_register_jobTypes_2021-10-05_14-14-08PM.log
              MRS-jobTypes               emctl_register_jobTypes_2021-10-05_14-14-21PM.log
              MRS-jobTypes               emctl_register_jobTypes_2021-10-05_14-14-37PM.log
  MRS-SecurityClassManager   emctl_register_SecurityClassManager_2021-10-05_14-14-47PM.log
                 MRS-swlib                  emctl_register_swlib_2021-10-05_14-14-56PM.log
                 MRS-swlib                  emctl_register_swlib_2021-10-05_14-15-09PM.log
            MRS-procedures             emctl_register_procedures_2021-10-05_14-15-28PM.log
            MRS-procedures             emctl_register_procedures_2021-10-05_14-15-38PM.log
            MRS-procedures             emctl_register_procedures_2021-10-05_14-15-56PM.log
            MRS-procedures             emctl_register_procedures_2021-10-05_14-16-07PM.log
         MRS-systemStencil          emctl_register_systemStencil_2021-10-05_14-16-17PM.log
         MRS-systemStencil          emctl_register_systemStencil_2021-10-05_14-16-26PM.log
             MRS-discovery              emctl_register_discovery_2021-10-05_14-16-35PM.log
          MRS-gccompliance           emctl_register_gccompliance_2021-10-05_14-16-43PM.log
         MRS-derivedAssocs          emctl_register_derivedAssocs_2021-10-05_14-17-04PM.log


--------------------------------------------------------------------------------
The following warnings have occurred during OPatch execution:
1)  Could not apply the patch "32860349" because the "oracle.sysman.empa.oms.plugin with version 13.5.1.0.0" core component of the "OMS" or the plug-in for which the patch is intended is either not deployed or deployed with another version in your Enterprise Manager system.
2)  Could not apply the patch "32941609" because the "oracle.sysman.bda.oms.plugin with version 13.5.1.0.0" core component of the "OMS" or the plug-in for which the patch is intended is either not deployed or deployed with another version in your Enterprise Manager system.
3)  Could not apply the patch "32941662" because the "oracle.sysman.emfa.oms.plugin with version 13.5.1.0.0" core component of the "OMS" or the plug-in for which the patch is intended is either not deployed or deployed with another version in your Enterprise Manager system.
--------------------------------------------------------------------------------
OMSPatcher Session completed with warnings.
Log file location: /u01/app//em135/middleware/cfgtoollogs/omspatcher/32835392/omspatcher_2021-10-05_13-10-29PM_deploy.log

OMSPatcher completed with warnings.

As you can see, the patching process completed. Now I have EM 13.5 with RU1 applied.

There are additional notes I want to mention in case you need to install EM 13.5.

If you need Database Templates 19.11 for EM 13.5 either for Single Instance (SI) or Pluggable Database (PDB), you can find them below.

click here…

On the other hand. If you need to upgrade your EM from 13.3 or 13.4 to 13.5, take a look at this upgrade checklist located at MOS note 2761728.1.

Happy patching!!!
Alfredo

Oracle Enterprise Manager 13c Snap Clone Demo

The database cloning process can be often time consuming, resource intensive and expensive especially for large multi-terabyte databases. This can lead to miss project deadlines or to cause that storage costs grow out of control.

Enterprise Manager 13c Snap Clone instant database cloning allows administrators to create fully functional copies of databases using the capabilities of the underlying storage layer. Snap Clone is also capable to use Data Masking Definitions in order to securely manage test data.

Below video is a demonstration on how to setup Snap Clone with the ZFS storage appliance in order to clone either single instance or pluggable databases (PDBs).

For additional information about Snap Clone capabilities click below.

Click here…

Thanks,
Alfredo

Oracle Database Performance Diagnostics, Tuning and Validation with Oracle Enterprise Manager 13c Workshops

Last month we held 2 workshops where we went through some capabilities of Oracle Enterprise Manager 13c that help with performance diagnostics, tuning and validation for the Oracle Database.

If you were not able to attend and you want to learn about these capabilities, I recommend you take a look at the recording using the link below.

Session 1: August 4th 2021

Click here…

Session 2: August 25th 2021

click here…

Thanks,
Alfredo

Upgrade Your DB to 19c As A PDB using Enterprise Manager 13c

With Oracle Database 19c being the long term release, makes sense to start planning the upgrade of the DBs running on previous releases. Even better, what about converting Non-CDB databases into PDBs at the same time?

Using Oracle Enterprise Manager (EM) 13c, we can kill two birds with one stone. That is upgrade our DBs to 19c and migrate them into a PDB at the same time.

How this works? First of all, this functionality is part of the Database Lifecycle Management Pack. You can find the documentation for this feature along with all the pre-reqs below:

Click here

Let me guide you through this process.

In this environment I have a single instance database “orders”. As you can see on the screenshot below, is currently running version 18.10.

Orders DB Running 18.10 And Db19c Running 19.3 Version

Let’s now navigate to Enterprise -> Provisioning and Patching -> Database Provisioning

Database Provisioning Menu

Locate the Provision Pluggable Databases link under Related Links section

Provision Pluggable Databases Link

This will open the Provision Pluggable Database dashboard.

Provision Pluggable Databases Dashboard

Select the Container Database which is out target. Click on Migrate Existing Databases and then click the Launch button.

Select the desired migration method. You can choose between Data Pump Full Transportable Export and Import or Plug as a PDB. There are cons and pros on each method. Review the documentation previously shared so you can choose the best option for your migration.

For the purpose of this example we are going to choose Data Pump Full Transportable Export and Import.

Available Migration Methods

Now add the source DBs to be migrated.

Add DBs To Be Migrated
Select The Orders DB

Add or select the required Named Credentials and provide the path for the Export Directory.

Source Information

Provide the required Destination Information and click Next.

Destination Information

EM will execute compatibility and validation checks. If there are no errors click Close to proceed.

Validation Completed Successfully

Type a name for the EM job and select the desired schedule for it to run.

Schedule Information

Review all the information provided and click Submit.

Review Window

Wait for the Confirmation pop-up window and click View Job.

Confirmation Window

Monitor the progress of the deployment procedure until it completes.

Migration Deployment Procedure

Confirm that the db19c container DB now has the ORDERS PDB.

Orders PDB – db19c CDB

Click on the ORDERS PDB and verify the version information.

ORDERS PDB Dashboard

We now have migrated our orders DB into the db19c container running 19.3 version.

I also recommend to take a look at MOS Doc ID 2694986.1 before attempting the migration.

Hope this helps to ease the migration process for your DBs.

Thanks,
Alfredo

Upgrade Oracle Enterprise Manager to 13.5

Oracle Enterprise Manager 13.5 (EM) was just recently announced. The installation files along with the documentation are now available in the Oracle portal. The upgrade process is very similar to the one followed for 13.4.

You can find the process I followed to upgrade EM to 13.4 here:

Click HERE…

Let’s now get into the 13.5 upgrade process.

The same way as EM 13.4, this is an out of place upgrade. What is the significance of this? Well, you have to install a new Middleware home. Then the wizard will take care of all the required steps to upgrade EM using this new home.

My current environment details:

  • Oracle Enterprise Manager 13.4 RU 9 (Single OMS)
  • Oracle Database 19c RU 9 (OMR)
  • Oracle Linux 7 64-bit

Take a look at the

Oracle EM documentation and make sure you comply with all the pre-requisites before attempting the upgrade.

more info

It is recommended that you apply the latest RU to the Oracle Database hosting the Oracle Management Repository (OMR). Review and make sure you meet all the pre-requisites detailed in the upgrade guide.

Download the Oracle EM 13.5 software and stage it on your OMS server.

Click here
$ chmod +x em13500_linux64.bin
$ ./em13500_linux64.bin

Select an installation type. In this case will be an End-to-End upgrade. As you can see, the installer has been enhanced compared with the previous release.

I’m going to un-select the security updates box and click Next.

The wizard will run through a couple of checks and provide recommendations.

Review the output of each check and perform any required fix.

Type the location for the new Middleware home.

Enter the Database connection details for the OMR.

Fix the required Database checks.

You can click the Auto Fix button. Auto Fix won’t fix things you have to manually setup. In my case I had to execute the following:

  • Copy the emkey to repos
$ ./emctl config emkey -copy_to_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 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".
  • Shutdown the EM agent
$ cd $AGENT_HOME/bin
$ ./emctl stop agent
  • Shutdown OMS
$ cd $ORACLE_HOME/bin
$ ./emctl stop oms -all
Oracle Enterprise Manager Cloud Control 13c Release 4
Copyright (c) 1996, 2020 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

I ignored the MD5 check.

As previously stated. You have to verify that the DB hosting the OMR has all the required patched already applied.

Verify the plug-ins that are going to be upgraded to 13.5

Select additional plug-ins you want to install as part of this upgrade to 13.5

Type the WebLogic password and the location of the WebLogic base instance

Review all the upgrade inputs and click the Upgrade button

The upgrade wizard will perform all the required steps

Execute root scripts

$ sudo /u01/app/em135/middleware/allroot.sh

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

Starting to execute /u01/app/em135/middleware/root.sh ......
Check /u01/app/em135/middleware/install/root_emcc.marketplace.com_2021-05-10_23-16-24.log for the output of root script
Finished execution of  /u01/app/em135/middleware/root.sh ......

Oracle EM has been upgraded to 13.5

Now you should start you EM agent and start upgrading all of them.

All new features on 13.5 are described below.

click here…

As you can see, the process is very straight forward.

Happy upgrade!!!

Thanks,
Alfredo

Applying Oracle Enterprise Manager 13.4 RU 8

Oracle Enterprise Manager (EM) Release Update (RU) 8 for 13.4 version was released at the end of last month. Follow the link below to find out what’s included in this RU.

more info here…

In this post, I want to show you how to apply this RU to your Oracle Enterprise Manager environment.

Let me start by describing the environment that I’m using for this. Oracle Enterprise Manager 13.4 can be deployed both on-premises or in the Oracle Cloud (OCI). Oracle Enterprise Manager 13.4 is available in the OCI’s Marketplace. You have the ability to choose from both single-instance and multi-node EM deployment. This makes the process really straightforward and you can have an environment up and running with couple of clicks.

EM on marketplace…

For this example I’m going to be using the on-premises option. This means that Oracle EM 13.4 is also available for download as a VirtualBox image. This image comes as a single-instance EM deployment. Is worth to mention that this image is not recommended for anything but for testing.

Em on virtualbox…

I assigned 16 Gb of RAM and 2 virtual CPUs to this VirtualBox VM. Follow the instructions in the README file and start your environment. I also downloaded patch 32071974 from MOS Doc ID 2647078.1

For this RU, there are specific instructions about OPatch and OMSPatcher that we need to take attention to. The first one is that we need to upgrade OPatch and immediately after that apply the RU. If you are not planning to apply RU8 right away the advice is not to upgrade OPatch as the MOS note mentions that it may disrupt the environment.

Go ahead and download patch 28186730. Unzip the patch file into an staging area and execute the OPatch upgrade tool. Be sure that you have a valid backup of both, the Oracle Home and the EM configuration (export config).

$ $ORACLE_HOME/oracle_common/jdk/bin/java -jar /home/oracle/patches/6880880/opatch_generic.jar -silent oracle_home=$ORACLE_HOME
Launcher log file is /tmp/OraInstall2020-12-07_04-35-38PM/launcher2020-12-07_04-35-38PM.log.
Extracting the installer . . . . Done
Checking if CPU speed is above 300 MHz.   Actual 2245.782 MHz    Passed
Checking swap space: must be greater than 512 MB.   Actual 17151 MB    Passed
Checking if this platform requires a 64-bit JVM.   Actual 64    Passed (64-bit not required)
Checking temp space: must be greater than 300 MB.   Actual 25737 MB    Passed
Preparing to launch the Oracle Universal Installer from /tmp/OraInstall2020-12-07_04-35-38PM
Installation Summary


Disk Space : Required 34 MB, Available 37,853 MB
Feature Sets to Install:
        Next Generation Install Core 13.9.4.0.1
        OPatch 13.9.4.2.5
        OPatch Auto OPlan 13.9.4.2.5
Session log file is /tmp/OraInstall2020-12-07_04-35-38PM/install2020-12-07_04-35-38PM.log

Loading products list. Please wait.
 1%
 40%

Loading products. Please wait.
 42%
 43%
 45%
 46%
 48%
 49%
 50%
 51%
 52%
 54%
 55%
 57%
 58%
 60%
 61%
 62%
 64%
 65%
 67%
 68%
 70%
 71%
 72%
 74%
 75%
 77%
 78%
 80%
 81%
 82%
 84%
 85%
 87%
 88%
 90%
 91%
 92%
 94%
 95%
 97%
 98%
 99%

Updating Libraries



Starting Installations
 1%
 2%
 3%
 4%
 5%
 6%
 7%
 8%
 9%
 10%
 11%
 12%
 13%
 14%
 15%
 16%
 17%
 18%
 19%
 20%
 21%
 22%
 23%
 24%
 25%
 26%
 27%
 28%
 29%
 30%
 31%
 32%
 33%
 34%
 35%
 36%
 37%
 38%
 39%
 40%
 41%
 42%
 43%
 44%
 45%
 46%
 47%
 48%
 49%
 50%
 51%
 52%
 53%
 54%
 55%
 56%
 57%
 58%
 59%
 60%
 61%
 62%
 63%
 64%
 65%
 66%
 67%
 68%
 69%
 70%
 71%
 72%
 73%
 74%
 75%
 76%
 77%
 78%
 79%
 80%
 81%
 82%
 83%
 84%
 85%
 86%
 87%
 88%
 89%
 90%
 91%
 92%
 93%
 94%
 95%

Install pending
...
Saving the inventory oracle.glcm.opatch.common.api.classpath

The install operation completed successfully.

Logs successfully copied to /u01/app/oraInventory/logs.

Now is time to upgrade OMSPatcher to the latest version. Follow the instructions from MOS Doc ID 2646080.1.

$ omspatcher version
OMSPatcher Version: 13.9.4.4.0
OPlan Version: 12.2.0.1.16
OsysModel build: Tue Nov 03 18:16:07 PST 2020

OMSPatcher succeeded.

After that, you will be ready to start patching.

Let’s now go to the directory where we are staging our patch and execute the OMSPatcher analyze command. For this RU, I downloaded patch 32071974 and extracted into a staging directory in the server.

$ omspatcher apply -analyze
OMSPatcher Automation Tool
Copyright (c) 2017, Oracle Corporation.  All rights reserved.


OMSPatcher version : 13.9.4.4.0
OUI version        : 13.9.4.0.0
Running from       : /u01/app/oracle/product/em134/middleware
Log file location  : /u01/app/oracle/product/em134/middleware/cfgtoollogs/omspatcher/opatch2020-12-07_16-49-21PM_1.log

OMSPatcher log file: /u01/app/oracle/product/em134/middleware/cfgtoollogs/omspatcher/32071974/omspatcher_2020-12-07_16-49-26PM_analyze.log

...

OMSPatcher Session completed with warnings.
Log file location: /u01/app/oracle/product/em134/middleware/cfgtoollogs/omspatcher/32071974/omspatcher_2020-12-07_16-49-26PM_analyze.log

OMSPatcher completed with warnings.

Those warnings are expected as I don’t have some of those plug-ins deployed in this environment.

After you validate that there are no conflicts. Proceed to shutdown the Oracle Management Service (OMS).

$ emctl stop oms
Oracle Enterprise Manager Cloud Control 13c Release 4
Copyright (c) 1996, 2020 Oracle Corporation.  All rights reserved.
Stopping Oracle Management Server...
Oracle Management Server Successfully Stopped
Oracle Management Server is Down
JVMD Engine is Down

And now let’s execute the OMSPatcher command to apply the RU patch.

$ omspatcher apply
OMSPatcher Automation Tool
Copyright (c) 2017, Oracle Corporation.  All rights reserved.


OMSPatcher version : 13.9.4.4.0
OUI version        : 13.9.4.0.0
Running from       : /u01/app/oracle/product/em134/middleware
Log file location  : /u01/app/oracle/product/em134/middleware/cfgtoollogs/omspatcher/opatch2020-12-07_16-52-59PM_1.log

OMSPatcher log file: /u01/app/oracle/product/em134/middleware/cfgtoollogs/omspatcher/32071974/omspatcher_2020-12-07_16-53-05PM_deploy.log

...

--------------------------------------------------------------------------------
The following warnings have occurred during OPatch execution:
1)  Sub-patch "31812958" skipped as it is already been applied to the OMS system.
2)  Could not apply the patch "31802583" because the "oracle.sysman.vt.oms.plugin with version 13.4.1.0.0" core component of the OMS or the plug-in for which the patch is intended is either not deployed or deployed with another version in your Enterprise Manager system.
3)  Could not apply the patch "31894733" because the "oracle.sysman.am.oms.plugin with version 13.4.1.0.0" core component of the OMS or the plug-in for which the patch is intended is either not deployed or deployed with another version in your Enterprise Manager system.
4)  Could not apply the patch "30851102" because the "oracle.sysman.vi.oms.plugin with version 13.4.1.0.0" core component of the OMS or the plug-in for which the patch is intended is either not deployed or deployed with another version in your Enterprise Manager system.
5)  Could not apply the patch "31894749" because the "oracle.sysman.bda.oms.plugin with version 13.4.1.0.0" core component of the OMS or the plug-in for which the patch is intended is either not deployed or deployed with another version in your Enterprise Manager system.
6)  Could not apply the patch "31894832" because the "oracle.sysman.ssa.oms.plugin with version 13.4.1.0.0" core component of the OMS or the plug-in for which the patch is intended is either not deployed or deployed with another version in your Enterprise Manager system.
7)  Could not apply the patch "31894720" because the "oracle.sysman.emfa.oms.plugin with version 13.4.1.0.0" core component of the OMS or the plug-in for which the patch is intended is either not deployed or deployed with another version in your Enterprise Manager system.
8)  Could not apply the patch "31889317" because the "oracle.sysman.csm.oms.plugin with version 13.4.1.0.0" core component of the OMS or the plug-in for which the patch is intended is either not deployed or deployed with another version in your Enterprise Manager system.
9)  Could not apply the patch "31802539" because the "oracle.sysman.smf.oms.plugin with version 13.4.1.0.0" core component of the OMS or the plug-in for which the patch is intended is either not deployed or deployed with another version in your Enterprise Manager system.
--------------------------------------------------------------------------------
OMSPatcher Session completed with warnings.
Log file location: /u01/app/oracle/product/em134/middleware/cfgtoollogs/omspatcher/32071974/omspatcher_2020-12-07_16-53-05PM_deploy.log

OMSPatcher completed with warnings.

Verify the output of OMSPatcher. Let’s start the OMS.

$ emctl start oms
Oracle Enterprise Manager Cloud Control 13c Release 4
Copyright (c) 1996, 2020 Oracle Corporation.  All rights reserved.
Starting Oracle Management Server...
WebTier Successfully Started
Oracle Management Server Successfully Started
Oracle Management Server is Up
JVMD Engine is Up
Starting BI Publisher Server ...
BI Publisher Server Already Started
BI Publisher Server is Up

Login now to the OEM console and verify that EM is showing the latest RU.

Happy patching,
Alfredo

Adobe Flash End-Of-Life and Oracle Enterprise Manager

Adobe announced the End-Of-Life (EOL) for the Flash technology and this is happening December 31, 2020. As a result, most of the popular Web browsers also announced that Flash will be blocked the same day.

I’ve been blogging about this for more than a year now, explaining how this impacts Oracle Enterprise Manager’s (EM) database performance pages.

more info here…

If you are running EM on versions 13.3.1.0 and below you should upgrade now before browsers can’t display the database performance graphs.

After you upgrade to 13.3.2.0 (13.3 PG) or higher (13.4 is the recommended version), you have to get familiar with the fact that the Top Activity page has been deprecated. I also blogged about this last year.

more info here…

If you are considering upgrading to Oracle EM 13.4, also consider applying the latest Release Update (RU), at the time of this blog RU8 is the latest one. Take a look at MOS Doc ID 2647078.1.

I recommend you take a look at the November Advisor Webcast for Oracle Enterprise Manager. Kurt from the Product Manager team did a great job explaining this change.

Advisor Webcast Recording: Enterprise Manager (EM) – New OEM JET Pages and Flash End Of Life held on November 19, 2020 (Doc ID 2729947.1)

Thanks,
Alfredo