AutoUpgrade New Features: Download the Newest AutoUpgrade.jar

Patching 1 Minute

I’ve told you a million times:

Always get the latest version of AutoUpgrade!

A while ago, AutoUpgrade even became available for direct download from Oracle.com. But it must be even easier.

Now, AutoUpgrade downloads the latest version of itself when you use the keywords RECOMMENDED or AU. Here’s an example:

global.global_log_dir=/home/oracle/autoupgrade-patching/log
global.keystore=/home/oracle/autoupgrade-patching/keystore
global.folder=/home/oracle/autoupgrade/patches
patch1.target_version=19
patch1.patch=RECOMMENDED

I start AutoUpgrade:

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

Conveniently, AutoUpgrade grabs the latest version after downloading the patches:

Connected to MOS - Searching for specified patches

-----------------------------------------------------
Downloading files to /home/oracle/autoupgrade/patches
-----------------------------------------------------
DATABASE RELEASE UPDATE 19.30.0.0.0(REL-JAN260130)
    File: p38632161_190000_Linux-x86-64.zip - LOCATED

...

autoupgrade.jar 26.2 (February 2026)
    File: autoupgrade.jar - LOCATED
-----------------------------------------------------

Simple and easy!

Other Tools

Besides AutoUpgrade, there are other important tools for Oracle AI Database.

Here’s a little sneak peek at what the next version of AutoUpgrade brings. Using this config file:

global.global_log_dir=/home/oracle/autoupgrade-patching/log
global.keystore=/home/oracle/autoupgrade-patching/keystore
global.folder=/home/oracle/autoupgrade/patches

patch1.target_version=19
patch1.patch=AHF,CVU,SQLCL

You’ll get the latest versions of:

  • Autonomous Health Framework
  • Cluster Verification Utility
  • SQLcl

Leave a comment if you think there are other tools that AutoUpgrade should get for you.

Published

9 thoughts on “AutoUpgrade New Features: Download the Newest AutoUpgrade.jar”

  1. It is still somewhat cumbersome. If I have EE + Oracle Restart on 64‑bit Linux, the best option seems to be to specify patch1.patch=RECOMMENDED,JDK,OCW,TEXT where according to the documentation: “RECOMMENDED: Alias for all of the following options: RU, OPATCH, OJVM, DPBP.”
    So JDK, OCW, and TEXT apparently are no longer considered recommended???!!! … We do not use Oracle Spatial.
    At the same time, OCW, JDK, and TEXT are not part of the official documentation (see the link below). I found these “hidden” options only on blogs by Daniel Overby Hansen and Mike Dietrich :-) !!! https://docs.oracle.com/en/database/oracle/oracle-database/26/upgrd/autoupgrade-patching.html#GUID-B4169A36-FA3F-430E-B5FE-E72082D0B6AD

    Like

    Reply

    1. Hi Michal,

      The “recommended” patches changes based on your configuration, so it’s not possible to have one keyword that covers all possible scenarios. Thus, “RECOMMENDED” is basis recommendation and in most cases you’d add more patch. You could argue that having a “RECOMMENDED” keyword is misleading – and perhaps “BASIS” would’ve been a better term.
      You can find all the “patch” keywords here:
      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

      Like

      Reply

      1. OK, I have added feedback to the Oracle documentation, so that the documentation is not duplicated (once incomplete and out-of-date in Table 4-1), and it is not linked to the current (common) parameter values.

        Like

        Reply

  3. getting MFA error but I think is not related to update of autoupgrade tool:

    java -jar autoupgrade.jar -config get19.30.cfg -patch -mode download

    AutoUpgrade Patching 26.3.260401 launched with default internal options

    Processing config file …

    Loading AutoUpgrade Patching keystore AutoUpgrade Patching keystore is loaded

    There were conditions found preventing AutoUpgrade Patching from successfully running *Downloading files

    Download query failed *

    Connection Failed – Tenant is MFA enabled. Use Multi-Factor Authentication for all users in this tenant.*

    Like

    Reply

  4. how to get the gi patch or the bug id? example 39062956 (COMBO OF OJVM RUCOMPONENT 19.31.0.0.260421+KB869205GI RU19.31.0.0.260421) or 38854064 for 19.29 linux-x64?

    thanks!

    Like

    Reply

    1. Hi,
      19.29 was revoked and is now password-protected. This means it can’t be downloaded by AutoUpgrade. You’d need to download it manually and place it in the “patch” folder and then AutoUpgrade can apply it.

      What patch are you looking specifically? 19.31 has been a little delayed and the one you specifically mentions 38854064 is scheduled for delivery on MAY 15.

      Regards,
      Daniel

      Like

      Reply

Leave a comment