The Easiest Way to Download 19.27 Release Update

Patching 3 Minutes

Oracle just released new Release Updates, so it’s time to patch your Oracle Database again. As much as I love patching, the part about finding and downloading patches is not that much fun.

Luckily, I can use AutoUpgrade to download the Release Update and other patches with just a few commands.

How to Download Release Updates

I can do the following on any computer. I just need Java 8 or 11 to run AutoUpgrade.

  1. I download the latest version of AutoUpgrade:

    wget https://download.oracle.com/otn-pub/otn_software/autoupgrade.jar

  2. I create an AutoUpgrade config file called get-patches:

    global.global_log_dir=/home/oracle/autoupgrade/logs
global.keystore=/home/oracle/autoupgrade/keystore
global.folder=/home/oracle/autoupgrade/patches

patch1.platform=LINUX.X64
patch1.patch=RU:19.27,OPATCH,OJVM
    • I want to download 19.27 Release Update and supporting patches for Linux and I specify that using the platform parameter.

  3. I’ve already used AutoUpgrade to download patches, so my My Oracle Support credentials are already stored in the AutoUpgrade keystore. If you’ve never used AutoUpgrade to download patches, follow the instructions below (see Creating an AutoUpgrade Keystore).

  4. I download the patches by starting AutoUpgrade in download mode:

    java -jar autoupgrade.jar -config get-patches -patch -mode download

  5. That’s it! I’ve download all the new Release Updates – plus OPatch and the matching OJVM bundle patch.

    • DATABASE RELEASE UPDATE 19.27.0.0.0 – p37642901_190000_Linux-x86-64.zip
    • OJVM RELEASE UPDATE 19.27.0.0.0 – p37499406_190000_Linux-x86-64.zip
    • OPatch 12.2.0.1.46 for DB 19.0.0.0.0 (Apr 2025) – p6880880_190000_Linux-x86-64.zip

Is it really that easy? Yes, it is…

Happy patching!

What About the Other Platforms

At the time of writing, Oracle has only released the Linux patches. Once the other platforms are available, you can easily download them as well. Check the Patch Availability Document for details. Add the following to your config file:

patch2.platform=ARM.x64
patch2.patch=RU:19.27,OPATCH,OJVM

patch3.platform=AIX.x64
patch3.patch=RU:19.27,OPATCH,OJVM

patch4.platform=SPARC.x64
patch4.patch=RU:19.27,OPATCH,OJVM

patch5.platform=SOLARIS.x64
patch5.patch=RU:19.27,OPATCH,OJVM

patch6.platform=WINDOWS.X64
patch6.patch=RU:19.27,OPATCH,OJVM

Creating an AutoUpgrade Keystore

The first time I use AutoUpgrade to download patches, I must store my MOS credentials in the AutoUpgrade keystore.

  1. I create my config file. It must include global.keystore to specify the location of the AutoUpgrade keystore.

  2. I start the password console:

    java -jar autoupgrade.jar -config get-patches -patch -load_password

  3. AutoUpgrade prompts for a password to protect its keystore. AutoUpgrade uses the password to encrypt the keystore, which stores my My Oracle Support credentials.

    • This is not the database keystore password that you use for TDE Tablespace Encryption.
    Processing config file ...

Starting AutoUpgrade Patching Password Loader - Type help for available options
Creating new AutoUpgrade Patching keystore - Password required
Enter password:
Enter password again:

  4. I specify my MOS username. AutoUpgrade then prompts me for the MOS password:

    MOS> add -user <mos-username-or-email>
Enter your secret/Password:
Re-enter your secret/Password:

  5. I save the changes, and I choose to create an auto-login keystore so I don’t have to enter the AutoUpgrade keystore password every time AutoUpgrade starts:

    MOS> save
Convert the AutoUpgrade Patching keystore to auto-login [YES|NO] ? YES

  6. I exit, and that’s it:

    MOS> exit

AutoUpgrade Patching Password Loader finished - Exiting AutoUpgrade Patching

Here’s a video explaining the use of the AutoUpgrade keystore:

Pro Tips

  • After downloading the patches, I still need to patch my databases. I can do that using AutoUpgrade as well.

  • Once MRPs (888.1) or critical fixes (555.1) become available for the Release Update, I can get those as well. Or, if I need specific one-off patches:

    patch1.patch=RU:19.27,OPATCH,OJVM,MRP,12345678,23456789,34567890

  • If the Data Pump bundle patch is also available, I can also get that:

    patch1.patch=RU:19.27,OPATCH,OJVM,DPBP,MRP,12345678,23456789,34567890
    • Notice the DPBP keyword, that toggles the download of the Data Pump bundle patch.

What About Grid Infrastructure

  • Although AutoUpgrade can’t patch Grid Infrastructure, it can still get the GI bundle patch:

    patch1.patch=RU:19.27,OCW

Be sure to patch Grid Infrastructure out-of-place and I’d recommend using the SwitchGridHome method.

Further Reading

Published

14 thoughts on “The Easiest Way to Download 19.27 Release Update”

  1. Hi Daniel,

    Downloading the 19.27 Release Update with the parameter patch1.patch=RECOMMENDED or patch1.patch=RU:19.27,OPATCH,OJVM:19.27,DPBP
    does not work because no DPBP is present for 19.27 to download.

    The autoupgrade tool cannot handle this and fails with the following message or notice:

    AutoUpgrade Patching 25.1.250212 launched with default internal options
    Processing config file …
    Loading AutoUpgrade Patching keystore
    AutoUpgrade Patching keystore was successfully loaded

    Connected to MOS – Searching for specified patches

    There were conditions found preventing AutoUpgrade Patching from successfully running

    *Downloading Oracle Patch files
    Query for the DPBP patch resulted in none being found

    Only “patch1.patch=RU:19.27,OPATCH,OJVM” works perfectly as you have already shown.

    This means that the value “RECOMMENDED” cannot be used if DPBP is not available!

    Regards

    Adel

    Like

    Reply

    1. Hi Adel,

      That’s correct! When you specify patches using the “patch” parameter, all those patches must be available either on disk or to download. Otherwise, you must edit the config file and remove the patches that doesn’t exist yet. The Data Pump bundle patch should come within days.
      Regards,
      Daniel

      Like

      Reply

      1. Hi Daniel,

        Thank you for the reply.

        It’s good news that the Data Pump bundle patch will be available soon.

        I generate the download scripts for different environments and would like to avoid this manual adjustment.

        It looks like I started too early!

        Best Regards

        Adel

        Like

        Reply

    1. I believe it has extended support until 2032 or so (although I’m not a Java expert).

      You can also use Java 8 which is what we bundle in the Oracle home (I believe). AutoUpgrade is compiled to work with the Java that’s shipped with the Oracle homes for backward compatibility.

      As much as it would be great with a newer version (using new Java features), we don’t leave anyone behind. :)

      Daniel

      Like

      Reply

  3. Hi Daniel

    Can Autoupgrade download the base release yet – i.e 19.3? If not, is that planned or is it thought to be a rare enough requirement (i.e once you have it you use it for the lifecycle of that version) that it wont be added as a feature?

    ThanksNick.

    Like

    Reply

    1. Hi,

      No, AutoUpgrade does not download the base image for 19c yet. We’re still working on a process for that. When we support patching on 23ai, this will change because on this release Oracle ships fully updated gold images, not individual Release Updates.

      Regards,
      Daniel

      Like

      Reply

  4. Hi Daniel,

    When trying to download patches (for 19.28 RU in my case) the following error occurs:

    *Downloading Oracle Patch files
    Patch query failed
    *SSL peer shut down incorrectly*

    The same error appears when listing credentials in the keystroke:

    MOS> list
    MOS Credentials Loaded – Connection Failure
    *SSL peer shut down incorrectly*

    What could be the root cause? May it somehow be related to Oracle Support 2FA?

    Like

    Reply

    1. Hi Alex,

      I’ve not seen this error before and I don’t think it is related to the 2FA requirement when you log on to My Oracle Support.

      I assume that you are doing this from a corporate network. Please ensure that your server can communicate to the below servers via SSL. Perhaps a firewall sits in between and causes problems:
      https://updates.oracle.com
      https://login-ext.identity.oraclecloud.com
      https://aru-akam.oracle.com
      If you have any firewall rules allowing these connections, be sure to make them work on the DNS name and not the IP addresses as they will change constantly.

      Alternatively, can you try from a computer that is not part of the same network or less tight network security?

      Do you have an open SR for the problem, if so, please share it with me on daniel.overby.hansen (a) oracle.com. Be sure to include the log files (https://dohdatabase.com/auzip).

      Regards,
      Daniel

      Like

      Reply

  5. It is not working for me. It asked me to convert to autologin, but later always asks again for the wallet password, and after updating my username and password several times, it always says:

    There were conditions found preventing AutoUpgrade Patching from successfully running

    *Downloading Oracle Patch files
    Patch query failed
    *Connection Failed – You entered an incorrect user name or password.*

    Like

    Reply

  6. Hi Daniel,

    I just successfully installed new oracle home using autoupgrade :

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

    download.cfg ( parts are removed) :

    patch1.source_home=…/db_1925

    patch1.target_home=…/db_1927

    patch1.folder=…/auto/patch

    patch1.patch=RU:19.27,OPATCH,OJVM,MRP

    Is there a way for autoupgrade to install and patch new Oracle home together with examples ?

    Our current 19.25 ORACLE HOME was installed manually and examples were added as described in manual – https://docs.oracle.com/en/database/oracle/oracle-database/19/exmpl/index.html

    You install base release 19.3, then into it examples and after that RU , OJVM and so on.

    19.25 OH opatch lsinventory ( parts are removed ) :

    …

    Local Machine Information::
    Hostname: REMOVED
    ARU platform id: 226
    ARU platform description:: Linux x86-64

    Installed Top-level Products (2):

    Oracle Database 19c 19.0.0.0.0
    Oracle Database 19c Examples 19.0.0.0.0
    There are 2 products installed in this Oracle Home.

    …

    19.27 OH created with autoupgrade contains only 1 product:

    Installed Top-level Products (1):

    Oracle Database 19c 19.0.0.0.0
    There are 1 products installed in this Oracle Home.

    …

    It is not critical – I’m just comparing autoupgrade method with our own.

    kind regards

    Januš

    Like

    Reply

      1. Hi Daniel,

        I managed to do that with another parameter :

        patch1.before_action.create_home=…./replace_base_image.sh

        The script replaces base image downloaded from MOS with it’s customized version containing also examples .

        The original version of base image must be in patch folder at the beginning, otherwise autupgrade.jar recognizes it’s not there and stops.

        with kind regards

        Januš

        Like

        Reply

Leave a reply to adel8560 Cancel reply

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