I totally forgot to announce the 26.4 version of AutoUpgrade. And now, the new AutoUpgrade version 26.5 is available (plus 26.4) already. The AutoUpgrade Development team did an amazing job in shortening the release cycle. This way, we can deliver quick fixes faster to you. When you study the list of enhancements and fixes carefully, some of you will say: Great, this is what I was waiting for.
Photo by julien Tromeur 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.5.260807 build.date 2026/08/07 17:06:01 +0000 build.hash 0d4f2f519 build.hash_date 2026/07/31 15:26:55 +0000 build.supported_target_versions 12.2,18,19,21,23,26 build.type production build.label (HEAD, tag: v26.5, origin/stable_devel, stable_devel) build.MOS_NOTE KB123450 build.MOS_LINK https://support.oracle.com/support/?anchorId=&kmContentId=2485457&page=sptemplate&sptemplate=km-article
Enhancements and Fixes in the newest 26.5 version of AutoUpgrade
You know it already. It is not just an “upgrade” tool anymore. 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.5 version has everything from the previous versions included.
You can see that we tackle mostly enhancements and fixes with this version:
Overview
- 23 Bugs fixed since v26.4 release.
- Released also with Release Updates 19.33 and 26.4 (OCT2026RU)
New Features
- None
New Checks
- None
Enhancements
- AUPG-4642
Update the AutoUpgrade version after creating a new Oracle Home - AUPG-5671
Call AutoUpgrade Patching to creating a home in AutoUpgrade and adjust the work flow - AUPG-6045
AutoUpgrade Patching – Inform customer when aru-bug-map.json is missing from the patch folder - AUPG-6305
AutoUpgrade Patching – Create and use user-created gold images. - AUPG-6384
AutoUpgrade Patching – List Gold Image as LOCATED when download is not needed - AUPG-6459
AutoUpgrade Patching – Implement new security parameter option for Gold Image downloads - AUPG-6509
AutoUpgrade Patching – Accept RECOMMENDED:X.Y style - AUPG-6544
AutoUpgrade Patching – Don’t enforce download=no when PATCH=GOLDIMAGE is used in create_home mode
Change in behavior
- AUPG-5897
Enhancement logging for the PGA_AGGREGATE_LIMIT check - AUPG-6070
AutoUpgrade Patching – Modified the RECOMMENDED workflow to gracefully handle cases where no - Data Pump Bundle Patch (DPBP) is available, rather than treating it as an error
- AUPG-6303
AutoUpgrade console mode proceed message is truncated causing confusion - AUPG-6521
Updated the product to use Jakarta JSON version 2.1.3, providing the latest supported implementation and compatibility improvements.
Bugs
- AUPG-6079
AutoUpgrade Patching – Wrong OCW bug number stored in aru-bug-map.json file - AUPG-6342
AutoUpgrade Patching – DPBP will be included in 23.26.4 RU starting in Oct - AUPG-6404
AutoUpgrade Patching – OCW patch no longer being downloaded when gold_image=no - AUPG-6430
AutoUpgrade Patching – Wrong JDK being selected during create home phase - AUPG-6431
AutoUpgrade Patching – Do not skip OUA request when MRP is included - AUPG-6535
AutoUpgrade Patching – Error when downloading image from OUA in Windows - BUG-39242067
Resolved an issue where SSH login banners on remote RAC nodes could disrupt remote oratab processing and cause /etc/oratab to be truncated. - BUG-39611493
Fix AutoUpgrade analyze failure when kfod checks ASM recovery-area space. - BUG-39681214
AutoUpgrade Patching – Fails to recognize 19.31 GIRU ON SOLARIS - BUG-39730296
AutoUpgrade restore is showing warning message for non-existent sqlnet file - BUG-39758946
Upgrade from 19ru to main failed with “database check failed with a runtime exception” (conname=”raca1″, stage=”prechecks”, checkname=”plug_nk_tbs_blksz_target_nk_cache_zero”. Query results were getting truncated and yielding wrong results.
REST API
- None
Features, Checks, Enhancements and Fixes in the previous 26.4 version of AutoUpgrade
As I completely forgot to write about the unbelievable amount of enhancements and fixes in the 26.4 version, I am going to list them here.
Overview
- 62 Bugs fixed since v26.3a release.
New Features
- AUPG-5709
AutoUpgrade Patching now supports Datapatch rollback
New Checks
- AUPG-5442
Check CHECKDUPLICATEDOH verifies if the Oracle home configured in CRS differs from the ORACLE_HOME value in the environment. - AUPG-5555
Add a distinct error message to differentiate replay upgrade failures versus a traditional upgrade failures. - AUPG-5604
Check CHECKGLOGIN detects glogin.sql issues when running Datapatch. - AUPG-6148
Check PFILE_INTEGRITY validates generated pfiles before startup - BUG-38875523
Check PLSQL_JSON_TYPES_NOT_PERSISTABLE to identify JSON types that are not to be used for column data. - BUG-39101324
Check STATS_MODEL_EXIST is a post-upgrade check to evaluate whether statistics models are found in the database - BUG-39117373 / AUPG-6044
Check PLUG_NK_TBS_BLKSZ_TARGET_NK_CACHE_ZERO to avoid ORA-29339 during plug-in and ORA-00379 during upgrade. Target CDB needs DB_NK_CACHE_SIZE set for all incoming non-default tablespace block sizes. Fixed in 11.2.0.4 with AUPG-6044.
Enhancements
- AUPG-5302
The Datapatch report now includes a link to status.html. - AUPG-5610
AutoUpgrade Patching – Allow drain_timeout=WAIT for “-patch” in RAC rolling - AUPG-5826
AutoUpgrade Patching – Suppress config parameter errors in create_home/download - AUPG-5842
Implement an option to use a shared auto-login keystore in AutoUpgrade - AUPG-5892
AutoUpgrade Patching – Do not abort when the autoupgrade.json file uploaded to oracle.com is in an invalid format - AUPG-6037
AutoUpgrade Patching – Change the Gold Image CSI requirement - AUPG-6231
AutoUpgrade Patching – Add configuration file parameter value supporting downloading monthly CSPUs - AUPG-6304
AutoUpgrade Patching – Download the Release Update patch file rather than the Oracle-supplied gold image - BUG-35572738
Add AutoUpgrade support for password wallet type (TDE) for non-CDB/CDB databases - BUG-38509766
Include the “Total Job Time” in the “STAGES SUMMARY” in the AutoUpgrade log - BUG-39259840
Fix issues 1-8 - BUG-39268537
AutoUpgrade keystore should not show inactive for TDE_SEPS configuration if the source and target CDB are on the same system
Changes in behavior
- None
Bug Fixes
- AUPG-3739
Unplug/plug can fail intermittently for PDBs with PATH_PREFIX - AUPG-5282
AutoUpgrade fails in the TDE Password Check - AUPG-5588
AutoUpgrade Patching – create_home + deploy was not working with %RELEASE%.%UPDATE% placeholders - AUPG-5609
AutoUpgrade Patching – Fix “lsj -a” indentation - AUPG-5642
AutoUpgrade Patching – Fix invalid argument -applyOneOffs error while creating a new home in a RAC environment - AUPG-5650
AutoUpgrade Patching – Unable to download Spatial bundles - AUPG-5666
AutoUpgrade Patching – Multiple MRP patches found for 23.26.0 - AUPG-5821
AutoUpgrade Patching – Support OKV + SEPS - AUPG-5856
AutoUpgrade Patching – Skip starting DB if already running after DB_PATCHING - AUPG-5865
AutoUpgrade Patching – Windows fails to create an SPFILE from the log directory - AUPG-5867
Dataptach rollback files are now copied into the DBUPGRADE directory. - AUPG-5883
AutoUpgrade Patching – cannot create autoupgrade.zip file - AUPG-5884
Update regex to detect DBD::Oracle errors from Datapatch’s Perl layer - AUPG-5898
In Windows, job resume does not continue from the point where it stopped - AUPG-5907
AutoUpgrade Patching – Create Home on Windows now preserves the source home account_type for domain users - AUPG-5922
AutoUpgrade stores standby SCN in scientific notation when manage_standbys_clause=standbys=all - AUPG-5948
AutoUpgrade Patching – RAC Oracle Homes are not automatically detected in Windows - AUPG-5973
AutoUpgrade Patching – On Windows, loading the Windows credentials fails when the -patch argument is not specified - AUPG-6008
AutoUpgrade Patching – When AutoUpgrade Patching calls AutoUpgrade, it uses the wrong jar - AUPG-6011
Unplug-relocate appears cross-server instead of same-server when using a dblink that points to CDB$ROOT - AUPG-6052
AutoUpgrade Patching – Skip JDK patch download for 23.26+ RUs - AUPG-6071
AutoUpgrade Patching – GRP should not be created for a SE2 database - AUPG-6072
AutoUpgrade Patching – Unable to download patch 38189383 - AUPG-6080
AutoUpgrade Patching – Manually downloading a password-protected patch does not work - AUPG-6084
Fix merge issue for class DatapatchUtils casing ignore-errors feature to not work - AUPG-6105
AutoUpgrade Patching – 23.26.2 patching aborts due to missing newer RU - AUPG-6147
AutoUpgrade adds a clear error when SPFILE-sourced parameter values cannot be safely written/read in generated pfiles - AUPG-6150
DICTIONARY_HEALTH checks now stage temporary scripts in the job temp directory - AUPG-6253
AutoUpgrade Patching – Handle MRP with a single fix - AUPG-6258
Executed Datapatch with -ignorable_errors N/A as a parameter - AUPG-6261
AutoUpgrade Patching – Gold image download fails with special characters in the MOS password - AUPG-6285
Fix issue with sqlpatch execution arguments for force_terminate_blocking_sessions. - Check SC_RAC_CRS_OH_MISMATCH fails when environment does not use Bash shell.
- AUPG-6301
AutoUpgrade Patching – DNFS BinaryOption no longer uses major version in filenames - BUG-36375778
Multiple invalid oracle maintained dba objects after AutoUpgrade ru patching job completes - BUG-38682553
AutoUpgrade terminated when there was no fatal error from noncdb_to_pdb.sql - BUG-39037043
Windows AutoUpgrade fails when creating a sample config file - BUG-39074391
LNX-1931-CMT: Upgrade of the SEHA database failed with DCS-10001 – PRGT-440: the database upgrade operation failed - BUG-39129478
AutoUpgrade job failed because sqlnet.ora contained an invalid string, and no precheck validation was performed on the file - BUG-39153364
Upgrade of 19.29 tde RACONE database failed with prgt-440 - BUG-39231023
AutoUpgrade: BasicTdeInfoCombiner IllegalStateException for a refreshable clone via CDB$ROOT dblink - BUG-39418834
AutoUpgrade check PLUG_NK_TBS_BLKSZ_TARGET_NK_CACHE_ZERO throws upg1010 after target cdb has non-zero db_32k_cache_size - BUG-39522665
AutoUpgrade RAC SYSUPDATES stage fails stopping pdb services in upgrade mode
REST API
- None
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
–Mike
Hello Mike,
With the latest version, is it now possible to set the PATH_PREFIX in the config file?
We raised a request via the SR#4-0002546083. In the blog here I don’t see any mention about this.
Thanks,
Sreedhar Medipally
Hi Sreedhar,
you can check by yourself I hope – the bug number you have received for the enhancement request is bug/er: 39676704 which is not listed.
I wait for feedback from the developer and will mail you.
In the future, it is better if you mail me directly, please, since we work together directly already.
Cheers,
Mike
I’m ready to try AutoUpgrade again; previously, some RAC/GI restrictions. Can this entire workflow now be automated? 3-node RAC, 3 DBs served by single Oracle Home on each node. How do I construct a CFG file (maybe 2?) that would automate applying RU+recommended to every Oracle Home and GI Home on all 3 nodes with minimal downtime? Can be in-place or new homes. Before, I was not able to use AutoUpgrade to patch Grid Homes. Thanks.
Hi Bob,
autoupgrade still can’t install or patch your GI home. This is in the making but will take a bit. Spec is written and finalized while I write.
Everything else, including the download of your OCW RU can be done with AutoUpgrade:
global.global_log_dir=/Users/mdietric/TEMP/AU/logsglobal.keystore=/Users/mdietric/TEMP/AU/keystore
global.folder=/Users/mdietric/TEMP/AU/patches
patch1.platform=LINUX.X64
patch1.target_version=19
patch1.patch=OCW
patch1.gold_image=AUTO
Would download the 19.32 GI RU.
But the patch/install of GI is in your hands right now.
For building a proper config file, use Marcus’ Composer:
https://autoupgrade-composer.com/
I advertised this on the blog as well, and we are in constant exchange with Marcus to make sure he has the newest things in the composer, too.
Furthermore, try it out for downloading.
It makes your life so much easier than reading through MOS notes and searching for patch numbers.
Start here:
https://mikedietrichde.com/2026/07/06/autoupgrade-patching-from-zero-to-hero-part-1/
Cheers,
Mike
Hello Mike !
At a time network security is a central subject, do you know the exact IP range and ports a network team should open for using this tool from an internal server ?
Is there a way to get some kind of insurance that what is downloaded is valid and really comes from oracle, like a certificate-signed source file ?
See here, Jefferson:
https://mikedietrichde.com/2026/07/08/autoupgrade-patching-from-zero-to-hero-part-3-download-patches/
Everything documented to share with your IT team.
And the “insurance” is built in. When you look at the download activity, AU does a “VERIFY” at the end. This is a cross-check which happens automatically of what has been downloaded with the checksum file being stored on MOS/ARU and OUA. So, we always check if the download is exactly the same on your disk compared to what you asked to download.
Cheers,
Mike
Hi Mike,
on Windows Plattform when AU-Patching with AU-26.5 we get the same problem in DRIAN-Stage
“Error: ORADIM-101
C:\temp\AutoUpgrade\Logs\CPADBAA\temp\error_SOURCE_DELETE_CPADBAA.txt
Unable to stop service, OS Error = 1062”
as I repored some days ago with AU-25.4 – I opened a SR as requested: SR 4-0003497230
no problems with AU-26.2
Best Regards
Marco
Marco,
i let Byron know. I think he has been kept up with other things.
Thanks
Mike
Hi Mike,
thanks for the feedback – I have added all information I collected to the SR.
All AU-versions equal or lesser than 26.3 are ok – 26.4 and 26,5 run into “Error: ORADIM-101” while in DRAIN-Stage.
have a good time in Paraguay, Brazil and Uruguay 🙂
Best Regards
Marco
Marco,
Byron is working on it.
Thanks
Mike
Hi Mike,
We see an issue with 26.5 and that looks like following:
ORAHOMES installed with 26.4, using “patch=recommended,ocw”, can not be “deployed” using 26.5 as it expects some MRP’s to be installed.
An orahome installed with 26.4 looks like:
$ ./opatch lspatches
39526364;OCW RELEASE UPDATE 19.32.0.0.0 (39526364)
39222882;OJVM RELEASE UPDATE: 19.32.0.0.260721 (39222882)
39657094;DATAPUMP BUNDLE PATCH 19.32.0.0.0
39472050;Database Release Update : 19.32.0.0.260721 (39472050)
An orahome installed with 26.5 using the same config file looks like:
39526364;OCW RELEASE UPDATE 19.32.0.0.0 (39526364)
39779336;Fix for Bug 39779336
39750798;Fix for Bug 39750798
39661089;Fix for Bug 39661089
39222882;OJVM RELEASE UPDATE: 19.32.0.0.260721 (39222882)
39657094;DATAPUMP BUNDLE PATCH 19.32.0.0.0
39472050;Database Release Update : 19.32.0.0.260721 (39472050)
Since we have installed all orahomes immediately after the RU was released, we have to reinstall them all again, or step back to version 26.4 of autoupgrade.
What do you recommend??
Hi Frank-Jan,
I won’t add a comment since we did follow up on email.
Cheers,
Mike
Hello Mike,
Is JDK still not supported in the latest version?
I got the following error when using “patch=RECOMMENDED,OCW,JDK,29213893,34774667,38238416,38723830,28090604,33396432”:
############################################################
*Downloading files
Download failed
*Gold image validation failed – Gold Image validation cannot continue because the following patches are missing from the Gold Image: [39791916]*
– Bootstrap.processCLIParams#83
oracle.commonx.utils.errors.ConfigurationError:
There were conditions found preventing AutoUpgrade Patching from successfully running
*Downloading files
Download failed
*Gold image validation failed – Gold Image validation cannot continue because the following patches are missing from the Gold Image: [39791916]*
###########################################################
Patch 39791916 is the JDK BP 19.32 Aug2026, so it was correctly identified as the latest available JDK patch.
Regards,
Nick
Hi Nick,
it is supported but we struggle a bit with the different information in the JDK, and what has been packaged into the gold image.
Can you check what the Gold Image has, and what version of the JDK you’D download separately?
Thanks
Mike
Hello Mike,
There was no Gold Image file in the download directory.
Two 19.32 JDKs were released – Patch 39329591: JDK BUNDLE PATCH 19.0.0.0.260721 and Patch 39791916: JDK BUNDLE PATCH 19.0.0.0.260818.
AutoUpgrade chose the latter one, which is correct. The whole process failed after more than 2 hours. I can upload log files if you’re interested.
Another run with the same configuration but without JDK, succeeded.
Regards,
Nick
Hi Nick,
it usually depends on how and whether you use the prefix.gold_image= parameter. The default will try to pull the gold image, and 19c has a 3 months old JDK in it (26ai has the current one already). When you say prefix.gold_image=yes/all, then it will build one – which takes up to two hours (or even more).
Mike
Hello Mike,
Why are MRP patches applied when they haven’t been requested (AU version 26.5)?
Three patches were applied when using either “patch=RECOMMENDED,OCW,29213893,34774667,38238416,38723830,28090604,33396432”
or “patch=OCW,RU,OJVM,DPBP,OPATCH,AU,29213893,34774667,38238416,38723830,28090604,33396432”:
39661089: Fix for Bug 39661089
39750798: Fix for Bug 39750798
39779336: Fix for Bug 39779336
Regards,
Nick
Hi Nick,
MRPs are included into the Gold Image out of the box already since they are considered now as essential.
Cheers,
Mike
Hi Mike,
Can I use autoupgrade for out-of-place patching of the Grid Infrastructure 19c/26ai?
Best regards,
Alex.
Hi Alexander,
not yet – we are working on the GI patching part but it will take several months until we can release it.
But spec is written and finalized already. And the team is working on it.
Thanks
Mike
I’m using this to patch and its a great tool. But I have a problem, the problem is the network config files (ldap.ora,tnsnames.ora) are copied at the end of the patching process.
But I want to keep the db available for users during the datapatch phase. However, that means there is a window of an hour or so, when the datapatch is running but ldap.ora doesn’t exist. If any uses try a dblink then they will get an error.
Is there any option to get autoupgrade to copy these files earlier in the process – like maybe in the create_home phase? thanks
Hi Martyn,
would you please do me a favor and drop me an email so we can further investigate and get back to easy (easier than doing it through the blog).
mike.dietrich …. oracle.com is the one.
Cheers,
Mike
Hi Mike,
I have been trying to create a new home using the new version of AutoUpgrade (mode=create_home).
The installation uses a gold image containing RU 19.32, OJVM, DPBP, OCW, and MRP, along with the JDK and one-off patch 38238416 added separately (for some reason, they cannot be included in the image itself).
The JDK installation completes successfully, but when attempting to apply one-off patch 38238416, a conflict arises with patch 39948860; this means one-off patch 38238416 conflicts with this merge patch, which is already present in the image. Patch 39948860 is applied via the latest MRP (19.32.0.0.260902).
Patch 39948860 (Merge patch for bugs 39906400, 39918912)
The following patches have conflicts. Please contact Oracle Support and get the merged patch of the patches:
38238416, 39948860
Conflicts/Supersets for each patch are:
Patch: 38238416
Conflict with 38238416
Conflict details:
/u01/app/oracle/19.0.0/db_2/lib/libserver19.a:qkscr.o
/u01/app/oracle/19.0.0/db_2/lib/libserver19.a:kqtph.o
/u01/app/oracle/19.0.0/db_2/lib/libserver19.a:kxtt.o
/u01/app/oracle/19.0.0/db_2/lib/liboraolap19.a:xsdbts.o
/u01/app/oracle/19.0.0/db_2/lib/libserver19.a:kta.o
/u01/app/oracle/19.0.0/db_2/lib/libserver19.a:ktst.o
/u01/app/oracle/19.0.0/db_2/lib/libserver19.a:qksbg.o
/u01/app/oracle/19.0.0/db_2/lib/libserver19.a:qksfm.o
/u01/app/oracle/19.0.0/db_2/lib/libserver19.a:kspt.o
Conflict with 39948860
Conflict details:
/u01/app/oracle/19.0.0/db_2/lib/libserver19.a:qkscr.o
/u01/app/oracle/19.0.0/db_2/lib/libserver19.a:qksbg.o
/u01/app/oracle/19.0.0/db_2/lib/libserver19.a:qksfm.o
How can we resolve this? Many thanks.
Regards,
Víctor
Hi Victor,
you need to open an SR, please. I think this has been introduced with the “out of schedule” September 2 MRP.
Sorry for the inconvenience!
Mike
Hi,
on linux and unix systems is there a chance to add the root password. So the complete installation of a new oracle home is possible. I’m no fan of the sudo solution.
Regards Thomas
Coming somebody 🙂
Wait for it … we work on solutions!
Cheers,
Mike