The October 2025 Release of AutoUpgrade (25.6) is available

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.

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