Apply Holistic Patch to OMS

Holistic Patching for Oracle Enterprise Manager

This blog outlines how holistic patching works and provides an example of it in action. Holistic patching for Enterprise Manager is a newly announced(May 2024) method for applying all stack patch bundles for a given release by Oracle across all its components. Sumesh Balakrishnan from Product Management of EMCC has a blog post(Holistic Patching – a modern approach for Security Patch Management) about this new method and also How To Apply/Rollback Holistic Patch (SPB, CPU, and JDK) On OEM 13.5 (Doc ID 3002450.1) document explains all the steps. I will use them as a guide.

Patching Enterprise Manager Cloud Control is challenging because it involves 10-15 different components that require patching, such as OHS, WLS, OPSS, ADR, ADF, RDA, OWSM, JDK and OPatch. Some components require a maintenance window, and it takes hours to fully patch the enire system. In my environment, Oracle Enterprise Manager Cloud Control is effectively used, primarily for Fleet Patching.

Holistic patching simplifies patch management by consolidating updates into a single bundle for the quarterly cycle, reducing complexity and downtime. This efficiency allows organizations to focus more on core activities. When patching all the stack for EMCC, the biggest challenge is keeping the JDK up to date, as it often has many prerequisite patches. For offline environments, downloading all the setups and using different patching methods (OMSPatcher, OPatch, Java, opatch napply, unzip, etc.) can be particularly cumbersome.

With the new methodology, only the OMSPatcher will be updated to the latest version, and all subsequent patching will be done using a simple command. Consolidating patch activities into one downtime window minimizes disruption and reduces the overall apply time since System and environment prechecks are performed once.

OMSPatcher now includes new parameters such as -spb_patch and -jdk_update. We will use the -spb_patch parameter to patch the entire stack. However, for OMS on AIX, the -jdk_update parameter must be explicitly included in the omspatcher apply command. For other Unix platforms (LinuxX64, Solaris, etc.), the -jdk_update parameter is not needed, as the JDK will be updated automatically as part of the apply command.

According to the Readme of Patch 36635982, the patches included in this Holistic Patch are provided below. It will be awesome to patch all at once. It is a big bundle stack patch that includes(OHS,OPSS,WLS etc.) all except database.

  • Bug 36348444 ADF BUNDLE PATCH 12.2.1.4.240228
  • Bug 34809489 PS4 : PATCH CONFLICT OBSERVED BETWEEN 34647149 AND 34604561
  • Bug 35965629 – ADR FOR WEBLOGIC SERVER 12.2.1.4.0 – SIZE OPTIMIZED FOR JAN 2024
  • Bug 36410345 Coherence 12.2.1.4 Cumulative Patch 21 (12.2.1.4.21)
  • Bug 33093748 FMW PLATFORM 12.2.1.4.0 SPU FOR APRCPU2021
  • Bug 36468190 FMW Thirdparty Bundle Patch 12.2.1.4.240401
  • Bug 32720458 Fix for Bug 32720458
  • Bug 35430934 MERGE REQUEST ON TOP OF 12.2.1.4.0 FOR BUGS 32720458 33607709
  • Bug 34153238 HTTPS PROXY CONFIGURATION IS NOT USED WHEN PROTOCOL IS CONFIGURED TO TCP
  • Bug 31657681 THREADS CONTEND FOR LOCK IN LOADFILEBASEDKEYSTORE WHEN OPENING TLS/SSL ENABLED JDBC CONNECTIONS
  • Bug 36270037 Oracle JDK 8 Update 411
  • Bug 28186730 OPATCH 13.9.4.2.15 FOR EM 13.5 AND FMW/WLS 12.2.1.4.0 and 14.1.1.0.0
  • Bug 36316422 OPSS Bundle Patch 12.2.1.4.240220
  • Bug 35024228 OSS BUNDLE PATCH 12.2.1.4.230128
  • Bug 34065178 MERGE REQUEST ON TOP OF 12.2.1.4.0 FOR BUGS 34010500 33903365
  • Bug 36402397 OWSM BUNDLE PATCH 12.2.1.4.240313
  • Bug 34831198 PERL PATCH FOR EM 13.5 FOR CVE-2022-43680: LIBEXPAT UPDATE TO 2.5.0
  • Bug 36187017 RDA release 24.2-2024416 for FMW 12.2.1.4.0
  • Bug 36349529 WebCenter Core Bundle Patch 12.2.1.4.240227
  • Bug 36440005 WLS PATCH SET UPDATE 12.2.1.4.240325
  • Bug 36636070 EM Stack Patch Bundle 13.5.0.0.0(ID:240520.101106) (Patch 36635982)
Holistic Patching of Entire OMS Stack
Holistic Patching of Entire OMS Stack

I will apply 36335368 Holistic Patch. Its prerequisites are OMS RU 21 or later on OMS_HOME. We have OMS RU 19 so we will apply release update on OMS.

  • OMS RU 21 (36172321) also requires one-off Patch 36492660.
  • If you choose to apply RU 22 (36335368), it also requires one-off patch 36634909.

First I will apply 36172321 OMS RU 22. It also has prerequisites and I have all in my inventory.

We have upgraded current ompspatcher version to the latest.

To avoid setting credential every time we will use the property file we have created before. It can be created with commands provided below.

This command creates config and key files. We provide them to the variables shown below.

Lets apply Release Update on OMS.

Now “One small step for man, one giant leap for dbakind”.

At the patching stage you may track which patches are getting applied currently by tailing the file in $OMS_HOME/.patch_storage/NApply/2024-06-10_11-25-34AM/patchlist.txt

Patching OMS Agents demands extra effort. We’ll handle their patching individually. However, this isn’t related to Holistic Patching.

Hope it helps.


Discover More from Osman DİNÇ


Comments

Leave your comment