The May 2025 version of AutoUpgrade (25.3) is available

Many of you know it and downloaded it already. But just in case you are not aware yet, let me give you a quick summary since the May 2025 version of AutoUpgrade (25.3) is available for download.

Photo by julien Tromeur on Unsplash

How to download it?

That’s very simple. You either download it via the well-known

• MOS Note: 2485457.1 – AutoUpgrade Tool

or you fetch it directly from oracle.com with curl, wget or by just clicking on the big button.

What’s new?

Well, 25.3 is a one-fix-only release, the real change was in 25.2 released a week or so before.

build.version 25.3.250509
build.date 2025/05/09 02:53:51 +0000
build.hash 3110a3d32
build.hash_date 2025/05/05 19:43:04 +0000
build.supported_target_versions 12.2,18,19,21,23
build.type production
build.label (HEAD, tag: v25.3, origin/stable_devel, stable_devel)
build.MOS_NOTE 2485457.1
build.MOS_LINK https://support.oracle.com/epmos/faces/DocumentDisplay?id=2485457.1

The only fix in 25.3 is:

BUG-37889660
AutoUpgrade fails with “OVERLAPPING RESOURCE FILE (LWC_FILE_EXISTS)” when non-English locale is used

But since it is cumulative, these are the improvements we released with 25.2.:

New Features

• AUPG-2531
  AutoUpgrade now supports resume from a specific upgrade phase for example
  java -jar autoupgrade.jar resume -job 100 -catctl_options=-p 0
  forces the resume to start at the beginning of upgrade
• AUPG-4275
  AutoUpgrade Patching – Allow create_home to be executed without a source home
• AUPG-4347
  AutoUpgrade Patching – Support for “patch=ocw” to patch OCW component in DB home
• BUG-37698373
  AutoUpgrade Patching – Support added for Oracle Key Vault Transparent Data Encryption (TDE)

Enhancements

• AUPG-4219
  AutoUpgrade Patching – Add option to ignore one-off conflicts
• AUPG-4337
  AutoUpgrade Patching – Better error message when there is a zip file that cannot be processed in the patch folder
• AUPG-4351
  AutoUpgrade Patching – Always print Root Script failure message
• AUPG-4378
  Create restoration_user.log file and point to it in status file
• AUPG-4564
  AutoUpgrade Patching – Copy opatch log files into logging directories

Change in behavior

• AUPG-4273
  Set or default compatible value with raise_compatible parameter
  The raise_compatible parameter can now apply a compatible parameter value
  For Example: raise_compatible=19.25.0
• AUPG-4353
  AutoUpgrade SC_CENTRAL_INVENTORY check fails with error when a symlink is specified on the config file as the source home.
• AUPG-4421
  CONSTRAINT_PRECHECK_UNMARKED check fixup changed from automatic to manual
• AUPG-4470
  AutoUpgrade Patching – Delay running root.sh until after all patches have been applied
• AUPG-4503
  AutoUpgrade Patching – Update OPATCH and PATCHING stage names
• AUPG-4517
  Change SC_CENTRAL_INVENTORY_SYMLINK check text message for better clarity

Added Checks

• None

Bugs fixed

• AUPG-1928
  ALTER DATABASE UPGRADE SYNC OFF causes replay to run traditional upgrade
• AUPG-3025
  Database fails to open in exclusive mode when resuming a distributed RAC in the PDBSUPG stage
• AUPG-3464
  AutoUpgrade cannot run load_win_credential after successful upgrade
• AUPG-4190
  AutoUpgrade Patching – fails if NLS_NUMERIC_CHARACTERS = “. “
• AUPG-4269
  AutoUpgrade Patching – clear_recovery_data was not deleting the state file causing analyze mode to fail
• AUPG-4295
  Update AutoUpgrade help message for -load_win_credential to SID
• AUPG-4300
  RTI-30742916 CheckForErrors incorrectly handles “SQL> ORA-32004: obsolete or deprecated parameter(s)”
• AUPG-4302
  MIGRATION_32K_NOT_COMPLETED Check With a runtime exception was not handling CDB$ROOT correctly
• AUPG-4306
  Upgrade from 19c non-CDB to 23ai CDB using autoupgrade fails wih an ORA-65019 we now handle this error and continue the AutoUpgrade processing
• AUPG-4349
  EMCLI modify_target command was not working because of incorrect command assembly
• AUPG-4369
  AutoUpgrade Patching – Fails to connect to database with “SET TIMING ON” in glogin.sql
• AUPG-4398
  Exception while copying sqlpatch_invocation.log due to a race condition
• AUPG-4448
  RTI 30684578 It was not possible to extract the Edition from Windows Registry when Windows Operating system is 64 bits and Java VM is 32 bits.
• AUPG-4512
  Invalid work option specified for distributed upgrades was not validated and defaulted to the entire container being upgraded
• AUPG-4525
  AutoUpgrade Patching – OPatch phase using wrong ORACLE_HOME and failing on Windows
• AUPG-4543
  Update password file pointer in srvctl during restoration
• BUG-37333230
  AutoUpgrade restore summary log has an incomplete upgrade log file path
• BUG-37580989
  Analyze failed on a non-CDB database where the database name and Oracle Sid values are different from the name returned from v$containers view. We now set the container name to match the Oracle Sid.
• BUG-37636475
  AutoUpgrade refreshable clone fails with error ORA-00922 while creating PDB.
• BUG-37549238
  DISK_SPACE_FOR_RECOVERY_AREA check failed with a runtime exception calling the kfod utility
• BUG-37570295
  Patching Error ORA-01034 Unexpected exception error occurred when validating a closed PDB
• BUG-37201065
  AutoUpgrade fails with [tde_passwords_required] error
• BUG-37285505
  Upgrading 19c RAC CDB database to 23ai, AutoUpgrade was unable to validate the remote nodes correctly
• BUG-37614308
  AutoUpgrade job hangs while upgrading container database with 50 pdbs using the tuning option distributed_upgrade

Quite am impressive list … so, 25.3 is the release to go with. And I am deeply impressed by the number of improvements the upgrade team has delivered in such a short time frame.

Further Links and Information

• MOS Note: 2485457.1 – AutoUpgrade Tool
• AutoUpgrade direct download link

–Mike