autoupgrade.jar

September 2023 version of AutoUpgrade is available

It’s time again – and the new September 2023 version of AutoUpgrade is available for download to you.

Where to download it?

As usual, the MOS Note: 2485457.1 offers you access to the new release, and to the previous versions of the tool as well. This new version will show the following version information:

java -jar autoupgrade.jar -version

build.version 23.4.230921
build.date 2023/09/21 14:43:05 -0400
build.hash 165be072
build.hash_date 2023/09/21 13:05:52 -0400
build.supported_target_versions 12.2,18,19,21
build.type production
build.label (HEAD, tag: v23.4, origin/stable_devel, stable_devel)

This version will be also included in the Jan 2024 RU, 19.22.0, but not …

Continue reading...

March 2023 release of AutoUpgrade is available

It’s download time again. So please refresh the AutoUpgrade release you are using with the new one since the March 2023 release of AutoUpgrade is available now for download.

Where to download?

As usual, please download the newest version of AutoUpgrade via MOS Note:2485457.1 – Download AutoUpgrade.

March 2023 release of AutoUpgrade is available

 

What does this version improve?

A lot.

Really, a lot of things got improved.

You’ll find the change.log for tracking purposes at the bottom of the note. I’d wish everybody would do such a transparent change tracking as the AutoUpgrade team does. This makes …

Continue reading...

October 2020 Version of AutoUpgrade is available

The October 2020 Version of AutoUpgrade is available now for download since Friday last week. As usual, you can access it easily via MOS Note: 2485457.1 – AutoUpgrade Tool.

What’s new in the October 2020 version?

As usual you find the change.log at the end of MOS Note: 2485457.1 – AutoUpgrade Tool for the most recent Oracle Database upgrade tool. You will find the following fixes and enhancements:

  • Enahancements
    • BUG_31709141 Allow the job state to be reset when database is restored manually
  • Fixes
    • AUPG-1862 ORA-65173 occurs when running the fix for
Continue reading...

AutoUpgrade Tips: Running two (or more) sessions in parallel

Our intention with the AutoUpgrade as the single tool to upgrade your databases was initially: You have one big config file for your databases. And you will use this file to upgrade your databases unattended. Ideally you run an “analyze” at first, then you schedule a “deploy” for overnight or the next weekend or whenever it is convenient for you. But sometimes people have different needs. In this particular case several people asked whether you can run multiple AutoUpgrade tools in parallel on the same server. Hence, I’d like to explain the first of more AutoUpgrade …

Continue reading...

AutoUpgrade may fail when patch ID column is NULL

Monday morning – it’s time to write a new blog post. And actually I will set priorities based on what you reported to me in the past week. This way it may prevent others from hitting the same pitfall. The AutoUpgrade may fail when patch ID column is NULL in REGISTRY$HISTORY.

AutoUpgrade may fail when patch ID column is NULL

Photo by Etienne Boulanger on Unsplash

What is happening?

You start a database upgrade with autoupgrade. But the initial check will fail with a message like this:

AutoUpgrade tool launched with default options
There was an error initializing the patching information for entry upg2

The AutoUpgrade won’t kick …

Continue reading...