AutoUpgrade

New AutoUpgrade Tool is available in March 2024

It has been a longer while – but the Upgrade Dev team worked very hard. And finally, the new AutoUpgrade Tool is available in March 2024. And it brings a ton of new enhancements and features. Some of them, for instance the windows services support, were awaited by you for a long time. Still, there’s much more to talk about.

 

Download the newest version of AutoUpgrade

As usual, you can download it from MOS Note:2485457.1 – Download AutoUpgrade. And when you check the version, you already find some of the new …

Continue reading...

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...

June 2023 version of AutoUpgrade is available

It’s time to exchange your AutoUpgrade tools with the most recent one when you plan to do upgrades or use it for patching already. The June 2023 version of AutoUpgrade is available for download from MOS Note:2485457.1. And in case you are still using DBUA for unknown reasons, please read this blog post, too.

Where to download?

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

June 2023 version of AutoUpgrade is available

What does this version improve?

New Features

  • BUG-34010941 – Incorparated the Health check package to identify database dictionary inconsistencies
Continue reading...

DBUA Deprecation and future Desupport in Oracle Database 23c

Daniel pointed me to Tim Hall’s blog post about deprecated and desupported features in Oracle Database 23c. And his first bullet point mentioned is the DBUA Deprecation and future Desupport in Oracle Database 23c. Since Daniel and I agree that this needs a bit more explanation, we would like to share more background information with you.

Deprecated vs Desupport?

At first, let me refresh an old topic. What does deprecated mean, and what is the difference to desupport? A long while ago I wrote this blog post about it, and nothing …

Continue reading...

Patching to Oracle 19.19.0 out-of-place with additional patches

From all my quarterly blog posts you know that I patch usually in-place for space and other reasons. And you may have similar reasons when you patch. But it is not ideal – and just speaking about risk and downtime, you should always patch out-of-place. So let me show you how Patching to Oracle 19.19.0 out-of-place with additional patches works.

What do I need?

Actually, this is not complicated at all. And if you never done it this way, give it a try now please.

  • Base release Oracle Database 19.3.0 image
  • opatch 37 from
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...

A new version of AutoUpgrade has been released

Yes, we did it again. A new version of AutoUpgrade has been released. With important fixes.

A new version of AutoUpgrade has been released

Download the May 2022 version

So it is time to update your AutoUpgrade and download the most recent version.

A new version of AutoUpgrade has been released

Changes / Fixes / Enhancements

As usual, we document the changes and fixes as well as the enhancements in the change log you’ll find in MOS.

At first, this is the new build:

build.version 22.3.220503
build.date 2022/05/03 11:55:20 -0400
build.hash 9e84e228
build.hash_date 2022/05/03 11:37:00 -0400
build.supported_target_versions 12.2,18,19,21
build.type production
20 bug fixes since v22.2 release
Tag: V22.3
Description: 
Continue reading...

AutoUpgrade 2.0 has been released – and got reuploaded

Many of you have used AutoUpgrade for your database upgrades already. Just a few days ago I received some almost enthusiastic comments which made me very very happy. And if you thought it can’t get any better, no worries: AutoUpgrade 2.0 has been released – and got reuploaded.

Why AutoUpgrade 2.0?

As you know, we don’t do marketing but just talk tech. But you may have also recognized that we slowed down in our agile release cycle for AutoUpgrade. The simple reason for this long period of silence was that we’ve had a …

Continue reading...

New AutoUpgrade version 20211115 (Nov 2021) available for download

Yesterday at DOAG conference I announced it already in our Upgrade and Migration Round Table – and just a few hours later my team mates made the New AutoUpgrade version 20211115 (Nov 2021) available for download.

How to download AutoUpgrade?

Always download the most recent version of AutoUpgrade via MOS Note: 2485457.1 – AutoUpgrade Tool.

Just click on this link in the MOS Note:AutoUpgrade Nov 2021

Why do you need a new version?

A good number of issues being logged to us via blogs, tweets, SRs and eMails can be solved with the current …

Continue reading...

Upgrading a non-CDB to Oracle Database 21c with AutoUpgrade

Yesterday I wrote about the installation of Oracle Database 21c on Linux. But today it is time for Upgrading to Oracle Database 21c with AutoUpgrade.

Upgrading a non-CDB to Oracle Database 21c with AutoUpgrade

Photo by Arjun MJ on Unsplash

AutoUpgrade

You may have heard it already from us and other colleagues, but we can’t repeat it often enough: There is only one recommended tool to upgrade your databases – and this is AutoUpgrade.

In my 21c home, I’m checking the deployed version of AutoUpgrade at first:

[CDB3] oracle@hol:/u01/app/oracle/product/21/rdbms/admin
$ java -jar autoupgrade.jar -version
build.hash 57ab246
build.version 21.1.3
build.date 2021/04/21 13:32:13
build.max_target_version 21
build.supported_target_versions 12.2,18,19,21
build.type production

Now please …

Continue reading...

New version of AutoUpgrade (21.2) is available for download

As we often tell you, our Upgrade Development team is working hard to ensure an agile release cycle for AutoUpgrade. And the New version of AutoUpgrade (21.2) is available for download.

How to download?

As usual, you can (and should) always download the most recent version of AutoUpgrade from this MOS Note: 2485457.1. Usually the tool gets refreshed every 6-8 weeks. And the version you will download is guaranteed newer than the one you could get on disk.

New version of AutoUpgrade (21.2) is available for download

The fact the tool has a 21c versioning does not affect 19c upgrades. There …

Continue reading...

Where are AutoUpgrade error codes documented?

I know, I didn’t blog for a while due to seminar preparations and holidays. But as I’m going through the open comments on the blog trying to answer them, I came across a question regarding the strange UPG error codes, AutoUpgrade is printing sometimes. And of course, where are AutoUpgrade error codes documented?

The UPG errors

Once AutoUpgrade hits an error condition, it prints an error code such as UPG-1400 or UPG-1303. And often, this error code is not very meaningful. In the comments section, somebody asked where to fine more information about these …

Continue reading...

Download the newest AutoUpgrade for 19c and 21c upgrades

It’s out now and available since yesterday: AutoUpgrade 21c. Download the newest AutoUpgrade for 19c and 21c upgrades with many new features and improvements.

Download it!

This is the current version of AutoUpgrade:

build.hash 8ee6880
build.version 21.1.1
build.date 2020/12/14 14:41:34
build.max_target_version 21
build.supported_target_versions 12.2,18,19,21
build.type production
48 bug fixes since v21.0.0 release
Tag: v21.1.1
Description: This is the release for 21.1.1 MOS only

As usual, download it please from:

What’s new?

  • Non-CDB to PDB Upgrades
    • AutoUpgrade can upgrade and convert a non-CDB to a PDB in a new
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...

When Fixed Object Stats Gathering takes very long during upgrade …

Over the past days I exchanged several emails with a very important customer regarding Fixed Objects Stats gathering in relation to database upgrade. The customer found out that it takes very long in their environment – over an hour to be precise. Relaxing on the weekend helped me a bit. And this morning, it dawned me that I’ve had two similar cases before already. Plus I didn’t blog about it yet. Now it’s time to tell you a little but about Unified Auditing and the situation when Fixed Object Stats Gathering takes very long during upgrade …

When Fixed Object Stats Gathering takes very long during upgrade ...

Photo by Ayse

Continue reading...

AutoUpgrade and the Partial Offline Backup Strategy

In our Fallback talk we promote a backup strategy for large DWHs and database which are on purpose in NOARCHIVELOG mode. But last week I learned that there is something important to know about AutoUpgrade and the Partial Offline Backup Strategy. Otherwise you may hit a

AutoUpgrade and the Partial Offline Backup Strategy

Photo by Esri Esri on Unsplash

pitfall.

 

Partial Offline Backup Strategy?

I won’t explain in all details what this is. If you’d like to read more, please find all the necessary information on my blog post from July 17, 2018:

with graphics included. In brief, you take …

Continue reading...

Oracle AutoUpgrade between two servers – and Plugin?

In my previous blog post I demonstrated how you can upgrade with AutoUpgrade between two servers. This a very typical scenario where you get new server, often also with a newer operating system version installed. But I was wondering if you can use Oracle AutoUpgrade between two servers – and Plugin?

AutoUpgrade between two servers

Please see my previous blog post about all the details:

Upgrade and Plugin?

At the end of it, I was curious if I couldn’t just plugin afterwards. But I …

Continue reading...

Oracle AutoUpgrade between two servers

I try to catch up with missing AutoUpgrade posts. And I should have written this one a while earlier ideally. Just yesterday a colleague asked me about it. So it’s time now to describe how to use Oracle AutoUpgrade between two servers.

Oracle AutoUpgrade between two servers

Photo by Alex Motoc on Unsplash

Documentation

The Oracle Database 19c Upgrade Guide has this section about the scenario:

And you see that it consists of 5 steps:

  1. Run the -mode analyze step on source server
  2. Run the -mode fixups step on source server
  3. Shutdown and
Continue reading...

Upgrade fails with ORA-20001 during datapatch run

I encountered this issue now multiple times in my own environment. And I searched MOS and tried different things. But I couldn’t solve it yet. My Upgrade fails with ORA-20001 during datapatch run – and I’d like to show you how to bring the upgrade to an successful end.

Upgrade fails with ORA-20001 during datapatch run

Photo by chuttersnap on Unsplash

It all starts with an upgrade

In my lab environment I upgrade two databases often in parallel. An 11.2.0.4 database and a 12.2.0.1. The 11.2.0.4 upgrades always flawless. But the 12.2.0.1 occasionally fails. This is the screen AutoUpgrade is showing me – but this is not …

Continue reading...

AutoUpgrade with Transparent Data Encryption (TDE)

I knew, one fine day I will have to dig into TDE. Resistance is futile. There were so many questions regarding AutoUpgrade with Transparent Data Encryption (TDE) in the past weeks and months. And the team is still working hard on a solution to make the non-CDB to PDB plugin flawless and automated for such cases. But I won’t cover the latter in this post here. I will solely focus on the database upgrade itself.

AutoUpgrade with Transparent Data Encryption (TDE)

Photo by Jason Dent on Unsplash

 

This blog post may not be up to date anymore since we introduced lots of automation to it

Continue reading...

How to skip a Fixup in AutoUpgrade

In this blog post I’d like to demonstrate how to skip a fixup in AutoUpgrade. This can be very useful in cases where you know that an issue may happen. Recently we saw several cases with unexpected long runtime for the gathering of fixed objects stats.

How to skip a Fixup in AutoUpgrade

Photo by Warren Wong on Unsplash

Analyze Mode

During the analyze phase, AutoUpgrade creates a <SID>_checklist.cfg file. You will find it in your job’s prechecks subdirectory, e.g.

/home/oracle/logs/DB12/100/prechecks

My SID is DB12, and 100 is the job number.

This is how the db12_checklist.cfg looks in my example:

[SID]          [DB12]
==========================================
[container]          [DB12]
Continue reading...

More information on AutoUpgrade’s TARGET_PDB_COPY_OPTION

A few weeks ago I blogged about the 3 new parameter options to plugin a non-CDB right after the upgrade and make it a PDB. As I explained, you must create the receiving CDB by yourself. But from your emails and comments, we realized that the examples in the documentation are not sufficient. Hence, today I’d like to give more information on AutoUpgrade’s TARGET_PDB_COPY_OPTION parameter.

What does this parameter do?

At first, this AutoUpgrade parameter (not an init.ora parameter!) is optional. If you don’t set it, the NOCOPY option will be used. Your …

Continue reading...

AutoUpgrade: Refresh Status Information automatically

I have heard and received this question several times. And I always pointed people to the status logs in AutoUpgrade’s logging directory. But I wasn’t aware how simple the monitoring can be. Kudos to my colleague Meir Burmanov from Oracle Israel for explaining me today how you can simply monitor AutoUpgrade: Refresh Status Information automatically. And as things progress quickly, and we have smart developers in the upgrade team, I had to refresh this blog post soon after. See below …

Like it – and it’s very simple

This won’t be a long …

Continue reading...

AutoUpgrade in trouble when you are short on RAM

Actually I blog about this topic for the simple reason that currently you won’t find helpful information in MyOracle Support. And I’ve seen this issue now twice in a row at Enterprise customers. You may see AutoUpgrade in trouble when you are short on RAM. During one of the restarts AutoUpgrade initiates you may get an ORA-600.

AutoUpgrade in trouble when you are short on RAM

Photo by Vadim Sadovski on Unsplash

What you may see

At first, the alert.log – and this is the strange pattern here – does not give you any indication about this ORA-600. You will find it only in the logs written by autoupgrade.jar:…

Continue reading...

AutoUpgrade and Plug In to a CDB – with a single command (and video)

I have to confess, this feature is out and available for quite a while. But only unofficially. AutoUpgrade can upgrade and plug in a non-CDB into a CDB. But it lacked flexibility. And we didn’t test it a lot. Hence, you could find it documented in our Hands-On Lab instructions. And we did this exercise with you already in our sold-out labs at OOW 2019 as well. But since a week and a bit, it is officially supported: AutoUpgrade and Plug In to a CDB – with a single command (and video).

AutoUpgrade and Plug In to a CDB - with a single command (and video)

Photo by William Daigneault on Unsplash

Create

Continue reading...