Sometimes also the best tools do have some little bug, even if it is typically bullet proof.
The issue today is with autoupgrade tool build version 26.3.260401 from April 2026. If you need to check your version just use
java -jar autoupgrade.jar -version
and you can see your version, build date, etc..
If you try to analyze or patch your existing environment with
java -jar autoupgrade.jar -patch -config <myconfig.cfg> -analyze
java -jar autoupgrade.jar -patch -config <myconfig.cfg> -deploy
you will get an error that in the patch directory nothing newer is found.
If you look into your autoupgrade error log for this patch job, you will find the following messages (followed by a java call error stack):
*Validating Oracle Patch files
An Oracle newer Release Update file for database is not found in <patch-directory> for the job with prefix <patch1>
- Bootstrap.processCLIParams#83
oracle.commonx.utils.errors.ConfigurationError:
There were conditions found preventing AutoUpgrade Patching from successfully running
*Validating Oracle Patch files
An Oracle newer Release Update file for database is not found in <patch-directory> for the job with prefix <patch1>
Unfortunately, the previous 26 version of the autoupgrade tool throws the same error. If you want to step back to the last autoupgrade versions 25 - this will not work. They will all throw the same message:
AutoUpgrade Patching has derived the version for prefix <patch1> as [23.26.1.0.0].
AutoUpgrade Patching currently only supports the following major versions:
[19].
The bug is known to Oracle and they will fix it. I think the next version will follow soon (as the last one is from April 2026), maybe in the next days.
Until then, as a workaround, you need to download the patches first (you can use analyze mode until it throws the error or the download mode).
If the patches are available in the staging directory you must create the new home first:
java -jar autoupgrade.jar -patch -config myconfig.cfg -mode create_home
Afterwards, analyze the source database, run the fixups and deploy (without -patch):
java -jar autoupgrade.jar -config myconfig.cfg -mode analyze
java -jar autoupgrade.jar -config myconfig.cfg -mode fixups
java -jar autoupgrade.jar -config myconfig.cfg -mode deploy
This should do it.
I will update the post as soon as the new autoupgrade version is available.
