AutoUpgrade Patching – From Zero to Hero – Part 4: Download Examples

Posted on July 9, 2026 by AutoUpgrade Oracle AI Database 26ai Oracle Database 19c Patch Recommendation 7

Let me take off into the 4th part of this blog post series: AutoUpgrade Patching – From Zero to Hero – Part 4: Download Examples. I’d like to show you some of the most common examples and use cases we came across. And of course, I will add some additional (and hopefully useful) information on top.

AutoUpgrade Patching – From Zero to Hero – Part 4: Download Examples

The patch parameter

At first, in my previous blog post I used patch1.patch=RECOMMENDED (by the way, upper/lowercase does not matter). But I didn’t explain the whole extent and possibilities of the patch parameter to you.

Here’s a list of the most important parameter options. You will find the full list here.

  • RU – the most recent Release Update
  • OPATCH – the most recent OPatch
  • OJVM – for 19c only, the most recent OJVM Bundle
  • DPBP – the most recent Data Pump Bundle Patch matching the RU
  • AU – the newest available AutoUpgrade
  • MRP – the most recent available MRP for Oracle 19c and 26ai on Linux on top of the selected RU
    or
    CSPU – the most recent available CSPU for Oracle 21 on Linux or all other platforms on top of the selected RU

All of the above are included and covered under:

  • RECOMMENDED

when applicable. For instance, OJVM is not available as a separate bundle from Oracle 21c onward, and therefore won’t be downloaded. A message in the output will tell you. You could add a version number, and for gold images this may still work in some cases. But since the older RUs had been password protected (read more here) this often is not an option anymore. You can try:

patch1.patch=RU:19.30,OPATCH,DPBP

And you may see that – as long as you don’t turn off gold_image, it will fetch 19.30 since the OUA has always the current and the two previous gold images in-stock.

 

What else can patch download?

As you can see, there are a lot more options:

  • OCW – Oracle Clusterware home – it is installed in your 19c database home as well, and may be still in version 19.3.0
  • JDK – highly recommended for 19c – skipped in 26ai since 26ai gets shipped with an updated JDK already
  • patch-no1,patch-no2,.. – single patch numbers, merges, one-offs etc – be aware that AutoUpgrade does not do any conflict check during download
  • TEXT – the Oracle Text Bundle
  • SDOBP – Spatial Data Bundle Patch

Then you can fetch tools such as:

  • AHF – Automatic Health Framework
  • CVU – CluVy – Clusterware Verification Utility
  • SQLCL – SQLcl, our preferred replacement for SQL*Plus
  • AU – AutoUpgrade (which I did list above already)

or you use the shorcut:

  • TOOLS – which fetches AutoUpgrade, Cluvy, SQLcl and AHF

In the following section I am going to share a few examples with you. This way, it may be easier to start with.

 

Download 19c patches for Linux

This may be the most simple and straight forward example many may use.

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

This fetches:

java -jar autoupgrade.jar -patch -config gp.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

----------------------------------------------------
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

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-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 - VALIDATED
----------------------------------------------------

What is remarkable: We take the Gold Image for 19c since it is pre-built and in-stock already. Hence, we are fetching it from the OUA (Oracle Update Advisor) service. Since it is available, you will get with it:

  • Base release 19.3.0
  • Release Update 19.31
  • MRP2 for 19.31

with one single download:

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

In addition, we pull AU, OJVM, Data Pump Bundle Patch, OPatch and the newest AutoUpgrade.

 

You don’t like Gold Images?

It is true, we’ve had customers asking for access to the RU instead of the Gold Image. There may be various reasons, and I don’t want to dispute any of them. It is your choice, we just want to make your life easier. But at the end, you decide.

Then let us add the parameter patch1.gold_image=NO, and see what happens.

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
patch1.gold_image=NO

Now we are downloading the individual bundles, and you must add the base release by yourself if you want to install from this folder. This is what you’ll get:

java -jar autoupgrade.jar -patch -config gp.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
----------------------------------------------------
DATABASE RELEASE UPDATE 19.31.0.0.0 (REL-APR2026)
    File: p39034528_190000_Linux-x86-64.zip - VALIDATED

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 - LOCATED

DATABASE MRP 19.31.0.0.260616
    File: p39487048_1931000DBRU_Linux-x86-64.zip - VALIDATED

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

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

So, instead of the Gold Image we downloaded in the session before, we get now the RU 19.31 as plain Release Update without the base release. And we get the June 2026 MRP on top of the RU 19.31. Both were baked into the same gold image before together with the base release. Everything else has been downloaded before, and AutoUpgrade marks it as LOCATED.

You see, everything is possible – you have the choice.

 

You are a patching fan-boy/girl?

You truly love patching. Your Oracle Home must contain everything available, you want to be on the safe side? Then let’s fetch everything together and see what happens.

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

patch3.platform=LINUX.X64
patch3.target_version=19
patch3.patch=RECOMMENDED,JDK,TOOLS,SDOBP,TEXT,OCW,29213893,34774667,38723830
patch3.gold_image=AUTO

I have now added a long list of fixes, plus two individual one-offs which are not RAC rolling applicable from KB188772 – Oracle Database 19c and Oracle AI Database 26ai Important Recommended One-off Patches. Let’s see what I will get here:

java -jar autoupgrade.jar -patch -config gp.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

----------------------------------------------------
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

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-x86-64.zip - VALIDATED

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

Standalone CVU (OL8+, RHEL8+) January 2026
    File: cvupack_linux_ol8_x86_64.zip - VALIDATED

PLACEHOLDER - DOWNLOAD LATEST AHF (TFA and ORACHK/EXACHK)
    File: AHF-LINUX_v26.5.0.zip - VALIDATED

SPATIAL BUNDLE PATCH #3 ON DBRU 19.31.0.0.0
    File: p39661994_1931000DBRU_Linux-x86-64.zip - VALIDATED

MERGE OF 19.31 ORACLE TEXT RAC + NON-RAC MLRS
    File: p39193352_1931000DBRU_Linux-x86-64.zip - VALIDATED

DBMS_STATS FAILING WITH ERROR ORA-01422 WHEN GATHERING STATS FOR USER$ TABLE
    File: p29213893_1931000DBRU_Generic.zip - VALIDATED

ORA-7445 IN PURGE QUEUE TABLE
    File: p34774667_1931000DBRU_Linux-x86-64.zip - VALIDATED

OCI: ORA-7445 [__INTEL_SSE2_STRNCMP()+379] OCCURS IN RS0I PROCESS AND INSTANCE TERMINATED.
    File: p38723830_1931000DBRU_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 - VALIDATED

sqlcl-latest.zip 26.2.0.181.2110 (June 2026)
    File: sqlcl-latest.zip - VALIDATED
----------------------------------------------------

That’s a lot of fixes and tools – but the whole download took 10 minutes, and I did not check a single MOS note. If you wonder why OCW is not listed: It is included into the Gold Image as is the MRP.

 

Let’s fetch Oracle AI Database 26ai

So far, I pulled 19c only. For a change, let us get 26ai now. Keep in mind that this is working for Oracle Database 19c, Oracle Database 21c and Oracle AI Database 26ai but not for older releases.

Currently, there are no single one-off patches listed in KB188772  on top of 23.26.2. Therefore, I didn’t include any single patches.

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=26
patch1.patch=RECOMMENDED,JDK,OCW
patch1.gold_image=AUTO

This is what we get:

java -jar autoupgrade.jar -patch -config gp.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

Skipping standalone JDK patch for RU 23.26.2 for the job with prefix patch1 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 - VALIDATED

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 - VALIDATED
----------------------------------------------------

What is misleading is the fact that we call the Gold Image here:

DATABASE RELEASE UPDATE 23.26.2.0.0 File: p39099680_230000_Linux-x86-64.zip - VALIDATED

But it is actually the pre-built Gold Image available in-stock.

I removed TEXT and SDOBP as well since it does not exist for 23.26.2 yet. If you’d include it, we would throw an error since you requested it, and we don’t have it yet available. Therefore, it may be a general good practice to use RECOMMENDED and add additional software in a second section such as:

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=26
patch1.patch=RECOMMENDED
patch1.gold_image=AUTO

patch2.platform=LINUX.X64
patch2.target_version=26
patch2.patch=JDK,OCW,TOOLS
patch2.gold_image=AUTO

Kicking it off:

java -jar autoupgrade.jar -patch -config gp.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

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
----------------------------------------------------
OPatch 12.2.0.1.51 for DB 23.0.0.0.0 (Apr 2026)
    File: p6880880_230000_Linux-x86-64.zip - LOCATED

Standalone CVU (OL8+, RHEL8+) January 2026
    File: cvupack_linux_ol8_x86_64.zip - VALIDATED

PLACEHOLDER - DOWNLOAD LATEST AHF (TFA and ORACHK/EXACHK)
    File: AHF-LINUX_v26.5.0.zip - VALIDATED

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

sqlcl-latest.zip 26.2.0.181.2110 (June 2026)
    File: sqlcl-latest.zip - VALIDATED
----------------------------------------------------


Connected to MOS - Searching for specified patches

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

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 - LOCATED

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

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

You see now two download sections, patch2 at first, then patch 1.

 

Download the Combo Patches

From several customers I know that some of you prefer the Combo patches for various reasons. Maria asked me about it as did Matjaz recently. Hence, let me share a parameter file with you. In this case, we can’t use an acronym but instead you need to find out the patch number of the Combo patch, e.g. 39062956. This is the reason why I am not a great fan of this option – it leaves me again with wasting time going through MOS notes and finding the patches manually, then updating my config file.

But if you wish to download the Combo Patches, simply use:

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=39062956
patch1.gold_image=NO

You see, I am using the raw patch number instead of one of the predefined acronyms. And of course, this works nicely, too.

java -jar autoupgrade.jar -patch -config gp.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
----------------------------------------------------
COMBO OF OJVM COMPONENT 19.31.0.0.260421 + GI RU 19.31.0.0.260421
    File: p39062956_190000_Linux-x86-64.zip - VALIDATED
----------------------------------------------------

Works!

 

Further Links and Information

AutoUpgrade Patching Blog Post Series
Additional Links
Virtual Classroom Seminars

To be continued …

–Mike

Tags:

You may also like...

7 Responses

  1. Laszlo says:
    July 9, 2026 at 13:48

    Hi, nice, thank you!
    Very useful tool just like ‘opatch util DeleteInactivePatches’ !
    May there other options for other products as well, like FMW?
    Regards, Laszlo

    Reply
  2. Bob Bryla says:
    July 9, 2026 at 16:53

    Thanks, it’s still not clear after more searching and looking through the official documentation — if I want both the DB and GI RU, is that two separate patches? One for grid home, one for database home? For 19c, not sure for 26ai, the GI RU was everything and also contained the RU patches only for the database home. In other words, from the GI RU I would install all 5 patches, and then only two of them would be used to patch the DB home.

    Reply
    • Mike.Dietrich says:
      July 9, 2026 at 21:08

      Hi Bob,

      at first, when AutoUpgrade detects a RAC Database home, it would apply the OCW to it as well. When you check “opatch lspatches” in 19c, you will see that OCW is 19.3.0. Not an issue usually as long as your DB home is not used in a RAC environment. But I know some security scanners which mark this as well.

      Then, for the pure download, we prefer to download the Gold Image from OUA – which is prebuilt and in stock. And this one contains OCW by default. Therefore, you don’t have to make choices.
      But you can download OCW separately as well if you want to.

      Cheers,
      Mike

      Reply
  3. Michele says:
    July 9, 2026 at 23:24

    Thank you so much Mike! Tried it and love it, and am going to use it for JUL 2026! I do wish the .json file included a bit more information (size in bytes/last updated) for the downloaded patches…

    Reply
  4. Nikolay Serbezov says:
    July 10, 2026 at 06:49

    Hi Mike,

    One question about the gold image of version 19.
    I already tried 3 or 4 times to download it, every time an error occurred before download finish. What can be the reason? It is not so bigger than other patches, for example RU, which are downloaded with no problem and with normal speed.

    Thanks,
    Nikolay

    Reply
    • Mike.Dietrich says:
      July 26, 2026 at 07:39

      Hi Nikolay,

      I really can’t tell – maybe just a very bad day?
      It is really hard to say from my end.

      For me, it usually finishes fast and nicely.

      Cheers,
      Mike

      Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Mike Dietrich
Oracle Vice President of Product Management and Development for Database Upgrade, Cloud Migrations and Patching writing just another blog.

Opinions certainly are my own as is this page.

Archives

Categories

Upgrade @YouTube

Subscribe via Email

Join 11.1K other subscribers