Once you try downloading patches using AutoUpgrade, you’ll never do it from My Oracle Support again.
But what if you want to download:
Do you really have to do that from My Oracle Support? Of course – AutoUpgrade has you covered!
Download Tools
-
I’ve already configured AutoUpgrade to download patches.
-
I create a config file:
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.target_version=19 patch1.patch=SQLCL,AHF,CVU- Notice the
patchspecification. It contains the three new keywords that instruct AutoUpgrade to download the tools.
- Notice the
-
I start AutoUpgrade in download mode:
AutoUpgrade Patching 26.3.260401 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 /home/oracle/autoupgrade/patches ----------------------------------------------------- PLACEHOLDER - DOWNLOAD LATEST AHF (TFA and ORACHK/EXACHK) File: AHF-LINUX_v26.3.1.zip - LOCATED Standalone CVU (OL8+, RHEL8+) January 2026 File: cvupack_linux_ol8_x86_64.zip - LOCATED sqlcl-latest.zip 26.1.2.132.1334 (May 2026) File: sqlcl-latest.zip - LOCATED ------------------------------------------------------
-
AutoUpgrade places the latest version of the tools in the download folder.
-
Nice and simple.
Multiple Platforms
-
If I have multiple platforms, I can download for all of them:
patch1.platform=LINUX.X64 patch1.target_version=19 patch1.patch=SQLCL,AHF,CVU patch2.platform=WINDOWS.X64 patch2.target_version=19 patch2.patch=SQLCL,AHF,CVU patch3.platform=AIX.X64 patch3.target_version=19 patch3.patch=SQLCL,AHF,CVU- Notice how each platform has its own prefix (patch1, patch2, and patch3).
-
When I start AutoUpgrade in download mode, it downloads the tools for the three platforms.
That’s It
There are several tools that help you work with Oracle AI Database. Don’t miss out, update the tools and benefit from the latest enhancements.
Do you have a favorite tool that AutoUpgrade should download for you? Drop a comment and I’ll see what we can do.
Happy patching!
Databases Are Fun 
am i a alien for not have even tried SQLcl yet? i generally use sqlplus to admin tasks (like creating tablespace, change parameters etc) and any more complex query i use sql developer
LikeLike
Oh, you didn’t even try it yet. I wouldn’t call you an alien, but I think you’re missing out big time.
Be sure to use the latest version and give it a shot.
Regards,
Daniel
LikeLike
Hello Daniel, Autoupgrade is a very nice tool to download patches without looking for them in MOS. Do you think it will be able, one day, to download patches needed to upgrade Enterprise Manager 13.5/24ai (OMS, Agent, OMSPatcher, …) ?
Best Regards.
Pierre
LikeLike
Hello Daniel,
Autoupgrade is a very nice tool to download easily patch without to search into MOS…
Now, it is possible to find AHF, CVU, SQLcl, very nice too.
Do you think that Autoupgrade will be able, one day, to find and download patch for Enterprise Manager, because it’s not very easy, for OMS, Agent, OMSPatcher,… ?
Thanks a lot
Best Regards
LikeLike
Hi,
I’m glad you find it useful.
Getting patches for OEM is on the list of good ideas. Hopefully one day…
Regards,
Daniel
LikeLike
Daniel,
Love these are now included… Would also love some metadata to ease automation and of course the obligatory checksum details for the downloaded files to please security folks. These would be the icing on the cake for me!
John
LikeLike
Hi John,
I have a draft blog post that has been sitting for a while allowing me to complete it.
AutoUpgrade does a checksum verification after downloading each file. If there is a mismatch, AutoUpgrade automatically deletes the downloaded file and produces an error.
In the download folder (config file parameter “folder”) you’ll find a JSON file which contains a list of all the files AutoUpgrade has downloaded. It also lists the expected checksum so you can perform the verification yourself. Although AutoUpgrade does that, I know some customers that must perform the checksum verification themselves to satisfy security requirements.
You can file an example and some more information here:
If there are other information that you’d like to see in the file, please let me know.
Hope that helps,
Daniel
LikeLike
I did see the checksum checking in the ARU log but didn’t know it was available in a JSON file for user self comparision.
This is great! I’ll definitely take a look.
Would also be great to get some direction / examples on -noconsole (batch) mode.
LikeLike
Hi John,
I have (another) draft blog post about using AutoUpgrade with scripting in noconsole mode. It’ll probably evolve into multiple blog posts.
Are there any topics you’d be particular interested in? That might motivate me to get started! :)
Regards,
Daniel
LikeLike
As we automate the download from Oracle we cannot use autologin for the keystore as the server is different every time (unless I read this incorrectly)… Therefore I’m very interested in all things keystore whilst protecting the password inputs. For keystore creation and keystore opening to extract MOS login details. At the moment have to use expect and it is quite complex to utilise multiple stdin inputs to protect the password being in clear text. With automation it should be easier than it is and I’m hoping -noconsole can help.
LikeLike
The latest version of AutoUpgrade gives you the option of creating a “shared” keystore when you save your passwords in AutoUpgrade password loader. If you do so, then the auto-login keystore may be shared with other servers.
Using “expect” for the keystore with MOS credentials is too cumbersome compared to creating a shared keystore.
Hope that helps,
Daniel
LikeLike
Ah that is great about shared keystore… I was not aware… Thanks for the insights as that should make it so much easier ❤️
LikeLike