Using AutoUpgrade, you can download patches for Oracle Enterprise Manager (OEM). It’s fast and convenient.
Get Those Patches
-
I use the latest version of AutoUpgrade.
wget https://download.oracle.com/otn-pub/otn_software/autoupgrade.jar -
I’ve already stored my MOS credentials in the AutoUpgrade keystore.
-
I create an AutoUpgrade config file:
global.global_log_dir=/home/oracle/autoupgrade/logs global.keystore=/home/oracle/autoupgrade/keystore global.download_folder=/home/oracle/patch-repo patch1.patch=OEM:24.1 patch1.target_version=19 patch2.patch=OEM:13.5 patch2.target_version=19- I use the
OEMkeyword to download patches for Oracle Enterprise Manager. - I want to get patches for versions 24.1 and 13.5.
- I use the
-
I start AutoUpgrade in download mode:
java -jar autoupgrade.jar -patch \ -config get-patches.cfg \ -mode download -
AutoUpgrade now downloads the patches:
AutoUpgrade Patching 26.6.260925 launched with default internal options Processing config file ... Loading AutoUpgrade Patching keystore AutoUpgrade Patching keystore is loaded ------------------------------------------------------ Downloading files to /Users/doverbyh/Downloads/patches ------------------------------------------------------ Oracle Enterprise Manager 24ai Release 1 Update 13 (24.1.0.13) for Oracle Management Service File: p39815035_241000_Generic.zip - LOCATED Oracle Enterprise Manager 24ai Release 1 Holistic Patch for Oracle Management Service - September 2026 File: p39984254_241000_Generic.zip - LOCATED Oracle Enterprise Manager 24ai Release 1 Update 13 (24.1.0.13) for Oracle Management Agent File: p39815042_241000_Generic.zip - LOCATED OMSPatcher patch of version 13.9.24.17.0 for Enterprise Manager 24.1.0.0.0 File: p19999993_241000_Generic.zip - LOCATED AgentPatcher patch of version 13.9.25.3.0 for Enterprise Manager 24.1.0.0.0 File: p33355570_241000_Generic.zip - LOCATED ------------------------------------------------------ ------------------------------------------------------ Downloading files to /Users/doverbyh/Downloads/patches ------------------------------------------------------ Oracle Enterprise Manager 13c Release 5 Update 34 (13.5.0.34) for Oracle Management Service File: p39820104_135000_Generic.zip - LOCATED Oracle Enterprise Manager 13c Release 5 Holistic Patch for Oracle Management Service - September 2026 File: p39984261_135000_Generic.zip - LOCATED Oracle Enterprise Manager 13c Release 5 Update 34 (13.5.0.34) for Oracle Management Agent File: p39820108_135000_Generic.zip - LOCATED OMSPatcher patch of version 13.9.5.27.0 for Enterprise Manager Cloud Control 13.5.0.0.0 File: p19999993_135000_Generic.zip - LOCATED AgentPatcher release of version 13.9.5.10.0 for Enterprise Manager Cloud Control Agent 13.5.0.0.0 File: p33355570_135000_Generic.zip - LOCATED ------------------------------------------------------ -
That’s it. Now I can take those patches and patch OEM. AutoUpgrade can’t help me with that part.
Notes
- AutoUpgrade downloads the following patches:
- Oracle Management Service Release Update
- Oracle Management Service Holistic Patch
- Oracle Management Agent Release Update
- OMSPatcher
- AgentPatcher
- OEM patches are generic, so there’s no need to specify a
platformin the config file. - You must also specify
target_versionin the config file, although AutoUpgrade doesn’t use it for OEM patches.That requirement will be removed in a later version of AutoUpgrade. - AutoUpgrade supports OEM versions 13.5 and 24.1. There will be no support for older releases.
- The patches are quite large. Have at least 15 GB per set of patches.
That’s It
Once again AutoUpgrade proves itself as the trusted aid of the DBA.
This enhancement came directly from customer feedback. What should we add next?
Happy patching!
Hey Daniel,such a great feature. I’ve already tried by myself.I’ve already left a question as a comment on Mike’s blog (not confirmed yet :-) ):Is it possible to additionally download agent one-offs like “WLS PATCHSET” or “OSS BUNDLE PATCH”?These are mentioned in every CPU announcement and we regularly install them.It would be really cool to include those into this automatic process. Am i miss something or is this a possible feature?Cheers
LikeLike
Hi,
I’m glad that you like the feature.
Let’s see what we can do about those extra patches. Do you mind dropping me an e-mail at daniel.overby.hansen (a) oracle.com. I got a few things to clear out.
Regards,
Daniel
LikeLike
Hey Daniel,
Cool that this now is possible too! Next to WLS and OWSM patches I would appreciate including the Java and Perl patches as well.
Kind regards,
Michael
LikeLiked by 1 person
Hi,
I’m glad that you like the feature.
Let’s see what we can do about those extra patches. Do you mind dropping me an e-mail at daniel.overby.hansen (a) oracle.com. I got a few things to clear out.
Regards,
Daniel
LikeLike
Hi Daniel,
i’ve send you an email.
Regards
Markus
LikeLike
Hi Daiel,
This is another great adjustment. But the problem is we also need the OPatch for OEM patching. Setting like “patch=OEM:24.1” doesnt download the OPatch, even putting smth like “patch=OEM:24.1, OPATCH” is not helping. So we need to use AutoUpgrade and visit Metalink
Thanks, Nariman
LikeLike
I’m glad you like this feature. We received feedback about a few extra OEM related patches, so we’re already working on an enhancement. This is what we plan to add:
– OPatch for EM via patch 28186730
– Latest Perl for EM
– Latest JDK for EM
– Latest WLS Patch Set Update
– Latest OWSM Bundle Patch
– Latest OSS Bundle Patch (only if patch=OEM:13.5)
– Latest version of Remote Diagnostics Agent (RDA)
That should be much better suited for Enterprise Manager patching.
I hope we can add this enhancement to one of the next two releases.
Regards,
Daniel
LikeLike
Hi Daniel,
Next would be also great to have AutoUpgrade to actually patch OEM. :-) Maybe you should think about two separate products: AutoUpgrade and AutoPatch, to reduce the scope and have less bugs.
and where can I find in the documentation all available Patch types that we can use in “patch=” parameter?
LikeLike
Hi,
We’d like to patch the entire world, but we’re doing it one step at a time. At least for a foreseeable future, AutoUpgrade will remain a database-centric, so it’s unlikely. But we can all dream.
The list of options for the “patch” parameter is in the documentation (you just need to know where to find it :D):
https://docs.oracle.com/en/database/oracle/oracle-database/26/upgrd/common-parameters-autoupgrade-config-file.html#GUID-A7E6221E-5964-4553-9A63-61B2E4AB1CBD
Regards,
Daniel
LikeLike