Yes, the long-awaited new AutoUpgrade version 26.6 is available for download. Again, a fantastic job by our development team. And I know that many of you were waiting for it already since it has some really cool new features, enhancements – and of course, fixes, too.

Photo by Jason Leung on Unsplash
Download AutoUpgrade
As I described already in AutoUpgrade Patching β From Zero to Hero β Part 1: Download AutoUpgrade, you have several ways to fetch the newest version of AutoUpgrade – and when you use it to download patches, it will automatically trigger an update with the newest tool by downloading it.
Another quick way is this:
curl -L -O https://download.oracle.com/otn-pub/otn_software/autoupgrade.jar
But please, check out Download AutoUpgrade and choose your best way.
Version Change
When you call AutoUpgrade with the -version option, it should tell you then:
java -jar patches/autoupgrade.jar -version build.version 26.6.260925 build.date 2026/09/25 22:11:20 +0000 build.hash e53aa37a5 build.hash_date 2026/09/25 18:13:12 +0000 build.supported_target_versions 12.2,18,19,21,23,26 build.type production build.label (HEAD, tag: v26.6, origin/stable_devel, stable_devel) build.MOS_NOTE KB123450 build.MOS_LINK https://support.oracle.com/support/?anchorId=&kmContentId=2485457
Quick Fix for file permissions on the keystore
If you move to the new AU version, please make sure you check this blog post:
Amazing Enhancements in the newest 26.6 version of AutoUpgrade
You know it already. It is so much more than just an “upgrade” tool. It patches your databases, it finds and downloads the patches, it creates your Oracle – and so much more. Always use the newest – and the fixes and enhancements are certainly cumulative, meaning the 26.6 version has everything from the previous versions included.
What I like a lot is the new ability to download CPAT directly now with AutoUpgrade by using prefix.patch=CPAT in the config file. And of course, the ability to fetch Enterprise Manager patch bundles, too. And DBSAT. And SQLcl. Well, and you can also fetch the Exadata patches and the Grid Infrastructure Gold Images now with AutoUpgrade. Let me show a quick example config file for your convenience – and be aware that alone the EM patches are massive:
global.global_log_dir=/Users/mdietric/TEMP/AU/logs global.keystore=/Users/mdietric/TEMP/AU/keystore global.folder=/Users/mdietric/TEMP/AU/patches patch1.patch=OEM:24.1 patch1.target_version=26 patch2.patch=OEM:13.5 patch2.target_version=26 patch3.patch=CPAT patch3.target_version=19 patch4.patch=DBSAT patch4.target_version=19
This will fetch the following bundles and tools:
java -jar autoupgrade.jar -config em.cfg -patch -mode download
AutoUpgrade Patching 26.6.260925 launched with default internal options
Processing config file ...
Loading AutoUpgrade Patching keystore
AutoUpgrade Patching keystore is loaded
----------------------------------------------------
Downloading files to /Users/mdietric/TEMP/AU/patches
----------------------------------------------------
Oracle Enterprise Manager 24ai Release 1 Update 13 (24.1.0.13) for Oracle Management Service
File: p39815035_241000_Generic.zip - VALIDATED
Oracle Enterprise Manager 24ai Release 1 Holistic Patch for Oracle Management Service - September 2026
File: p39984254_241000_Generic.zip - VALIDATED
Oracle Enterprise Manager 24ai Release 1 Update 13 (24.1.0.13) for Oracle Management Agent
File: p39815042_241000_Generic.zip - VALIDATED
OMSPatcher patch of version 13.9.24.17.0 for Enterprise Manager 24.1.0.0.0
File: p19999993_241000_Generic.zip - VALIDATED
AgentPatcher patch of version 13.9.25.3.0 for Enterprise Manager 24.1.0.0.0
File: p33355570_241000_Generic.zip - VALIDATED
----------------------------------------------------
----------------------------------------------------
Downloading files to /Users/mdietric/TEMP/AU/patches
----------------------------------------------------
Oracle Enterprise Manager 13c Release 5 Update 34 (13.5.0.34) for Oracle Management Service
File: p39820104_135000_Generic.zip - VALIDATED
Oracle Enterprise Manager 13c Release 5 Holistic Patch for Oracle Management Service - September 2026
File: p39984261_135000_Generic.zip - VALIDATED
Oracle Enterprise Manager 13c Release 5 Update 34 (13.5.0.34) for Oracle Management Agent
File: p39820108_135000_Generic.zip - VALIDATED
OMSPatcher patch of version 13.9.5.27.0 for Enterprise Manager Cloud Control 13.5.0.0.0
File: p19999993_135000_Generic.zip - VALIDATED
AgentPatcher release of version 13.9.5.10.0 for Enterprise Manager Cloud Control Agent 13.5.0.0.0
File: p33355570_135000_Generic.zip - VALIDATED
----------------------------------------------------
----------------------------------------------------
Downloading files to /Users/mdietric/TEMP/AU/patches
----------------------------------------------------
Cloud Premigration Advisor Tool (CPAT) for version 11.2.0.4 and Higher
File: p32613591_112048_Generic.zip - VALIDATED
----------------------------------------------------
----------------------------------------------------
Downloading files to /Users/mdietric/TEMP/AU/patches
----------------------------------------------------
DATABASE SECURITY ASSESSMENT TOOL - DBSAT 4.3 (JUL 2026)
File: dbsat.zip - VALIDATED
----------------------------------------------------
Pretty amazing, isn’t it?
Enhancements, new Checks and Fixes in AutoUpgrade 26.6
Here is a consolidated list of enhancements and fixes with this version:
Overview
47 Bugs fixed since AutoUpgrade v26.5 release.
New Features
- AUPG-6506
Added support for Standard Edition High Availability (SEHA) and enhanced Oracle RAC One support to start the RAC database on the current node where AutoUpgrade is running. - AUPG-6517
Added CPAT download capability in AutoUpgrade Patching. - BUG-39676704
Added the PATH_PREFIX option for AutoUpgrade with refreshable clones.
New Checks
- AUPG-6564
Add a precheck MAINTENANCE_WINDOW to clearly explain expected behavior, potential service impact, duration, and required customer actions when a maintenance window begins.
Enhancements
- AUPG-5111
Apply timeouts per fixup instead of per job or stage. - AUPG-6015
Add the missing patching information to the help output. - AUPG-6213
Download SQLcl and verify it against the published checksum; display a warning if verification fails. - AUPG-6352
Support downloading the Database Security Assessment Tool (DBSAT) in AutoUpgrade Patching download mode. - AUPG-6515
Include file and patch metadata in patches_info.json. - AUPG-6532
Improve target_version validation in AutoUpgrade Patching. - AUPG-6583
In AutoUpgrade Patching, report an error when a patch contains no files. - AUPG-6595
Support downloading patches for Oracle Enterprise Manager in AutoUpgrade Patching. - AUPG-6602
Support downloading patches for Exadata in AutoUpgrade Patching. - AUPG-6614
Support the device flow for ARU credentials in AutoUpgrade Patching. - AUPG-6631
Display analyze-check totals and preupgrade report paths for each job. - AUPG-6639
Support GI gold image downloads in AutoUpgrade Patching. - AUPG-6657
Support prechecks when -mode create_home is invoked for AutoUpgrade Patching. - AUPG-6729
Add the CSPU option for 21c in AutoUpgrade Patching. - AUPG-6741
Support AutoUpgrade Patching deployment on the same RU version. - BUG-39839808
Correct a false AutoUpgrade Patching error indicating that the OJVM version [19.BB] must not be older than the RU version [19.AA].
Change in behavior
- AUPG-6355
AutoUpgrade Patching now excludes AHF from gold image requests. - AUPG-6572
Allow AutoUpgrade Patching to download dependent patches when the RU is password-protected or missing. - AUPG-6716
AutoUpgrade Patching now supports Data Pump bundle patches for the 23.26.4 RU. - BUG-39957813
Increase the GRP abort timer.
Fixes
- AUPG-4996
Add a command-line resume option. - AUPG-6362
Handle cases where the ar command on AIX returns no value. - AUPG-6528
Prevent REPLAY upgrades from starting when REPLAY is not specified in the configuration file. - AUPG-6559
Omit the second parameter from sys.dbms_pdb.describe for non-CDB source databases in TARGET_CDB_COMPATIBILITY check. - AUPG-6617
Gracefully handle Windows services that are already stopped during service deletion. - AUPG-6619
Correct an invalid format display with precheck SC_GLOGIN_CONFLICTING_COMMANDS. - AUPG-6667 ,AUPG-6833
Update the shipped libraries. - AUPG-6691
Change the build link to its short version. - AUPG-6698
Synchronize sanity check SC_DATAPUMP_RUNNING with the Datapatch team. - AUPG-6710
Fix precheck PREVENT_EMPTY_DATAPATCH_DIRECTORY_ERROR from failing by ensuring target directory exists. - AUPG-6732
In AutoUpgrade Patching, report when the Oracle Text patch file is missing while applying 19.32. - AUPG-6733
Support password-grant authentication for production clients in AutoUpgrade Patching. - AUPG-6734
Prevent Oracle ClusterWare from using the Linux.x64 patch on AIX during AutoUpgrade Patching. - AUPG-6753
Report an invalid target_home in AutoUpgrade Patching create_home mode. - BUG-39549036
Fix the post-upgrade CDB$ROOT failure caused by an error reading the OPatch inventory file. - BUG-39697010
Fix DISPATCH failures when an application PDB has a lower CON_ID than its application root. - BUG-39793265
Copy TNSNAMES.ORA before starting the upgrade of the database. - BUG-39805864
Fix SC_RAC_CRS_OH_MISMATCH precheck failure caused by an unexpected output from an ssh login banner. - BUG-39832743
Use PART_OFF instead of PARTITIONING_OFF for 26.4 AutoUpgrade Patching to match the 19c Makefile. - BUG-39836223
Fix failures during normal-mode AutoUpgrade Patching when a time zone upgrade is requested. We now validate that the database is in upgrade mode when upgrading time zone in RAC cluster. - BUG-39845581
Handle DISK_SPACE_FOR_RECOVERY_AREA values without raising NumberFormatException. - BUG-39846103
During AutoUpgrade prechecks or fixups, the logs may display an apparent ORA-00096 error indicating that optimizer_features_enable=’x’ is invalid, even though the process continues successfully. - BUG-39983243
In some cases, the PLUG_NK_TBS_BLKSZ_TARGET_NK_CACHE_ZERO precheck fails while parsing the SQL query output.
REST API
None
Composer tools
I know that Marcus Vinicius has updated the AutoUpgrade Composer already. And not sure if you are aware, but Kamil Stawiarski has launched ALIS, too π
So, in case you struggle with creating your own config file, the two tools will help you for sure in getting started.
Further Links and Information
- AutoUpgrade Patching β From Zero to Hero β Part 1: Download AutoUpgrade
- https://www.oracle.com/goto/upgrade
- MOS Note: KB123450
- wget https://download.oracle.com/otn-pub/otn_software/autoupgrade.jar
- curl -L -O https://download.oracle.com/otn-pub/otn_software/autoupgrade.jar
- AutoUpgrade 26.5 and 26.4 (August 2026)
- Quick fix for download issues with AutoUpgrade 26.6
–Mike
P.S.: No AI resources or LLM Tokens have been wasted to craft this blog post. It’s my own words, and my limited non-native-speaker writing skills you are dealing with π Enjoy!!
Excellant article.
I will need to research what these mean. I thought 26AI with RECOMMENDED would be pulling data pump patches. Was that not the case?
Also, patching deployment on the same RU… I think I ran into that limitation but trying to remember the use case.
AUPG-6741 Support AutoUpgrade Patching deployment on the same RU version.
AUPG-6716 AutoUpgrade Patching now supports Data Pump bundle patches for the 23.26.4
Hi David,
there is a difference between RECOMMENDED and RECOMMENDED. Sounds strange, I know.
When we can pull the complete gold image from OUA, then RECOMMENDED takes the gold image (which has no DPBP in it), and downloads the additional pieces from MOS.
When the you don’t download from OUA, for instance now for IBM AIX, we will got to MOS only, and then RECOMMENDED will include the DPBP. It really depends on what is provided where. But when you say “RECOMMENDED”, we make sure you always get the DPBP as well.
Cheers,
Mike
Is there any benefit of using AutoUpgrade compared to opatchauto when it comes to patching rather than upgrading?
We’re running standalone servers running ASM and CDB/PDB’s.
With opatchauto we are patching both GI home and DB home together
Yes, tons.
We run extra checks – and you opatchauto in a cluster environent usually.
AU give you more control, and especially the WAIT option for DRAIN which opatchauto doesn’t has.
Cheers,
Mike
Hi Mike
The Enterprise Manager patch download has potential. I will have to try it for the October critical patch updates. Looking at it today it isn’t downloading all the patches that show on the July CPU list, e.g. not downloading 38445807 (perl), 39638312 (wls), 39039951 (owsm) but I haven’t checked the September holistic patch and RU13 contents that are now downloaded… maybe these have been adopted.
Is there “official” documentation for Autoupgrade somewhere that gives more details around oem patch. All I can see are KB123450 which was updated yesterday but doesn’t mention Enterprise Manager, and the database autoupgrade documentation, which seems similarly lacking..
It would be nice for example to know whether patch1.target_version in your example does anything and whether there are further parameters that can be used.
Regards
Tim
Hi Tim,
we are working on improving this – to be frank, we weren’t fully aware how many things are needed in addition.
Please stay tuned …
The next version of AU will do better.
Cheers,
Mike
Just in time! Great! Will test Exadata patch download in the upcoming Exa patch session
It’s amazing – but they are huuuuuuuge!
Mike
Hi Mike,
thanks for the information.
I just tested on Windows “AUPG-6617 – Gracefully handle Windows services that are already stopped during service deletion.” and it looks good.
And it looks like one other unpleasent issues is also fixed after nearly 1 year, but not mentioned here π
– After successfull AU-Patching the Windows-Services (Instance) are now set to automatic and not to manual, as before. Maybe already fixed in 26.4 or 26.5 but not able to test due to bug “AUPG-6617”
Thanks Marco!
Mike
Thanks for the OEM patches – amazing!!
Happy that you like it!!
Mike
Hi Mike,
thanks a lot for deploying such a great feature like “download OEM patches”.
I’ve tried to download some additional agent one offs like…
WLS PATCH SET UPDATE 12.2.1.4.260823 PATCH 39919567
…without success.
These patches like:
WLS PATCH SET…
OWMS BUNLDE…
are also listed in every CPU release and we regulary install them.
A, i missing something or is this a possible feature? π
Markus
Markus,
we are collecting the missing pieces.
Cheers,
Mike
Hello Mike,
many thank for this great and helpful feature “download OEM patches”.
I’ve tried to download some additional agent patches like “OWSM BUNDLE PATCH” or “WLS PATCH SET UPDATE”. These patches are mentioned/recommended in every CPU-Update and we install them regulary.
Unfortunately i’ve received the message that Auto Upgrade doesn’t find those patch id’s:
*Downloading files
Cannot find the patch for bug 39919567
Am i missing something or could this a potentially be a new feature?
Regards
Hi Markus,
we will include the missing pieces in the next version of AutoUpgrade.
We were not aware of all the things needed in addition.
Thanks for your patience,
Mike
Excellent, we will stop wasting time searching for patches.
I will happily test that on my next patching session.
Please do so!
Thanks
Mike
Hi Mike,
I think it’s great that Enterprise Manager patches can be downloaded via AutoUpgrade. However, I’m missing several patches for the Enterprise Manager Agent, such as the RU34-related patches for WLS, OMS, and the JDK. In older patch bundles, OSS patches were often included as well, and sometimes even Perl-related patches.
It would be great if there were an option to download the recommended patches in addition to the currently available ones. This would make it much easier to keep Enterprise Manager environments up to date and ensure that all relevant components are patched consistently without having to manually identify and download additional dependencies.
Thanks!
Hi Micha,
we realized that there are things missing. We’ll do our best to include everything in the next release of AU.
We were not aware that there is so much more including a specific opatch.
Cheers,
Mike
Hi Mike,
I’ve tested on windows and wanted to create a windows service using the after_update.deploy option. I cannot find any logging of this action (stdout/stderr) in the postupgrade subdirectory of the job as described in the documentation.
https://docs.oracle.com/en/database/oracle/oracle-database/26/upgrd/patch-parameters-autoupgrade-config-file.html#GUID-499C682C-2C02-4110-B451-8C05B8D782A1
The windows service is running as Local System so autoupgrade can’t create the service using a credential file.
The interesting part of my config file looks like this:
patch1.drop_win_src_service=yes
patch1.after_action.deploy=\cre_win_trgt_service.bat
cre_win_trgt_service.bat looks like:
%ORACLE_HOME%\bin\oradim.exe -new -sid %ORACLE_SID% -startmode auto -srvcstart system
What am I missing?
Hi Erwin,
I need to check with Byron since I am not able to test anything on Win unfortunately.
CHeers,
Mike
Hi Mike,
vielen Dank fΓΌr die neuen Informationen. Das neue AutoUpgrade-Tool finde ich echt klasse β es kann ja fast die ganze Welt aktualisieren! π
Wir haben allerdings ein Problem in unserer Umgebung: Wenn ich versuche, mit AutoUpgrade unsere Standby-Datenbanken zu patchen, sucht das Tool nach der SPFILE im dbs-Ordner. Da wir die SPFILE jedoch in ASM gespeichert haben, wird sie dort nicht gefunden, und der Prozess endet mit einem Fehler:
ERROR Error found when copying the spfile in the standby database. Job oracle.upgrade.autoupgrade.utils.errors.UPG2002: It was not possible to find spfile or init file in directory /u01/app/oracle/product/23.0.0.0/dbhome_4/dbs. Job 100
Als Workaround habe ich fΓΌr eine Datenbank eine Datei spfilexxx.ora im dbs-Ordner erstellt, die auf den Speicherort der SPFILE in ASM verweist. Damit konnte ich die Standby-Datenbank erfolgreich patchen (out of place).
Da wir jedoch etwa 200 Datenbanken haben und sich der Speicherort der SPFILE nach einem Restore mΓΆglicherweise Γ€ndern kΓΆnnte, wΓΌrde ich diesen Ansatz nur ungern fΓΌr alle Datenbanken verwenden.
Hast du vielleicht eine LΓΆsung fΓΌr uns?
Vielen Dank und viele GrΓΌΓe,
Amin
Hi Amin,
I will follow up via email.
Cheers,
Mike