Oracle Enterprise Manager - alfredokriegdba.com

Finding the Weblogic Password for the Oracle Enterprise Manager Marketplace Image

Oracle Enterprise Manager (EM) 13.4 is available in the Oracle Cloud Infrastructure Marketplace. This image is very flexible and allows you to choose between different EM Deployment sizes ranging from Simple (Single node) to Large (Multi-node) setups.

I decided to deploy a Simple configuration in order to test it out. The deployment wizard prompts you for several passwords including the Enterprise Manager (sysman), Agent registration, Database password, etc. But it never asks for the Weblogic console password. I first thought that the Weblogic console and Enterprise Manager (sysman) password were going to be the same, but for my surprise they weren’t.

The Marketplace image comes with RU 2 deployed and I need to apply the latest RU 3 to this Oracle EM installation and I must know the Weblogic console username and password in order to accomplish this.

In one of my previous posts, I explained how to apply this RU 3 to Oracle EM.

click here…

So, the question now is… What are the username and password for the Weblogic console? Is there any way to change them if I don’t know them?

There’s an MOS note available that explains how to change these passwords when the current password is known.

EM 12c , EM 13c: Steps for Modifying the Password for Weblogic and Nodemanager User Accounts in the Enterprise Manager Cloud Control Installation (Doc ID 1450798.1)

But in this case, I don’t know it. For some reason I remembered that someone posted a way to decrypt this password many years ago when we were running EM 12c. I’m glad that the browser search came back with the result I was looking for. Gokhan Atil posted the method in 2015. Below is the link to his post.

Click here…

Now is time to follow the steps and find that needed password.

[oracle@oms1 em]$ cd /u01/app/oracle/em/gc_inst_134/user_projects/domains/GCDomain/
[oracle@oms1 GCDomain]$ cat servers/EMGC_ADMINSERVER/security/boot.properties
# Generated by Configuration Wizard on Sat May 09 09:30:41 GMT 2020
username={AES}oK4uyE6/MrBQd+38zr+wSk5y4vTMkQjB19ZOri4sDOI=
password={AES}hUM4t0cbEIJRuluMPxGBN3yGom1M9jwxEhNeGByu+8vTnmbG+xOTR
[oracle@oms1 GCDomain]$ vi recoverpassword.java
#####Insert this content#######
public class recoverpassword {
 public static void main(String[] args)
 {
  System.out.println(
  new weblogic.security.internal.encryption.ClearOrEncryptedService(
  weblogic.security.internal.SerializedSystemIni.getEncryptionService(args[0]
   )).decrypt(args[1]));
  }
}
#####Code ends here#########
[oracle@oms1 GCDomain]$ . bin/setDomainEnv.sh
[oracle@oms1 GCDomain]$ javac recoverpassword.java
[oracle@oms1 GCDomain]$ java -cp $CLASSPATH:. recoverpassword \
> $DOMAIN_HOME {AES}oK4uyE6/MrBQd+38zr+wSk5y4vTMkQjB19ZOri4sDOI=
weblogic
[oracle@oms1 GCDomain]$ java -cp $CLASSPATH:. recoverpassword \
> $DOMAIN_HOME {AES}hUM4t0cbEIJRuluMPxGBN3yGom1M9jwxEhNeGByu+8vTnmbG+xOTR
*************

Voila! Now I have both the username and password for the Weblogic console. Now I can proceed and apply the RU 3 to the OMS instance.

Thanks and happy patching!
Alfredo

DevOps, Ansible and Oracle Enterprise Manager

As IT moves towards virtualization, cloud and hybrid environments, containers, agile developments, etc. Automation and orchestration tools are gaining popularity to build and deliver environments faster and efficiently.

In this post, I want to show how Oracle Enterprise Manager (EM) interacts with 3rd party tools and how this can be used to integrate EM’s functionality with DevOps tools like Ansible or Terraform for configuration management and automation.

Oracle Enterprise Manager (EM) offers a complete tool-set for monitoring, provisioning, upgrade and patching, consolidation, compliance, DBaaS, etc., for the Oracle Database. Oracle Enterprise Manager makes use of Plug-ins and managements packs in order to discover, monitor and manage targets. EM’s functionality can be further extended with connectors and the EM’s extensibility framework in order to interact with 3rd party tools.

More info…

You can interact with Oracle Enterprise Manager (EM) in several ways:

Oracle Enterprise Manager Console
Oracle Enterprise Manager Command Line Interface (EMCLI)
Management Repository Views
Web Service REST APIs
Executing SQL via REST APIs (13.4 only)

We can leverage all the EMCLI commands and REST API’s that Oracle EM exposes with tools like Ansible or Terraform for a complete automation and orchestration solution.

One of the requirements for Oracle EM to monitor and manage a target is to deploy an Oracle Management Agent (OMA) to the machine hosting the target. Many organizations use DevOps tools to deploy virtual machines in an automated fashion. We can integrate the Oracle EM’s agent deployment process with these tools. This helps to drive consistency and reduces the efforts and time that administrators spend deploying Oracle Management Agents.

Let’s deploy an OMA to a Linux host using Ansible and Oracle’s EMCLI interface.

First of all, I need to download and install Ansible in a test server. My test server is a small virtual machine running Oracle Linux 7.

[root@ansible-s02 ~]# yum install -y ansible
Loaded plugins: langpacks, ulninfo
ol7_UEKR5                                                | 2.8 kB     00:00
ol7_addons                                               | 2.8 kB     00:00
ol7_developer                                            | 2.8 kB     00:00
ol7_developer_EPEL                                       | 3.4 kB     00:00
ol7_ksplice                                              | 2.8 kB     00:00
ol7_latest                                               | 3.4 kB     00:00
ol7_oci_included                                         | 2.9 kB     00:00
ol7_optional_latest                                      | 2.8 kB     00:00
ol7_software_collections                                 | 2.8 kB     00:00
(1/19): ol7_UEKR5/x86_64/updateinfo                        |  64 kB   00:00
(2/19): ol7_developer/x86_64/primary_db                    | 544 kB   00:00
(3/19): ol7_developer_EPEL/x86_64/group_gz                 |  87 kB   00:00
(4/19): ol7_developer_EPEL/x86_64/updateinfo               | 6.3 kB   00:00
(5/19): ol7_addons/x86_64/updateinfo                       |  91 kB   00:00
(6/19): ol7_ksplice/updateinfo                             | 5.3 kB   00:00
(7/19): ol7_addons/x86_64/primary_db                       | 153 kB   00:00
(8/19): ol7_latest/x86_64/group_gz                         | 134 kB   00:00
(9/19): ol7_ksplice/primary_db                             | 964 kB   00:00
(10/19): ol7_latest/x86_64/updateinfo                      | 2.9 MB   00:00
(11/19): ol7_developer/x86_64/updateinfo                   | 7.2 kB   00:00
(12/19): ol7_UEKR5/x86_64/primary_db                       | 6.9 MB   00:00
(13/19): ol7_oci_included/x86_64/primary_db                | 211 kB   00:00
(14/19): ol7_optional_latest/x86_64/updateinfo             | 1.0 MB   00:00
(15/19): ol7_software_collections/x86_64/updateinfo        | 8.7 kB   00:00
(16/19): ol7_software_collections/x86_64/primary_db        | 4.9 MB   00:00
(17/19): ol7_developer_EPEL/x86_64/primary_db              |  12 MB   00:00
(18/19): ol7_latest/x86_64/primary_db                      |  24 MB   00:00
(19/19): ol7_optional_latest/x86_64/primary_db             | 4.7 MB   00:00
...
Installed:
  ansible.noarch 0:2.8.4-1.0.1.el7

Dependency Installed:
  python-httplib2.noarch 0:0.9.2-0.1.el7
  python-paramiko.noarch 0:2.1.1-9.el7
  python2-jmespath.noarch 0:0.9.4-1.el7
  python3.x86_64 0:3.6.8-13.0.1.el7
  python3-libs.x86_64 0:3.6.8-13.0.1.el7
  python3-pip.noarch 0:9.0.3-7.el7_8
  python3-setuptools.noarch 0:39.2.0-10.el7
  sshpass.x86_64 0:1.06-1.el7

Complete!

Ansible is now installed in the test machine. The Ansible installion will create a directory under “/etc” that contains the configuration, host inventory and roles.

[root@ansible-s02 ~]# cd /etc/ansible/
[root@ansible-s02 ansible]# ls
ansible.cfg  hosts  roles

Our next step is to edit the host inventory file and add both, our Oracle EM server and the machine where we want to deploy the OMA into. This will look similar to my configuration file below.

# This is the default ansible 'hosts' file.
#
# It should live in /etc/ansible/hosts
#
#   - Comments begin with the '#' character
#   - Blank lines are ignored
#   - Groups of hosts are delimited by [header] elements
#   - You can enter hostnames or ip addresses
#   - A hostname/ip can be a member of multiple groups

# Ex 1: Ungrouped hosts, specify before any group headers.

## green.example.com
## blue.example.com
## 192.168.100.1
## 192.168.100.10

# Ex 2: A collection of hosts belonging to the 'webservers' group

## [webservers]
## alpha.example.org
## beta.example.org
## 192.168.1.100
## 192.168.1.110

# If you have multiple hosts following a pattern you can specify
# them like this:

## www[001:006].example.com

# Ex 3: A collection of database servers in the 'dbservers' group

## [dbservers]
##
## db01.intranet.mydomain.net
## db02.intranet.mydomain.net
## 10.25.1.56
## 10.25.1.57

# Here's another example of host ranges, this time there are no
# leading 0s:

## db-[99:101]-node.example.com


[local]
127.0.0.1

[emserver]
10.0.0.28

[emtarget]
10.0.0.11

I also configured a password-less SSH connectivity between the Ansible test machine and both, the EM’s server and the server where I want to deploy the OMA into. After this, I’m going to verify the connectivity from Ansible to both servers.

[root@ansible-s02 ansible]# ansible emserver -m ping -u oracle
 [WARNING]: Platform linux on host 10.0.0.28 is using the discovered Python
interpreter at /usr/bin/python, but future installation of another Python
interpreter could change this. See https://docs.ansible.com/ansible/2.8/referen
ce_appendices/interpreter_discovery.html for more information.

10.0.0.28 | SUCCESS => {
    "ansible_facts": {
        "discovered_interpreter_python": "/usr/bin/python"
    },
    "changed": false,
    "ping": "pong"
}
[root@ansible-s02 ansible]# ansible emtarget -m ping -u oracle
 [WARNING]: Platform linux on host 10.0.0.11 is using the discovered Python
interpreter at /usr/bin/python, but future installation of another Python
interpreter could change this. See https://docs.ansible.com/ansible/2.8/referen
ce_appendices/interpreter_discovery.html for more information.

10.0.0.11 | SUCCESS => {
    "ansible_facts": {
        "discovered_interpreter_python": "/usr/bin/python"
    },
    "changed": false,
    "ping": "pong"
}

I see the SUCCESS flag on both of them. Now is time to develop my .yml file with all the necessary steps to deploy the OMA to the host.

Let’s pause for a minute and review all the available options to deploy an OMA to servers. The list below show’s these options:

Oracle Enterprise Manager Console
Oracle Enterprise Manager Command Line Interface (EMCLI)
Silent Mode
- Using the AgentPull script
- Using the agentDeploy script
- Using the RPM file

MORE info…

I decided to use EMCLI to deploy the OMA to a host in this example. The .yml file to deploy the OMA looks like:

- hosts: emtarget
  vars:
        emagent_port: 3874
        emagent_base: /u01/app/oracle/product/agent134c
  tasks:
    - name: check emagent port
      wait_for: port={{ emagent_port }} state=stopped timeout=1
    - name: creating base directory
      file: path={{ emagent_base }} state=directory owner="oracle" group="oinstall"
      tags: install

- hosts: emserver
  vars:
        emagent_port: 3874
        emagent_base: /u01/app/oracle/product/agent134c
        emagent_hostname: emtarget.oracle.com
        emagent_platform_id: 226
  tasks:
    - name: execute emcli
      command: "/u01/app/oracle/product/omshome/bin/emcli submit_add_host -host_names={{ emagent_hostname }} -platform={{ emagent_platform_id }} -installation_base_directory={{ emagent_base }} -credential_name=\"HOST_ORACLE\" -port={{ emagent_port }} -wait_for_completion"
      register: result

    - name: show results
      debug:
        var: result.stdout

Now is time to execute our Ansible Playbook.

[root@ansible-s02 ansible]# ansible-playbook emcli_deploy_agent.yml -u oracle

PLAY [emtarget] *************************************************************************************************************************************************************************************************************************************************************************************************************

TASK [Gathering Facts] ******************************************************************************************************************************************************************************************************************************************************************************************************
ok: [10.0.0.11]

TASK [check emagent port] ***************************************************************************************************************************************************************************************************************************************************************************************************
ok: [10.0.0.11]

TASK [creating base directory] **********************************************************************************************************************************************************************************************************************************************************************************************
ok: [10.0.0.11]

PLAY [emserver] *************************************************************************************************************************************************************************************************************************************************************************************************************

TASK [Gathering Facts] ******************************************************************************************************************************************************************************************************************************************************************************************************
ok: [10.0.0.28]

TASK [execute emcli] ********************************************************************************************************************************************************************************************************************************************************************************************************
changed: [10.0.0.28]

TASK [show results] *********************************************************************************************************************************************************************************************************************************************************************************************************
ok: [10.0.0.28] => {
    "result.stdout": "Session Name : ADD_HOST_SYSMAN_Jun_26_2020_11:54:55_AM_EDT\nOverAll Status : Agent Deployment Succeeded\n\nHost                 Platform Name  Initialization  Remote Prerequisite  Agent Deployment  Error\nemtarget.oracle.com  Linux x86-64   Succeeded       Succeeded            Succeeded       "
}

PLAY RECAP ******************************************************************************************************************************************************************************************************************************************************************************************************************
10.0.0.11                  : ok=3    changed=0    unreachable=0    failed=0    skipped=0    rescued=0    ignored=0
10.0.0.28                  : ok=3    changed=1    unreachable=0    failed=0    skipped=0    rescued=0    ignored=0

Now let’s verify our agent deployment. I’m going to login to the Oracle Enterprise Manager Console and I should be able to see the details of the deployment.

Oracle Enterprise Manager Agent Deployment Dashboard

Here you go! The OMA was successfully deployed to my target host. I now need to manually execute the “root.sh” script, this because I didn’t specify a privileged credential during the deployment.

Hope this helps to demonstrate the flexibility of Oracle’s EM and also as an example on how to integrate it’s functionality with DevOps tools like Ansible. This is not by any means the best way to deploy an agent for your particular environment but rather an example of how to integrate EM with Ansible.

Thanks,
Alfredo

Applying Oracle Enterprise Manager 13.4 RU 3

Oracle Enterprise Manager (EM) Release Update (RU) 3 for 13.4 version was released early this month.

MORE INFO…

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 31299359 from MOS Doc ID 2647078.1

The overall steps are outlined below:

Download and unzip patch 31299359
Verify and make sure you meet the pre-reqs
Stop the Oracle Management Service
Apply the RU patch
Start the Oracle Mangement Service

As I previously mentioned, I downloaded and staged the patch in the Oracle EM VM. Now, let’s make sure we meet the pre-reqs.

This patch requires OPatch to be version 13.9.4.2.2 or higher and OMSPatcher version 13.9.4.0.0 or higher.

$ export ORACLE_HOME=/u01/OracleHomes/Middleware
$ export PATH=$PATH:$ORACLE_HOME/bin:$ORACLE_HOME/OPatch:$ORACLE_HOME/OMSPatcher/
$ cd /u01/OracleHomes/Middleware/
$ cd OMSPatcher/
$ ./omspatcher version
OMSPatcher Version: 13.8.0.0.3
OPlan Version: 12.2.0.1.16
OsysModel build: Thu Oct 25 18:18:12 PDT 2018

OMSPatcher succeeded.
$ cd ../OPatch/
$ ./opatch version
OPatch Version: 13.9.4.2.2

OPatch succeeded.

As you can see from above output, we need to upgrade our OMSPatcher utility. Follow the instructions from MOS Doc ID 2646080.1.

After that, you will be ready to start patching.

$ ./omspatcher version
OMSPatcher Version: 13.9.4.1.0
OPlan Version: 12.2.0.1.16
OsysModel build: Thu Oct 25 18:18:12 PDT 2018

OMSPatcher succeeded.

Let’s now go to the directory where we are staging our patch and execute the OMSPatcher analyze command.

$ cd /home/oracle/Downloads/31299359/
$ omspatcher apply -analyze -property_file /home/oracle/property
OMSPatcher Automation Tool
Copyright (c) 2017, Oracle Corporation.  All rights reserved.


OMSPatcher version : 13.9.4.1.0
OUI version        : 13.9.4.0.0
Running from       : /u01/OracleHomes/Middleware
Log file location  : /u01/OracleHomes/Middleware/cfgtoollogs/omspatcher/opatch2020-06-08_11-54-31AM_1.log

OMSPatcher log file: /u01/OracleHomes/Middleware/cfgtoollogs/omspatcher/31299359/omspatcher_2020-06-08_11-54-40AM_analyze.log

Configuration Validation: Success

Running apply prerequisite checks for sub-patch(es) "31187620,31187594,31140458,30851102,31189032,31187677,31193101,31187644,31187611,30851078,31187552,31187567" and Oracle Home "/u01/OracleHomes/Middleware"...
Sub-patch(es) "31187620,31187594,31140458,30851102,31189032,31187677,31193101,31187644,31187611,30851078,31187552,31187567" are successfully analyzed for Oracle Home "/u01/OracleHomes/Middleware"


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


All log file names referenced below can be accessed from the directory "/u01/OracleHomes/Middleware/cfgtoollogs/omspatcher/2020-06-08_11-54-31AM_SystemPatch_31299359_1"

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

The following sub-patch(es) are applicable:

             Featureset                                                                                                   Sub-patches                                                                                                                                        Log file
             ----------                                                                                                   -----------                                                                                                                                        --------
  oracle.sysman.top.oms   31187620,31187594,31140458,30851102,31189032,31187677,31193101,31187644,31187611,30851078,31187552,31187567   31187620,31187594,31140458,30851102,31189032,31187677,31193101,31187644,31187611,30851078,31187552,31187567_opatch2020-06-08_11-54-39AM_1.log



Log file location: /u01/OracleHomes/Middleware/cfgtoollogs/omspatcher/31299359/omspatcher_2020-06-08_11-54-40AM_analyze.log

OMSPatcher succeeded.

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 -property_file /home/oracle/property
OMSPatcher Automation Tool
Copyright (c) 2017, Oracle Corporation.  All rights reserved.


OMSPatcher version : 13.9.4.1.0
OUI version        : 13.9.4.0.0
Running from       : /u01/OracleHomes/Middleware
Log file location  : /u01/OracleHomes/Middleware/cfgtoollogs/omspatcher/opatch2020-06-08_14-45-59PM_1.log

OMSPatcher log file: /u01/OracleHomes/Middleware/cfgtoollogs/omspatcher/31299359/omspatcher_2020-06-08_14-46-08PM_deploy.log                                                                                                                 

Configuration Validation: Success

Running apply prerequisite checks for sub-patch(es) "31187620,31187594,31140458,30851102,31189032,31187677,31193101,31187644,31187611,30851078,31187552,31187567" and Oracle Home "/u01/OracleHomes/Middleware"...                           
Sub-patch(es) "31187620,31187594,31140458,30851102,31189032,31187677,31193101,31187644,31187611,30851078,31187552,31187567" are successfully analyzed for Oracle Home "/u01/OracleHomes/Middleware" 
                         
...

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

The following artifact(s) have been successfully deployed:

               Artifacts                                                      Log file
               ---------                                                      --------
                     SQL       rcu_applypatch_original_patch_2020-06-08_15-06-36PM.log
                     SQL       rcu_applypatch_original_patch_2020-06-08_15-11-28PM.log
                     SQL       rcu_applypatch_original_patch_2020-06-08_15-12-13PM.log
                     SQL       rcu_applypatch_original_patch_2020-06-08_15-13-02PM.log
                     SQL       rcu_applypatch_original_patch_2020-06-08_15-13-35PM.log
                     SQL       rcu_applypatch_original_patch_2020-06-08_15-14-08PM.log
                     SQL       rcu_applypatch_original_patch_2020-06-08_15-14-47PM.log
                     SQL       rcu_applypatch_original_patch_2020-06-08_15-15-21PM.log
                     SQL       rcu_applypatch_original_patch_2020-06-08_15-15-57PM.log
                     SQL       rcu_applypatch_original_patch_2020-06-08_15-16-44PM.log
                     SQL       rcu_applypatch_original_patch_2020-06-08_15-17-33PM.log
                     SQL       rcu_applypatch_original_patch_2020-06-08_15-18-24PM.log
            MRS-commands             emctl_register_commands_2020-06-08_15-19-14PM.log
          MRS-procedures           emctl_register_procedures_2020-06-08_15-19-24PM.log
          MRS-procedures           emctl_register_procedures_2020-06-08_15-19-37PM.log
               MRS-swlib                emctl_register_swlib_2020-06-08_15-19-52PM.log
               MRS-swlib                emctl_register_swlib_2020-06-08_15-20-12PM.log
          MRS-targetType           emctl_register_targetType_2020-06-08_15-20-43PM.log
          MRS-targetType           emctl_register_targetType_2020-06-08_15-21-23PM.log
          MRS-targetType           emctl_register_targetType_2020-06-08_15-21-44PM.log
          MRS-targetType           emctl_register_targetType_2020-06-08_15-23-36PM.log
          MRS-targetType           emctl_register_targetType_2020-06-08_15-29-31PM.log
     MRS-storeTargetType      emctl_register_storeTargetType_2020-06-08_15-29-48PM.log
     MRS-storeTargetType      emctl_register_storeTargetType_2020-06-08_15-30-00PM.log
     MRS-storeTargetType      emctl_register_storeTargetType_2020-06-08_15-30-11PM.log
     MRS-storeTargetType      emctl_register_storeTargetType_2020-06-08_15-30-31PM.log
     MRS-storeTargetType      emctl_register_storeTargetType_2020-06-08_15-30-48PM.log
  MRS-default_collection   emctl_register_default_collection_2020-06-08_15-31-00PM.log
  MRS-default_collection   emctl_register_default_collection_2020-06-08_15-31-23PM.log
  MRS-default_collection   emctl_register_default_collection_2020-06-08_15-31-38PM.log
  MRS-default_collection   emctl_register_default_collection_2020-06-08_15-32-48PM.log
  MRS-default_collection   emctl_register_default_collection_2020-06-08_15-33-59PM.log
      MRS-omsPropertyDef       emctl_register_omsPropertyDef_2020-06-08_15-34-14PM.log
      MRS-omsPropertyDef       emctl_register_omsPropertyDef_2020-06-08_15-34-23PM.log
            MRS-jobTypes             emctl_register_jobTypes_2020-06-08_15-34-35PM.log
            MRS-jobTypes             emctl_register_jobTypes_2020-06-08_15-34-49PM.log
       MRS-systemStencil        emctl_register_systemStencil_2020-06-08_15-35-02PM.log
       MRS-systemStencil        emctl_register_systemStencil_2020-06-08_15-35-09PM.log
       MRS-systemStencil        emctl_register_systemStencil_2020-06-08_15-35-18PM.log
        MRS-gccompliance         emctl_register_gccompliance_2020-06-08_15-35-26PM.log
       MRS-derivedAssocs        emctl_register_derivedAssocs_2020-06-08_15-36-05PM.log


Log file location: /u01/OracleHomes/Middleware/cfgtoollogs/omspatcher/31299359/omspatcher_2020-06-08_14-46-08PM_deploy.log

OMSPatcher succeeded.

After the RU patch was successfully applied you’ll need to start the OMS back up.

$ 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 Successfully Started
BI Publisher Server is Up

We have now our OMS running 13.4 RU 3 version. But we are not done yet. There’s one important step that we need to perform and is to apply the RU 3 to our agents as well.

In order to do this we need to download patch 31270875 from MOS. All the bug remediation information about this patch is outlined in Doc ID 2657051.1

Note: You don’t have to upgrade the OPatch utility for the agent as is already running the required version (13.9.4.2.2)

$ export ORACLE_HOME=/u01/OracleHomes/agent/agent_13.4.0.0.0
$ cd /u01/OracleHomes/agent/agent_13.4.0.0.0/OPatch
$ ./opatch lsinventory
Oracle Interim Patch Installer version 13.9.4.2.2
Copyright (c) 2020, Oracle Corporation.  All rights reserved.


Oracle Home       : /u01/OracleHomes/agent/agent_13.4.0.0.0
Central Inventory : /u01/app/oraInventory
   from           : /u01/OracleHomes/agent/agent_13.4.0.0.0/oraInst.loc
OPatch version    : 13.9.4.2.2
OUI version       : 13.9.4.0.0
Log file location : /u01/OracleHomes/agent/agent_13.4.0.0.0/cfgtoollogs/opatch/opatch2020-06-09_11-27-05AM_1.log


OPatch detects the Middleware Home as "/u01/OracleHomes/agent/agent_13.4.0.0.0"

Lsinventory Output file location : /u01/OracleHomes/agent/agent_13.4.0.0.0/cfgtoollogs/opatch/lsinv/lsinventory2020-06-09_11-27-05AM.txt

--------------------------------------------------------------------------------
Local Machine Information::
Hostname: localhost
ARU platform id: 226
ARU platform description:: Linux_AMD64


Interim patches (1) :

Patch  29812738     : applied on Wed Mar 18 12:51:59 EDT 2020
Unique Patch ID:  -1558519023
   Created on 22 May 2019, 02:57:03 hrs PST8PDT
   Bugs fixed:
     20141119, 27548560, 19030178, 24011099, 25423296, 21344996, 19154304



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

OPatch succeeded.

Now is time to stop the agent and apply the RU patch.

$ cd /home/oracle/Downloads/31270875/
$ ls
30989011  31270875  README.html  README.txt
$ $ORACLE_HOME/bin/emctl stop agent
Oracle Enterprise Manager Cloud Control 13c Release 4
Copyright (c) 1996, 2020 Oracle Corporation.  All rights reserved.
Stopping agent ... stopped.
$ $ORACLE_HOME/OPatch/opatch napply
Oracle Interim Patch Installer version 13.9.4.2.2
Copyright (c) 2020, Oracle Corporation.  All rights reserved.


Oracle Home       : /u01/OracleHomes/agent/agent_13.4.0.0.0
Central Inventory : /u01/app/oraInventory
   from           : /u01/OracleHomes/agent/agent_13.4.0.0.0/oraInst.loc
OPatch version    : 13.9.4.2.2
OUI version       : 13.9.4.0.0
Log file location : /u01/OracleHomes/agent/agent_13.4.0.0.0/cfgtoollogs/opatch/opatch2020-06-09_11-34-58AM_1.log


OPatch detects the Middleware Home as "/u01/OracleHomes/agent/agent_13.4.0.0.0"

Verifying environment and performing prerequisite checks...
OPatch continues with these patches:   30989011  31270875

Do you want to proceed? [y|n]
y
User Responded with: Y
All checks passed.
Backing up files...
Applying interim patch '30989011' to OH '/u01/OracleHomes/agent/agent_13.4.0.0.0'

Patching component oracle.sysman.agent.ic, 13.4.0.0.0...
Applying interim patch '31270875' to OH '/u01/OracleHomes/agent/agent_13.4.0.0.0'

Patching component oracle.sysman.top.agent, 13.4.0.0.0...
Patches 30989011,31270875 successfully applied.
Log file location: /u01/OracleHomes/agent/agent_13.4.0.0.0/cfgtoollogs/opatch/opatch2020-06-09_11-34-58AM_1.log

OPatch succeeded.
$ $ORACLE_HOME/bin/emctl start agent
Oracle Enterprise Manager Cloud Control 13c Release 4
Copyright (c) 1996, 2020 Oracle Corporation.  All rights reserved.
Starting agent .................................... started.

The process is quite simple. Of course, I’m doing this in a test environment but you should do it too before attempting this in a production environment. For your production environment you want to make sure to have proper recovery settings in place and Oracle Management Repository backups.

Hope this helps to understand the patching process.

Happy patching!
Alfredo

Oracle Enterprise Manager Performance Hub

Oracle Enterprise Manager (EM) 13.4 RU 2 has just been released this month. You may noticed that starting from EM 13.3 PG, the Top Activity page has been decommissioned. The Performance Hub page is the one that is available and yes, is not using Flash. If you have concerns about no longer having access to your EM Flash based graphs once the Web browsers stop supporting it, then your best bet is to upgrade your EM system.

MORE HERE!

Let’s talk about the features available on the Performance Hub page.

First of all, keep in mind that this page requires the Database Diagnostics and Tuning packs. All the data used by this page is provided thanks to Oracle’s instrumentation and stored in the Automatic Workload Repository (AWR). In order to open the Performance Hub page, from the Database Home page navigate to Performance -> Performance Hub -> ASH Analytics.

Oracle Enterprise Manager Performance Menu

I’m dividing the ASH Analytics Home page into 5 main sections:

Performance Hub main timeline (red)
Tab selection between ASH Analytics and SQL Monitoring (blue)
Average Active Sessions graph (yellow)
SQL ID breakdown information (purple)
User Session breakdown information (green)

The Performance Hub main timeline shows the current database performance divided in three classes; CPU utilization, User I/O and Wait. You may try to relate this to the old Top Activity graph, this one has additional functionality though.

Using ASH analytics you can customize your performance analysis by adjusting the timeline selector. Remember that in the Top Activity page this was fixed to 5 minutes.

This becomes real handy when you try to isolate performance issues in the database. Once you select the desired timeline for you analysis, the bottom of the page will update based on you selection. Only data data falls under you selection will be displayed in sections 3,4 and 5.

On top of this, we still have the classic time related selectors and page refresh rate.

Using the tab selector you can quickly switch between ASH Analytics and SQL Monitoring.

Tab Selector

If you click on SQL Monitoring, sections 3, 4 and 5 of the ASH analytics page will be replaced with the SQL Monitoring session information table. Keep in mind that the information showed in the table will be limited by the timeline selector that we already discussed. Adjust you selection accordingly.

Let’s now move to the Average Active Sessions section. This section displays detailed information of the current active sessions in the database during the selected period of time. You have the flexibility to adjust the graph by changing the graph’s dimensions. By default the graph will use the Wait Class a the main dimension.

Apart of that you can also adjust the Maximum CPU limit line to show the limit based on the number of CPU’s, the number of CPU cores or you may decide to not show the limit at all.

Another option is to only show foreground sessions (default) or to also include background sessions. You can even choose on whether show the standard load graph or to switch into a heat map like chart and select as many dimensions as needed.

The bottom of the page will display two tables. The one on the left side will show all the SQL information and the one on the right side the session information. You should be pretty familiar with these as the old Top Activity page was showing them as well.

You can also customize the view of these two tables and adjust the dimension. By default is set to the Wait Class.

Last but not least is the ability to select a SQL ID from the table and either call SQL Tuning advisor or to create a SQL Tuning Set from the same page.

SQL Tuning Advisor / SQL Tuning Set Buttons

As you can see, this is not the old Top Activity page that we were used to, but definitively has more features and offers way more flexibility while working on monitoring or when trying to spot performance issues in the database.

Thanks,
Alfredo