How To Discover ExaCC/ExaCS in Enterprise Manager – Detailed

In this post I want to share the required steps to discover ExaCC or ExaCS in Oracle Enterprise Manager (EM). I’ll provide as much detail as possible.

  1. Make sure your EM is at least on 13.5 RU 16. If not, please apply RU 16 to EM. Follow this link if you want to know how to patch EM. HERE!
  2. You need to designate a “monitoring” agent for the discovery. Is recommended that this agent sits outside your Exadata rack and has access to the OCI REST APIs. More information HERE!
  3. Make sure this agent has both the Database and the Exadata plugins deployed and is patched to the same RU level as the OMS. HERE!
  4. The agent must be able to reach the OCI REST APIs. There are 3 ways to achieve this.
    a) You can use a Proxy
    b) You can use the OCI Management Gateway
    c) You can have direct network connection

    Below is a list of APIs that you will need access to:
    Either grant access to (*.oci.oraclecloud.com) or individual URLS:
    https://query.<oci_region>.oci.oraclecloud.com
    https://identity.<oci_region>.oci.oraclecloud.com
    https://database.<oci_region>.oci.oraclecloud.com
    https://wss.exacc.<oci_region>.oci.oraclecloud.com
    https://management-agent.<oci_region>.oci.oraclecloud.com
    https://certificatesmanagement.<oci_region>.oci.oraclecloud.com
    https://certificates.<oci_region>.oci.oraclecloud.com
    https://telemetry-ingestion.<oci_region>.oci.oraclecloud.com
    https://auth.<oci_region>.oci.oraclecloud.com
    https://objectstorage.<oci_region>.oci.oraclecloud.com

    You may also test that connectivity by executing:
    $ curl -v https://query.<oci_region>.oci.oraclecloud.com
  5. Create or use an OCI account that has access to read your Exadata racks. These are the policies I have used:
    allow group <domain/group name> to read database-family in compartment <compartment name>
    You can find more information about the required policies HERE!
  6. Setup API Keys for authentication. Please follow instructions in the MOS note below:
    EM13.5: Manage OCI Connectivity Named Credentials Test Failed with Invalid Private Key. (Doc ID 2792126.1)
  7. Create an EM Named Credential using the API Keys created on the previous step. More details HERE!
  8. You also need the proper Storage Server credentials. If you don specify them during the discovery process, Storage Server targets will not be discovered. Instructions on how to retrieve this credential can be found HERE!
    If you can’t retrieve these credentials, please open a Service Request with support.
  9. Discover your Exadata Infrastructure following the discovery wizard. More information HERE!

After finishing the discovery, you should have your Exadata Cloud target in EM. Please wait between 15 to 20 minutes for the target information to be populated.

If your network setup does not allow direct connectivity to the OCI REST APIs then you will have to use an internal Proxy or use the OCI Management Gateway. More information about the OCI Management Gateway can be found HERE!

There’s also a very good post from Simone about setting up the Management Gateway for the EM agents.
https://blogs.oracle.com/observability/post/setup-oem-agents-cloud-mgmt-gw

Update:
You will also have to modify 2 parameters. One at the OMS level and one at the agent level. Please follow below MOS notes:

OEM 13c : SSH Key Credential Test On a Host Target Fails With “Remote operation timed out.” (Doc ID 2415262.1)
EM 13.2: Agent Patching From EM Console Fails With Error “concurrent job tasks limit (50) has been reached” (Doc ID 2476803.1)

Thanks,
Alfredo

How To Monitor Oracle DBs On Docker Containers With EM 13c

This post continues the thread of DevOps and automation for the Oracle Database. During the last couple of months I’ve seen more interest in deploying Oracle Databases on Docker containers. Even more now that Oracle released full support of RAC Databases running on Docker.



After you deploy your first Oracle Database on Docker, several questions come into mind; like:

  • How do I monitor the status of the Oracle Database?
  • How do I manage the performance of the Oracle Database and the SQL’s being executed on it?
  • How do I alert on issues on a timely manner?

Well, if you have the same questions or concerns… you are not alone!

On this post, I’m trying to explain the process I followed in order to deploy an Oracle Enterprise Manager agent on a Docker container and how I do monitor and manage the Oracle Database running on it.

First things first. Just a quick recap of my environment.

  • Oracle Linux 7 host running Docker 19.03
  • Create a MACVLAN network on Docker. My network adapter is ens3 on the host running Docker.
sudo docker network create -d macvlan --subnet=192.168.56.0/24 --gateway=192.168.56.1 -o parent=ens3 orcl_nw
  • Create a Docker volume type “nfs” using an NFS share named /NFSSHARE
sudo docker volume create --driver local --opt type=nfs --opt o=addr=<nfs server>,rw,bg,hard,tcp,vers=3,timeo=600,rsize=32768,wsize=32768,actimeo=0 --opt device=:/NFSSHARE agentstorage
  • Pull the 19.3 Docker image from container-registry.oracle.com
sudo docker pull container-registry.oracle.com/database/enterprise:19.3.0.0
  • Create the Docker container using the recently pulled image and mounting the volume “agentstorage” into “/u01” inside the container
sudo docker create -t -i \
--name ol7-orcl --hostname ol7-orcl --user oracle --ip 192.168.56.101 \
-e ORACLE_SID=ORCL \
-e ORACLE_PDB=PDB1 \
-v agentstorage:/u01 \
container-registry.oracle.com/database/enterprise:19.3.0.0
  • Disconnect the bridged Docker network from the container
sudo docker network disconnect bridge ol7-orcl
  • Connect the container to the MACVLAN network
sudo docker network connect orcl_nw --ip 192.168.56.101 ol7-orcl
  • Start our Docker container
sudo docker start ol7-orcl
  • Review the startup process and the creation of the database
sudo docker logs -f ol7-orcl

At this point we have our Docker container and the ORCL database up and running. But now I need a way to connect my ORCL database to the external world. Because I’m running a MACVLAN, I can create another Docker container in the same network and install Oracle Enterprise Manager (EM) in order to monitor it. Or I can also install Oracle EM on the host running Docker and setup a network link and a route to my Docker container. Let’s do the second option.

sudo ip link add mydocker-net link ens3 type macvlan mode bridge
sudo ip addr add 192.168.56.1/32 dev mydocker-net
sudo ip link set mydocker-net up
sudo ip route add 192.168.56.0/24 dev mydocker-net

I now have connectivity between my host and the Docker container.

$ ping 192.168.56.101
PING 192.168.56.101 (192.168.56.101) 56(84) bytes of data.
64 bytes from 192.168.56.101: icmp_seq=1 ttl=64 time=0.056 ms
64 bytes from 192.168.56.101: icmp_seq=2 ttl=64 time=0.070 ms
64 bytes from 192.168.56.101: icmp_seq=3 ttl=64 time=0.062 ms
64 bytes from 192.168.56.101: icmp_seq=4 ttl=64 time=0.073 ms
64 bytes from 192.168.56.101: icmp_seq=5 ttl=64 time=0.070 ms

sh-4.2$ ping 192.168.56.1
PING 192.168.56.1 (192.168.56.1) 56(84) bytes of data.
64 bytes from 192.168.56.1: icmp_seq=1 ttl=64 time=0.064 ms
64 bytes from 192.168.56.1: icmp_seq=2 ttl=64 time=0.079 ms
64 bytes from 192.168.56.1: icmp_seq=3 ttl=64 time=0.043 ms
64 bytes from 192.168.56.1: icmp_seq=4 ttl=64 time=0.082 ms
64 bytes from 192.168.56.1: icmp_seq=5 ttl=64 time=0.077 ms

The next step is to have name resolution setup between both hosts. For the Docker container it was easy to setup the full host name into the external DNS service. For the host resolution inside the Docker container you can use static entries in the /etc/hosts file or use the Docker embedded DNS server. For my exercise, I setup an entry in my /etc/hosts file providing the host name and the IP address of the host where EM is running.

The rest of the process is very straight forward. I use the silent install option for the Oracle EM agent. Below link has the steps to download the agent binaries for your specific platform and version.



Once you have the ZIP file of the agent binaries. Then just copy it inside the NFS share and connect to the Docker container.

sudo docker exec -it --user oracle ol7-orcl /bin/sh

After you login to the container just follow the steps in the provided agent install guide. Update the response file with the required information and run agentDeploy.sh. Make sure that the Agent Home resides in the Docker volume created. For this exercise will be inside /u01 directory.

After the agent deploy succeeds disconnect from the Docker session and re-connect as root.

sudo docker exec -it --user root ol7-orcl /bin/sh

Execute root.sh inside the Agent Home directory.

Let’s now verify that our EM has a new host target named ol7-orcl and is up and running.

Docker Container ol7-orcl on Oracle Enterprise Manager

The next step is to discover the ORCL database in EM. You can change the DBSNMP password by logging to the Docker container, then use SQLPlus to change the password and unlock the account.

alter user dbsnmp identified by <password> account unlock;

After the database discovery, verify the database target in the EM console.

ORCL database home page

Now that you have both the host target and the database target you can set metrics, thresholds and notifications on them.

Another important option is that if you have Diagnostics and Tuning packs, you can also monitor performance, get AWR/ASH reports and use EM to graphically analyze performance issues.

ORCL performance information

Hope this post helps understand the options you have in order to setup the required monitoring for the Oracle databases running on Docker containers.

Thanks,
Alfredo

Oracle Enterprise Manager 13c Series – Patching

I wanted to create a video series covering the basics of Oracle Enterprise Manager 13c. These series are designed to provide insights on how to install, configure and manage Oracle Enterprise Manager 13.5.

This week we are going to cover the patching of Oracle Enterprise Manager 13.5.

Oracle Enterprise Manager 13c – Patching

Hope this is useful.

Thanks,
Alfredo

Patch Oracle Databases With Ansible and Enterprise Manager 13c

In a previous post I show you how you can integrate DevOps automation and orchestration tools to provision Oracle databases by leveraging Enterprise Manager (EM) and the Cloud Management Pack (CMP). Once provisioned, databases need to be fully maintained in terms of monitoring but most precisely patching.

Patching databases decreases the risk of breach by timely mitigating vulnerabilities, but in can be a daunting task for organizations. Manual patching is time consuming and error prone. Home grown scripts are difficult to maintain and they increase maintenance cost. So the question is, how can I automate the patching process and even better, how can I integrate it with my current orchestration workflow?

Let me explain how you can achieve all this by making use of Oracle’s Database Lifecycle Management Pack (DBLM) and CMP. DBLM’s Fleet Maintenance help us patch and upgrade Oracle databases at scale with minimum downtime. It makes use of Gold Images and out-of-place patching in order to achieve this.

Fleet Maintenance Benefits

All this functionality can be integrated with CMP’s DBaaS in order to provide and end-to-end automation solution. DBaaS exposes REST APIs that we could then call using the automation tool of choice. Database Administrators, end users or 3rd party tools can then use these features to patch Oracle databases.

DBaaS Automation Diagram

Do you want to learn more about this and even be able to try it? We’ve created an Oracle LiveLabs that cover’s all this functionality. This lab will guide you through the request of a PDB, setup DBaaS configuration, setup Fleet Maintenance and finally patch the PDB.

Follow the link below for the Oracle LiveLabs workshop.



If you are planning on attending to Oracle Cloud World this year and you want to learn more about this consider attending my session.

LRN3519: Deploy and Manage Oracle Databases with Ansible, Oracle Enterprise Manager 

See you in Vegas!!!

Thanks,
Alfredo

Oracle Enterprise Manager 13.5 RU7 Now Available!

Before I start this post I want to give a big shoutout to FeedSpot for ranking my blog in the Top 100 Best Oracle Blogs and Websites. It’s honestly an honor. Since the start of this blog the main goal was and still is to share knowledge with the community.

Being an Oracle ACE Alumni and able to share all this information with you is a privilege.

If you want to take a look at the list click below.



Going back to this post. Last week RU7 for Oracle Enterprise Manager (EM) was released. In this post I’ll share information on new features that may want you think on applying this RU as soon as possible.

Oracle EM has a monthly release update model. With every RU there are bug fixes and new features released in the product.

Some of the features that I’m eager to use are:

  • Dynamic Runbooks. They allow you to add your SOP’s to EM for consistent incident resolution.
  • Migration Workbench TTS support. Migration Workbench now supports the option to control the incremental backups and the final migration phase.
  • Fleet Maintenance scheduling enhancement. Now EM allows you to better control the Fleet Maintenance scheduling steps.
  • New STIG standard version. STIG version 2 Release 3 is now available in RU7.

For additional information on this release update go to below Oracle blog:



The patching procedure is very straight forward and will cover it very soon in the next post.

In the meantime I strongly recommend to review the latest Oracle EM documentation and get familiar with the process.

Happy patching,
Alfredo

Improve Oracle Database Security With Enterprise Manager 13c

IT Security is popular topic nowadays! We constantly hear news about data breaches, ransomware, malware, unauthorized access to IT systems, etc. IT organizations are constantly looking to keep their systems, networks and data safe and secure.

Today’s blog is about how Oracle Enterprise Manager (EM) can help Database Administrators to secure and harden the Oracle Databases they manage along with the hosts those databases are running on.

First things first. I strongly recommend to review the Oracle Database 19c Security Guide. This guide provides guidelines on how to secure the Oracle Database, harden the DB access, secure and encrypt the DB data and so.



Now let’s discuss some areas that database administrators should also look at in order to improve their security posture:

  • Timely apply security patches
  • Monitor database configuration and detect misconfigurations
  • Use industry and regulatory standards like STIG and CIS for the Oracle Database

All the features that we will be discussing today are part of the Oracle Database Lifecycle Management pack. This pack requires an additional license.

Timely apply security patches

Fleet Maintenance (FM) enables administrators to automate lifecycle activities such as database patching and upgrades. FM is a gold image subscription based model that allows to patch databases with minimum downtime by using out-of-place patching mechanisms. In-place patching is also available if you need to apply an emergency on-off patch.

Administrators have the ability to customize the patching process by adding custom pre/post scripts to patching operations. FM supports single instance, RAC databases, Grid Infrastructure, Multitenant and Data Guard configurations.

One thing to mention is the ability to get security patch recommendations as soon as they are published. EM connects to My Oracle Support (MOS) and checks for the availability of new security patches. As soon as a new security patch is released EM will let you know if your DB estate is compliant or not in terms of these patches.



Monitor database configuration and detect misconfigurations

Configuration and Drift Management helps you monitor the configuration of your DB estate, the hosts on where those DB’s are running as well as the Oracle Homes (OH) for those installations. EM allows you to create your own configuration templates based on the configuration settings you need to enforce. Any misconfiguration or drift away of your template will be automatically reported via the Drift Management dashboard and you can also receive alerts if you choose to.

Corrective Actions (CA) can also be created to automatically fix this misconfigurations in order to comply with the templates and reduce security risks.

How many times administrators issued an ALTER SYSTEM command with SPFILE scope and forgot about it? Well, you will know next time you bring your DB up after maintenance. EM helps you detect these changes before they become a production issue. It also help you track the history of configuration changes, save configuration information at a given time and also allows you to use this configuration information to be compared between targets.

Have you wonder, how many OH’s we have with this specific one-off patch?

How many DB’s we have running on this specific OS version?

Well, EM can help you answer all these questions using this configuration data.

One thing worth mentioning is that EM comes with hundreds on configuration collections. If you need to gather a very specific configuration that is not available out-of-the-box, you can create your own configuration extension and collect this automatically.



Use industry and regulatory standards like STIG and CIS for the Oracle Database

EM provides compliance standards to help customers meet regulatory standards like STIG and CIS. Oracle’s best practices are also included within the compliance framework. There are two available options for analysis.

  • Rule based analysis
  • Real-time change

Each option allow administrators understand where attentions needs to be put in order to harden the DB estate.

Using the compliance framework, EM will provide a score to each associated target along with all the violations that need to be remediated after each evaluation.



I also want to provide links to Oracle LiveLabs workshops available that cover the features discussed above.

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.



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.



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.



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.



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.



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.



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