Enterprise Manager 13c – How to apply p23095307: enterprise manager for oms plugins 13.1.1.0.160429

Patch 23095307 is the newest system patch for the Enterprise Manager 13c family. This patch will be applied with the new patch tool OMSPatcher (see blog post http://dbakevlar.com/2016/05/em13c-applying-system-patches-with-the-oms-patcher from @dbakevlar for details). To apply this patch, the OMS has to be stopped.

Prerequisites

  • OMS 13.1.0.0.0
  • OMSPatcher 13.6.0.0.1 – I have installed it in directory /u00/app/oracle/product/em13cr1/OMSPatcher
  • URL / Username / Password from your EM13c Weblogic AdminServer (emctl status oms -details)
  • Patch 23095307 is unzipped and available in a local directory, in my case it’s in /u00/app/oracle/stage

The newest OMSPatcher can be downloaded according the My Oracle Support Note How to upgrade the OMSPatcher to latest version of OMSPatcher (Doc ID 2135028.1)

Patch Verification

For the verification you don’t have to shutdown the OMS. Be sure that your ORACLE_HOME is set to the EM13c installation directory.

As you can see, there is a WARNING in the output that a sub-patch is incompatible with the oracle.sysman.ssa.oms.plugin version 13.1.1.0.0. The SSA.OMS plugin is a plugin for the cloud self service zone. The patch 23092170 is the EM Cloud Plugin Bundle Patch 13.1.1.0.160429. I don’t have installed the cloud plugin during the installation of the EM13 because we don’t use it,  now the OMSPatcher wants this plugin.

Installation of the missing Plugins

To resolve the warning, I have installed the two missing plugins. The Oracle Cloud Application plugin requires the Oracle Virtualization plugin first. Attention: If you install the plugins on the Oracle Management Server, the OMS will be restarted during plugin installation process.

The Oracle Virtualization Plugin

plugin_virtualization

The Oracle Cloud Application Plugin

plugin_cloud

OMSPatcher Re-Analyze

Now the analyze job runs without any warnings or errors. I have removed some lines in the output for better reading.

The problem is solved, the system is ready to patch.

Patch apply

Before you apply the patch, you have to stop the OMS. Then you can apply it.

I have removed some output. if you want to have the full output, you can download it HERE.

Patch successfully applied

The patch is applied, the OMS can be started again. I don’t know why the patch needs the plugins. My understanding from the plugins is to have a small installation, and only the components which will be used should be configured. And at this point, personally I would expect only an INFORMATION  that some components are not installed so they not will be patched and not a WARNING.

The OMSPatcher is a new tool for the EM13c patching, maybe there are some improvements in one of the next releases.

Oracle Database Backup Service Configuration – java.net.UnknownHostException

In all the trials in the Oracle cloud in the past, I used the same syntax below to configure the Oracle Database Backup Service on my local servers. Last week I have decided to order the Service via shop.oracle.com. Now I am an official owner of an Oracle cloud account with a CSI :-). But back to my problem, after my account was created I got the mail with the configuration details. So far so good. Then I tried to configure the OPC package as always:

The installer didn’t found the hostname where my backup location should be located. I tried to verify if the REST endpoint URL was available, it was ok:

storage_test_api

The output from the installer file without any parameter shows me no additional information:

In the extracted opc_installer.jar file is a Java class file called OpcConfig.class. I used JD-GUI, a small Java decompiler, to take a look insight the Java class file. And at line 90 I found a new parameter which was not listed above – the -host.

opc_class

So why not try to install opc_installer.jar again and add this -host parameter?

Et voilà – the Oracle Database Backup Service is now configured and ready to use. Time to start RMAN 🙂

Enterprise Manager 13c – How to apply Patch 22505404: WLS PATCH SET UPDATE 12.1.3.0.160419

Since the 19th of April there is a new patch set available for Weblogic servers – Patch 22505404: WLS PATCH SET UPDATE 12.1.3.0.160419. This patchset has included 116 fixes and is a generic one. The patch is listed in the Enterprise Manager 13c as recommended. OPatch has no to be updated. This patch is not an online patch, you have to shut down your running EM13c server.

This blog post describes the apply of the Weblogic patch set update in an Enterprise Manager 13c environment running on a Oracle Linux server.

wls_patch_22505404

Prepare Patch Set Update on EM13c Server

The patch file has to be extracted. I have copied to file to a stage directory /u00/app/oracle/stage on the EM13c server.

Set ORACLE_HOME

Set the ORACLE_HOME variable to the directory where the Oracle Enterprise Manager 13c is located. In my example the EM13 is installed in directory /u00/app/oracle/product/em13cr1.

Stop running Oracle Enterprise Manager 13c

Apply Patch 22505404: WLS PATCH SET UPDATE 12.1.3.0.160419

Go to the extracted patch set directory:

Apply the patch:

You can ignore the warning message, it’s because OPatch has to rollback a previous installed patch.

Start Oracle Enterprise Manager 13c

Summary

Patching of the underlying Weblogic component has the same importance like patching the other components like databases and agents. Since Weblogic 12c is used for the Enteprise Manager,  patching can be done with the DBA well known OPatch tool which is very easy and good documented.