It’s October – and while the leafs keep falling on the northern hemisphere, the October 2025 Release of AutoUpgrade (25.6) is available. Get it now – and find the list of features and fixes below.

Photo by Louise Pilgaard on Unsplash
How to download it?
As usual, that’s very simple. You either download it via the well-known
or you fetch it directly from oracle.com with curl, wget or by just clicking on the big button.
What’s new?
Again, a lot. 25.6 release has a significant and important number of enhancements. It includes the fixes and enhancements for 25.5 as well. 25.5 is the version included into the 19.30 January 2026 Release Update whereas 25.6 is the slightly newer version available on My Oracle Support and oracle.com.
build.version 25.6.251016 build.date 2025/10/16 00:04:36 +0000 build.hash 54a1e2442 build.hash_date 2025/10/15 21:11:40 +0000 build.supported_target_versions 12.2,18,19,21,23 build.type production build.label (HEAD, tag: v25.6, origin/stable_devel, stable_devel) build.MOS_NOTE 2485457.1 build.MOS_LINK https://support.oracle.com/epmos/faces/DocumentDisplay?id=2485457.1
The highlights this time are:
- Enhanced MS Windows support for download and patching, e.g. not requiring an admin account anymore for downloading and better oradim support
- Patching and download support for Oracle Database 21c and Oracle AI Database 26ai
- Download and apply of the JDK – this is super-useful and a great relief
- Download and apply dNFS patches
One limitation is important to mention: We don’t support upg1.target_version=26 even though a grep may tell you.
[oracle@caldbcs1 ~]$ grep 'target_version' /home/oracle/auto_config_26ai.cfg # <prefix>.target_version #upg1.target_version=12.2|18|19|21|23|26
Right now you need to use upg1.target_version=23, please. Technically, this is fully correct but we understand that you may want to use “26” when we call the release now officially Oracle AI Database 26ai. The support for “26” will be included in the next release of AutoUpgrade.
New Features
- AUPG-4603
Allow creation of Oracle home as part of a database upgrade - BUG-35726156
Windows service creation for both deploy and restoration is now performed using the ORADIM utility
New Checks
- AUPG-4803
Check REMOTE_TARGET_CDB_AVAILABILITY performs PDB related checks when source and target servers are on different servers
Enhancements
- AUPG-3361
Create a global Windows credential - AUPG-4413
AutoUpgrade Patching now supports patching a standby database - AUPG-4566
-load_password prompt indicates that the password has an unknown validation status for OKV keystores - AUPG-4754
AutoUpgrade Patching – Add support to create a listener - AUPG-4804
AutoUpgrade Patching – Add support for 21c and 26ai - AUPG-4811
Add an option on the local wincredential to allow customers to override global entry wincredential - AUPG-4836
Support downloading the latest JDK patches for Oracle home - AUPG-4850
Allow delete_wincredential_file configuration parameter to be set globally - AUPG-4875
AutoUpgrade Patching – Add support for time zone upgrades - AUPG-4906
AutoUpgrade Patching – Ensure proper support for Oracle Direct NFS (dNFS) - AUPG-4958
Ensure correct setup for temp directory - AUPG-4975
AutoUpgrade Patching – Support domain usernames in home_settings.account_type parameter - AUPG-4980
Set Windows registry value ORA_LPENABLE in the target_home to the same value that was found in the source_home - AUPG-5040
IllegalArgumentException thrown in getDirectory for the DISPATCH method when a stage did not have its own log directory - AUPG-5058
AutoUpgrade Patching – Update error message for -mode create_home when target home is not empty - BUG-38191332
Validate startup environment to ensure AutoUpgrade can run utilities
Change in behavior
- AUPG-4915
Allow download mode on Windows without “Administrator” rights - AUPG-4936
AutoUpgrade Patching should not allow execution for -mode prefixups command on a standby database - AUPG-4995
Simplify and document how to override an internal value
Bugs
- AUPG-2959
Distributed RAC hangs if the -follower job fails to start - AUPG-3547
After a successful upgrade that used the Windows credentials file, this file gets deleted. If the customer tries to restore the job without recreating the credentials file, the restore fails as expected, but the database inadvertently gets shutdown. - AUPG-4888
Execute check MAX_DB_FILES_EXCEEDED for plugins where the source and the target are the same version - AUPG-4898
Validate the presence of target_pdb_copy_option during configuration validation - AUPG-4932
Status report is missing information - AUPG-4938
When a user specifies a path in the configuration file that contains special characters, the path is truncated before the special character. - AUPG-5007
Validate and disallow keystore and global_log_dir to be the same directory - AUPG-5009
AutoUpgrade is not creating invalid object table during prefixups stage - AUPG-5011
AutoUpgrade Patching – Support dashes and periods in home_settings.account_type parameter - AUPG-5063
Checks LC_ALL and LC_CTYPE were failing on the Solaris platform - AUPG-5071
AutoUpgrade Patching – exclude writable validation for folder parameter if download=NO - BUG-37746571
Check TARGET_HOME_REGISTERED_INVENTORY fails in some cases with misleading information - BUG-38113397 –
Update check EXADATA_USE_LARGE_PAGES to ignore SGA size - BUG-38144283
AutoUpgrade is bringing down source PDB during a relocate - BUG-38154461
Synchronize java threads ensuring memory consistency - BUG-38212028
Invalid value of null was set to renamed parameter LDAP_DIRECTORY_ACCESS - BUG-38237474
Check TARGET_HOME_REGISTERED_INVENTORY failed due to missing utility option - BUG-38269586
Utility UTLPRPOM.SQL on 18.4 -> PLS-00302: COMPONENT ‘ORACLE_MAINTAINED’ MUST BE DECLARED - BUG-38305507
RAC distributed PDB upgrades is missing the postupgrade log file - BUG-38344958
RAC PDB restoration failed due to not quoting the PDB name - BUG-38360852
AutoUpgrade gets stuck in a loop when trying to shutdown the RAC database during DRAIN stage - BUG-38391324
AutoUpgrade formatting issue in html analyze report
REST API
- None
–Mike
Hi Mike
Good evening
A question, does autoupgrade perform a backup before applying the patch in Oracle Database 19c in case a rollback is needed?
On the other hand, I understand that the 19c grid infrastructure cannot be patched via autoupgrade. Here are some backup mechanisms we should ensure before applying the patch to avoid the risk of being left without a rollback option.
Thank you very much for your support.
Hi Victor,
a backup of “what” actually?
Do you mean a backup of the database?
AU patches out-of-place, meaning the previous binary home is kept. And in case a rollback is needed from the database side, all the rollback scripts are kept within the database as a zipped archive.
Thanks,
Mike
Hi Mike,
we are testing to use the autoupgrade.jar patching methode for our DB-Server.
The test of an active dfns DB failed with out-of-place patching (the target has it not activated), is this not automated?
with the following command we activated the dfns:
cd $ORACLE_HOME/rdbms/lib && make -f ins_rdbms.mk dnfs_on
Hi Sebastian,
this is a very good point – and unfortunately not ON by default.
But since we have the coolest developers in the team, they created an option for it:
https://docs.oracle.com/en/database/oracle/oracle-database/26/upgrd/patch-parameters-autoupgrade-config-file.html#GUID-96908211-FC48-4F4A-B51A-1FB26A9B76F7
patch1.home_settings.binopt.dnfs=YES
If you add this, it will do it for you 🙂
Cheers,
Mike
Hi Mike,
Thank you for the regular update on autoupgrade. No doubt this tool has been evolved a lot.
Today, I got a new issue from nowhere while upgrading two 12.10.2 PDBs from one server to 19.28 in another server with remote clone option.
Note: Both PDBs are migrated to same 19c container.
My 1st DB(DatabaseA) upgrade completed successfully. While doing the fixups mode for 2nd database, got error for TARGET_CDB_COMPATIBILITY.
The following plugin violations with type=’ERROR’ are found:
DatabaseA 1 ERROR RESOLVED Database option CATALOG mismatch: PDB installed version 12.1.0.2.0. CDB installed version 19.0.0.0.0. Fix the database option in the PDB or the CDB
DatabaseA 1 ERROR RESOLVED Database option CATJAVA mismatch: PDB installed version 12.1.0.2.0. CDB installed version 19.0.0.0.0. Fix the database option in the PDB or the CDB
DatabaseA 1 ERROR RESOLVED Database option CATPROC mismatch: PDB installed version 12.1.0.2.0. CDB installed version 19.0.0.0.0. Fix the database option in the PDB or the CDB
At first I thought my DB link might be pointing to wrong DB.
But then I found in the above error log it is showing as “DatabaseA 1 ERROR RESOLVED …… ”
So, I went into target container and could see resolved entries for DatabaseA and cleared those.
SELECT CON_ID, NAME, STATUS FROM PDB_PLUG_IN_VIOLATIONS WHERE STATUS = ‘RESOLVED’;
exec DBMS_PDB.CLEAR_PLUGIN_VIOLATIONS( pdb_name => ‘DatabaseA’ );
After that the fixup mode and deploy mode completed successfully.
Please notify the new posts
Please subscribe to the blog, and then you easily will be notified (which is not too often since I lack clearly time for blogging at the moment).
Cheers,
Mike
Hi Mike
I’m confused about the target_version parameter.
I’ve got an database running under 19.28c, nopdb.
The upgrade should run via DB Link later.
I setup the configfile like this:
global.global_log_dir=/home/oracle/patch/log
upg1.folder=/tmp
upg1.sid=DBR19
upg1.restoration=no
upg1.source_home=/u01/apps/oracle/product/19.28/home2
upg1.target_home=/tmp
upg1.target_version=23
If I run an analyze autoupgrade returns
The source database version 19 does not match the target_version configuration parameter 23 for prefix upg1.
Can You give me a helping hand?
Cheers
Christian
Hi Christian,
what are you trying to do here?
Install 26ai into the /tmp directory?
Or do you install already, and you want to do an upgrade?
A perfect companion is Marcus’ autoUpgrade composer – there you’ll click together your config file at speed of light:
https://viniciusdba.com.br/autoupgrade-composer/
Cheers,
Mike