AutoUpgrade Patching – From Zero to Hero – Part 3: Download Patches

You completed Part 1 and Part 2 of this blog post series already? Then you are ready for AutoUpgrade Patching – From Zero to Hero – Part 3: Download Patches. Let us start simple, and then increase the scope to fetch the patches for various operating system platforms in your local patching folder.

Which download?

Strange headline – but you’ll see what I mean. At first, we need to clarify the various download options for patches.

1. Download patches directly from MOS/ARU by yourself
   This usually means that you go to the various MOS notes, such as KB106822 / 888.1 –  Primary Note for Database Quarterly Release Updates, KB188772 / 555.1 –  Oracle Database 19c and Oracle AI Database 26ai Important Recommended One-off Patches and KA958 Assistant: Download Reference for Oracle Database/GI Update, Revision, PSU, SPU(CPU), Bundle Patches, Patchsets and Base Releases.
   Can be boring? Yes, it can – and with patches not always be available at the same time, you need to check CPU58 to check for Post-Release (delayed) patches.
   .
2. Download patches with AutoUpgrade
   This is the exercise we are going to do here together – and it is important to understand the different download sources..
   1. Download everything from MOS/ARU
      This is basically the same way as if you would download the patches by yourself as shown in (1.) above. For Oracle Database 19c, there is one specific thing you must take into account if you go down this route: You must download the base release by yourself from eDelivery.oracle.com or from oracle.com manually.
   2. Download pre-baked Gold Images from Oracle Update Advisor (OUA)
      You will see below that this is the default approach AutoUpgrade takes. We download a pre-baked gold image, even for Oracle Database 19c, and then pull the additional fixes of your choice from MOS/ARU. This is the fastest and most efficient way to handle this.
   3. Download custom-built Gold Images from Oracle Update Advisor (OUA)
      This is an alternative where you request a complete custom-built gold image including all your fixes. It will take longer, usually about 2 hours, and this is optional but not the default.
      .
3. Download patches with other tools
   If you use Enterprise Manager already, OEM has the Lifecycle Management Pack which has gotten a license waiver for one year beginning from June 2026. In addition, you can use FPP (Fleet Patching and Provisioning) as an alternative, too. And of course, you can craft your own tools to download patches directly from OUA.
   .

Your database server has no internet access?

Of course, this is expected and quite normal. Therefore, I will separate the steps for patching into:

• Download
• Install
• Patch

If you wonder how we are downloading on a desktop and then later install on a DB server, watch this short video from our Virtual Classroom Seminar #21 and a quick demo.

• [38:29] Working without internet access
• [39:33] DEMO: Patch without internet access

Proxies

Many of you will be behind a proxy. Of course, we do offer various options. Again, Daniel has blogged about this, and I won’t repeat his whole blog post.

We allow multiple options for proxies:

[https|http|socks5|socks]://(user_info@)site:port

For instance,

export https_proxy=https://hugo:OracleHero001@proxy.mysite.net:8080

Which URLs must be accessible?

Please make sure these URLs are accessible when you want to automate patching from the machine you start the download from:

For MOS:

https://login-ext.identity.oraclecloud.com
https://updates.oracle.com
https://aru-akam.oracle.com

For Latest AU:

https://edelivery.oracle.com

For OUA:

https://transport.oracle.com
https://objectstorage.us-ashburn-1.oraclecloud.com

.

Let’s download OPatch

In Part 1 and Part 2 of this blog post series you downloaded the newest AutoUpgrade tool, and you put your MOS credentials into the SEPS keystore securely. AutoUpgrade can now connect to MOS/ARU and to the Oracle Update Advisor. This is the requirement to be able to continue. See also the list of URLs for the different purposes, and the proxy section above.

We start with a very simple config file I used in Part 2: AutoUpgrade Patching – MOS Credentials already. But here, I would like to fetch the most recent OPatch instead of AutoUpgrade. I need to add the platform parameter option in this case.

patch1.platform=LINUX.X64

This is the list of platforms we support:

• AIX.x64 IBM AIX on POWER Systems (64-Bit)
• ARM.x64 LINUX ARM (aarch64)
• LINUX.X64 Linux x86-64
• SPARC.x64 Oracle Solaris on SPARC (64-Bit)
• SOLARIS.x64 Oracle Solaris on x86-64 (64-Bit)
• WINDOWS.X64 Microsoft Windows x64 (64-bit)

# get_patches.cfg
#

global.global_log_dir=/Users/mdietric/TEMP/AU/logs
global.keystore=/Users/mdietric/TEMP/AU/keystore
global.folder=/Users/mdietric/TEMP/AU/patches

patch1.platform=LINUX.X64
patch1.target_version=19
patch1.patch=OPATCH

Let us kick off AutoUpgrade and download OPATCH for Oracle 19c on Linux:

java -jar autoupgrade.jar -patch -config get_patches.cfg -mode download 


AutoUpgrade Patching 26.4.260701 launched with default internal options
Processing config file ...
Loading AutoUpgrade Patching keystore
AutoUpgrade Patching keystore is loaded

Connected to MOS - Searching for specified patches

----------------------------------------------------
Downloading files to /Users/mdietric/TEMP/AU/patches
----------------------------------------------------
OPatch 12.2.0.1.51 for DB 19.0.0.0.0 (Apr 2026)
    File: p6880880_190000_Linux-x86-64.zip - VALIDATED
----------------------------------------------------

This is simple, isnt’t it.

You want OPatch for more releases and operating systems?

Then let us extend the config file a bit. I add now 3 additional sections, each using a different prefix: patch1, patch2, patch3 and patch4.

# get_patches.cfg
#

global.global_log_dir=/Users/mdietric/TEMP/AU/logs
global.keystore=/Users/mdietric/TEMP/AU/keystore
global.folder=/Users/mdietric/TEMP/AU/patches

patch1.platform=LINUX.X64
patch1.target_version=19
patch1.patch=OPATCH

patch2.platform=LINUX.X64
patch2.target_version=26
patch2.patch=OPATCH

patch3.platform=ARM.x64
patch3.target_version=19
patch3.patch=OPATCH

patch4.platform=SPARC.x64
patch4.target_version=19
patch4.patch=OPATCH

See what happens, the download starts almost instantly.

java -jar autoupgrade.jar -patch -config get_patches.cfg -mode download 


AutoUpgrade Patching 26.4.260701 launched with default internal options
Processing config file ...
Loading AutoUpgrade Patching keystore
AutoUpgrade Patching keystore is loaded

Connected to MOS - Searching for specified patches

----------------------------------------------------
Downloading files to /Users/mdietric/TEMP/AU/patches
----------------------------------------------------
OPatch 12.2.0.1.51 for DB 19.0.0.0.0 (Apr 2026)
    File: p6880880_190000_Linux-ARM-64.zip - VALIDATED
----------------------------------------------------


----------------------------------------------------
Downloading files to /Users/mdietric/TEMP/AU/patches
----------------------------------------------------
OPatch 12.2.0.1.51 for DB 23.0.0.0.0 (Apr 2026)
    File: p6880880_230000_Linux-x86-64.zip - VALIDATED
----------------------------------------------------


Connected to MOS - Searching for specified patches

----------------------------------------------------
Downloading files to /Users/mdietric/TEMP/AU/patches
----------------------------------------------------
OPatch 12.2.0.1.51 for DB 19.0.0.0.0 (Apr 2026)
    File: p6880880_190000_Linux-x86-64.zip - LOCATED
----------------------------------------------------


Connected to MOS - Searching for specified patches

----------------------------------------------------
Downloading files to /Users/mdietric/TEMP/AU/patches
----------------------------------------------------
OPatch 12.2.0.1.51 for DB 19.0.0.0.0 (Apr 2026)
    File: p6880880_190000_SOLARIS64.zip - VALIDATED
----------------------------------------------------

You may recognize that the 19c OPatch release on Linux has been downloaded before – and since we are using the same folder, AutoUpgrade recognizes it and doesn’t download it again. This is when it says LOCATED in the above output.

We wanted to download patches, right?

The blog post is titled “Download patches“, and we would like to do this now. I am going to download patch=RECOMMENDED patches but I will explain the various options in the next blog post. RECOMMENDED includes the most important fixes – and now also the CSPU (if it is available) or the MRP.

global.global_log_dir=/Users/mdietric/TEMP/AU/logs
global.keystore=/Users/mdietric/TEMP/AU/keystore
global.folder=/Users/mdietric/TEMP/AU/patches

patch1.platform=LINUX.X64
patch1.target_version=19
patch1.patch=RECOMMENDED,JDK

patch2.platform=LINUX.X64
patch2.target_version=26
patch2.patch=RECOMMENDED,JDK

patch3.platform=ARM.x64
patch3.target_version=19
patch3.patch=RECOMMENDED,JDK

Now you recognize an interesting pattern.

AutoUpgrade will download a Gold Image where applicable from the Oracle Update Advisor. Currently, OUA only provides the Linux x86-64 images but not the image for ARM, AIX, SPARC or Windows. See below how distinctive AutoUpgrade picks the right sources where possible:

java -jar autoupgrade.jar -patch -config get_patches.cfg -mode download 

AutoUpgrade Patching 26.4.260701 launched with default internal options
Processing config file ...
Loading AutoUpgrade Patching keystore
AutoUpgrade Patching keystore is loaded

Connected to Oracle Update Advisor service - Requesting gold images  
AutoUpgrade Patching has finished processing the gold image requests

Connected to MOS - Searching for specified patches

CSPU is ignored because Oracle has not created it for 19.31 RU version for the job with prefix patch3

----------------------------------------------------
Downloading files to /Users/mdietric/TEMP/AU/patches
----------------------------------------------------
DATABASE RELEASE UPDATE 19.31.0.0.0 (REL-APR2026)
    File: p39034528_190000_Linux-ARM-64.zip - VALIDATED

OPatch 12.2.0.1.51 for DB 19.0.0.0.0 (Apr 2026)
    File: p6880880_190000_Linux-ARM-64.zip - LOCATED

DATAPUMP BUNDLE PATCH 19.31.0.0.0
    File: p39196236_1931000DBRU_Generic.zip - VALIDATED

OJVM RELEASE UPDATE 19.31.0.0.0
    File: p38906621_190000_Linux-ARM-64.zip - VALIDATED

JDK BUNDLE PATCH 19.0.0.0.260421
    File: p38930593_190000_Linux-ARM-64.zip - VALIDATED

autoupgrade.jar 26.4 (July 2026)
    File: autoupgrade.jar - LOCATED
----------------------------------------------------


Connected to MOS - Searching for specified patches

Skipping standalone JDK patch for RU 23.26.2 for the job with prefix patch2 because JDK patches are included in the RU.

----------------------------------------------------
Downloading files to /Users/mdietric/TEMP/AU/patches
----------------------------------------------------
DATABASE RELEASE UPDATE 23.26.2.0.0
    File: p39099680_230000_Linux-x86-64.zip - VALIDATED

OPatch 12.2.0.1.51 for DB 23.0.0.0.0 (Apr 2026)
    File: p6880880_230000_Linux-x86-64.zip - LOCATED

DATAPUMP BUNDLE PATCH 23.26.2.0.0
    File: p39227161_2326200DBRU_Generic.zip - VALIDATED

DATABASE MRP 23.26.2.0.0 MAY 2026
    File: p39345754_2326200DBRU_Linux-x86-64.zip - VALIDATED

autoupgrade.jar 26.4 (July 2026)
    File: autoupgrade.jar - LOCATED
----------------------------------------------------


Connected to MOS - Searching for specified patches

----------------------------------------------------
Downloading files to /Users/mdietric/TEMP/AU/patches
----------------------------------------------------
OPatch 12.2.0.1.51 for DB 19.0.0.0.0 (Apr 2026)
    File: p6880880_190000_Linux-x86-64.zip - LOCATED

DATAPUMP BUNDLE PATCH 19.31.0.0.0
    File: p39196236_1931000DBRU_Generic.zip - LOCATED

OJVM RELEASE UPDATE 19.31.0.0.0
    File: p38906621_190000_Linux-x86-64.zip - VALIDATED

JDK BUNDLE PATCH 19.0.0.0.260421
    File: p38930593_190000_Linux-x86-64.zip - VALIDATED

Gold Image - 19.31.0.0.0
    File: autoupgrade_linux-x86-64_19.31.0.0.0_db_home.zip - VALIDATED

autoupgrade.jar 26.4 (July 2026)
    File: autoupgrade.jar - LOCATED
----------------------------------------------------

Let me explain a few things regarding the above output, section by section.

1. AutoUpgrade works from patch3 to patch2 to patch1 sections
   .
2. In section patch3 for ARM Linux:
   1. First message is that there is no CSPU for Oracle 19.31 on ARM yet
   2. Since there is no gold image for ARM on OUA, AutoUpgrade downloads the RU 19.31 from MOS/ARU instead. But you need to add the base release in this case to the patching folder
   3. autoupgrade.jar has been downloaded before as has been OPatch – therefore, you can see the LOCATED tag
   4. All downloads will be VALIDATED against the checksum file to ensure integrity
      .
3. In section patch2 for 26ai Linux
   1. It skips the JDK since 26ai has the most recent JDK always included by default
   2. Even though it is named RU 23.26.2, this is the Gold Image already. Hence, no need to download a base release.
   3. AutoUpgrade fetches the most recent MRP as well – you should install it
      .
4. In section patch1 for 19c for Linux
   1. OPatch, Data Pump Bundle Patch and AutoUpgrade are already LOCATED
   2. AutoUpgrade downloads the 19.31 Gold Image right away – no need to download the base release anymore
      .

This is just a first outlook into what’s possible. We put a lot of “logic” into the new 26.4 version of AutoUpgrade to fetch the right patches for you in the fastest possible way.

Try it out.

Further Links and Information

AutoUpgrade Patching Blog Post Series

• Part 1: AutoUpgrade Patching – Download and Version Check
• Part 2: AutoUpgrade Patching – MOS Credentials
• Part 3: AutoUpgrade Patching – Download Patches
• Part 4: AutoUpgrade Patching – Download Examples

Additional Links

• AutoUpgrade Download from oracle.com
• Static link to fetch AutoUpgrade
• MOS Note: KB123450 AutoUpgrade

Virtual Classroom Seminars

• Episode 21: One-Button Patching with AutoUpgrade – Easing every DBA’s life
• Episode 27: Patch Smarter, not Harder – Oracle Database Patching with AutoUpgrade
• Episode 28: Patch Smarter, not Harder – Microsoft Windows Special Patching Edition

To be continued …

–Mike