Our developers are amazing. And you may have felt this the past months. In September for OCW2024 we released AutoUpgrade 24.6 with the new patching ability, in October we then released 24.7 improving it significantly and fixing issues based on the first tests, and now in November 2024 AutoUpgrade 24.8 has been released adding MS Windows patching support. Of course, there’s more in AutoUpgrade.
How to download AutoUpgrade 24.8
Not only can you download the newest AutoUpgrade and its previous versions from MOS Note:2485457.1 – Download AutoUpgrade but as I wrote a few days ago, it is available now directly from oracle.com via curl or wget.
You have the choice – but please allow us a few days until the version on oracle.com is in synch with the MOS note since this is a manual process we can’t automate for each new AutoUpgrade version. Hence, you may want to do a quick check after you downloaded it.
java -jar autoupgrade.jar -version build.version 24.8.241119 build.date 2024/11/19 12:49:28 -0500 build.hash b404cf007 build.hash_date 2024/11/18 14:39:19 -0500 build.supported_target_versions 12.2,18,19,21,23 build.type production build.label (HEAD, tag: v24.8, origin/stable_devel, stable_devel) build.MOS_NOTE 2485457.1 build.MOS_LINK https://support.oracle.com/epmos/faces/DocumentDisplay?id=2485457.1
The above is from the version from MOS while the version on oracle.com still gives 24.7 until the mirroring to the external page has been completed.
What’s new?
At first, the most important new feature is the support to download patches and build a new home on MS Windows. This is massive as Daniel and I can tell. When we did ask you in our patching talk at DOAG 2024 Conference in Nürnberg last week, out of the 180 people in Tokio on Thursday, almost one third raised their hands when we did ask who’s running Oracle on Windows.
Now there is relief – and please, try it out.
Always refer to the change.log at the bottom of the MOS Note:2485457.1 – Download AutoUpgrade.
New Features
None
Enhancements
- AUPG-3554 – Add optional post upgrade operation for AutoUpgrade to automatically change an OEM client monitored Database to the new target home
- AUPG-3964 – Improve help output for AutoUpgrade
- AUPG-4032 – After a successful hot cloning/relocate migration optionally remove the database link
- AUPG-4051 – Add message when AutoUpgrade fails to display how to zip up the log files
- AUPG-4087 – AutoUpgrade Patching added support for Windows 64 bits
- AUPG-4112 – AutoUpgrade Patching change config file detection behavior when invoking patching when the global.global_log_dir parameter was used
- AUPG-4123 – Rename stage from “AUTOUPGRADE” to “PATCHING”
Change in behavior
None
Added Checks
None
Issues Fixed
- AUPG-4109 – AutoUpgrade does not detect pdb upgrades are not performed
- AUPG-4030 – Avoid starting the database with a pfile when spfile has already been created during RU patching operation
- AUPG-4094 – Restoration is not supported for unplug-plug-relocate operation
- AUPG-4095 – AUDTAB_ENC_TS check was revised to be more accurate
- AUPG-4101 – Improved error message for conflicting patches
- AUPG-4102 – load_password prompts twice for keystore password
- AUPG-4122 – AutoUpgrade throws an exception when the LANG variable is set to pt_BR.UTF-8
- AUPG-4124 – AutoUpgrade Patching supports AP_OPATCH_PREREQ check on Windows
- AUPG-4134 – AutoUpgrade Patching failed to clone OS groups from the source home during create_home phase
- AUPG-4136 – AutoUpgrade Patching disregarded runInstaller warnings from missing target prerequisites
- AUPG-4141 – AutoUpgrade Patching Unhandled exception patch=recommended in lowercase
- AUPG-4147 – No exception raised when previous jobs are unable to be restored
- AUPG-4167 – java.lang.IndexOutOfBoundsException in SteadyData on AIX platform
- BUG-37068257 – Missing oracle\lib path on HP_UNIX for LD_LIBRARY_PATH
Kudos to the super-amazing Oracle Database Upgrade Development team!!
Further Links and Information
- MOS Note:2485457.1 – Download AutoUpgrade
- Download AutoUpgrade directly from oracle.com
- www.oracle.com/goto/upgrade
- AutoUpgrade Patching – The Feature you waited for
- Virtual Classroom Seminar 21: One-Button Patching
–Mike
Please don’t forget AIX compatibility.
Hi Edgar,
no worries, we are working on it.
Cheers,
Mike
Hi Mike,
Seems I have questions on every version, sorry about that. I upgraded to 24.8 and I can analyze and deploy, however if I try and do a patch it fails with:
AutoUpgrade Patching has derived the version for prefix upg1 as [23.5.0.24.07]. AutoUpgrade Patching currently only supports the following major versions: [19].
Do you have any idea when this functionality will be available on 23ai? It is really an awesome feature I am trying to test.
Thanks!
Chris
Hi Chris,
this is correct (unfortunately). We offer this functionality for 23ai as soon as 23ai will be available on-prem generally. As you may know, right now it is only available for Engineered Systems and in the cloud – and of course as the Free Developer edition.
Cheers,
Mike
Hi Mike,
great thing.
But we have Windows and Linux DB servers, but only Windows clients with Internet access. How can I now download Linux patches under Windows?
Thanks
Jürgen
Hi Juergen,
not in the docu but already in the 24.8 version of AU:
patch1.platform=
is the parameter, and currently it accepts values: linux.x64, windows.x64
Therefore, please add:
patch1.platform=linux.x64
when you want to download Linux patches on a Windows machine.
With the AU 25.1 version it will support then:
aix.x64, arm.x64, linux.x64, solaris.x64, sparc.x64, windows.x64
Cheers,
Mike
Hi Mike
Great that autoupgrade runs on Windows now.
Just one question.
If I use the “-load_win_credential” function I’m asked for user and password.
(The user for the oracle service)
Can I use an domain user,too?
Cheers
Christian
Hi Christian,
yes.
See here:
global.keystore=c:\oracle\autoupgrade\keystore
patch1.source_home=c:\oracle\product\dbhome_19_29_0
patch1.target_home=c:\oracle\product\dbhome_19_30_0
patch1.sid=DB19
patch1.folder=c:\oracle\patches
patch1.patch=RECOMMENDED
patch1.wincredential=c:\oracle\autoupgrade\credential
Then for patching for instance:
java -jar autoupgrade.jar
-config patch_on_win.cfg
–patch
-loadwincredential “DB19”
C:\> java -jar autoupgrade.jar
-config patch_on_win.cfg
–patch
-mode deploy
And yes, you can pass on your domain credentials. It must be the user who runs the Oracle service, for instance “Mike_Windows_Box\OurDomain” then with the PW.
Cheers,
Mike