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

ORA-1422 and ORA-6512 from SYS.DBMS_STATS in Post Upgrade

Ernst Leber sent me an email today. He hit an error at a customer upgrading to Oracle 19.9.0 on Exadata with AutoUpgrade. ORA-1422 and ORA-6512 from SYS.DBMS_STATS in Post Upgrade were signaled – and he better flashed back to the Guaranteed Restore Point. He found even a MOS note but still had questions. So time to blog about it in case you hit this error sequence as well.

What happens, and when does it happen?

At first, this is not an AutoUpgrade issue. You may see the same error stack in the post upgrade …

Continue reading...

Upgrade: What if your time zone in source is newer than in target?

Sometimes there is just a simple question at the beginning. Like Daniel and I discussed this morning. Does AutoUpgrade check if the time zone file in source is higher than in target? While we discussed this, I downloaded the patches already to try it out. And in addition, I could double-check whether the time zone patches for 19c are now RU-independent finally. But the question remains for Upgrade: What if your time zone in source is newer than in target?

Upgrade: What if your time zone in source is newer than in target?

Photo by Srikanta H. U on Unsplash

My intention wasn’t initially to write a longer blog post. But read below …

Continue reading...

ORA-1722 when upgrading to 19.4.0 or 19.5.0 on Windows

Oh boy – I try to avoid blogging about errors on a specific platform. But as this topic was brought to my attention now 3x in 2 weeks, I think I’ll send it out. And I hope you won’t hit this ORA-1722 when upgrading to 19.4.0 or 19.5.0 on Windows.

ORA-1722 when upgrading to 19.4.0 or 19.5.0 on Windows

What is failing?

The database upgrade only on the MS Windows platform fails when you attempt to upgrade to 19.4.0 or 19.5.0. This means, you downloaded and installed 19.3.0. And then you followed our advice and applied one of the most recent Release Update – ideally 19.5.0, the October …

Continue reading...

Fallback Strategy: Partial Offline Backup

Oh, I think it took us years to get rid of recommendations in MOS notes saying before this or that change you must take an offline backup. These recommendations dated back to times where not almost everybody was using RMAN for online backups. But the times have changed. Still, there are situations where the “Offline Backup” word can be mentioned. And in this blog post I will describe a Fallback Strategy: Partial Offline Backup.

Usage Scenario

This method will only protect you against failure during an upgrade.

First of all, Offline Backup sounds really brutal and old-fashioned. …

Continue reading...

Upgrade to Oracle Database 12.2 – New MOS Notes

Some very helpful MOS Notes got published regarding the upgrade to Oracle Database

Furthermore check regularly for Known Issues and Alerts – currently the note has no content but exists already:


Continue reading...

Restarting a failed Database Upgrade with DBUA 12.2

In my previous blog post I did showcase how to restart a failed database upgrade on the command line before Oracle Database 12c, with Oracle Database 12.1.0.x and with the new Oracle Database 12.2.0.x:

Here I’d like to show the new capability of the Database Upgrade Assistant (DBUA) to restart an upgrade, a functionality the DBUA was missing until now. Please note that you can always go back to the command line, no matter in which version you have used the DBUA.

I won’t describe an upgrade with the DBUA in this …

Continue reading...

Upgrades to Oracle Database (and Downgrades)

Oracle Database 12c Release 2 (12.2) is available now in the Oracle Cloud
in DBCS and ECS in both NAS and EMEA zones, as well as being available on Exadata Express Cloud Service. The Oracle Database 12.2 documentation should be published later today.

Just to note down, the versions supporting direct upgrade either with catctl.pl on the command line or with DBUA are:

  • Oracle Database
  • Oracle Database
  • Oracle Database
  • Oracle Database

Direct Upgrade to Oracle Database 12.2

No direct upgrades are supported from versions below Oracle Database

For versions older than Oracle Database other tools such as Data Pump or …

Continue reading...

DBUA and Read-Only Tablespaces – Things to Know II

Related Blog Posts:

Thanks to Rodolfo Baselli commenting on a previous blog post about the DBUA and Read-Only Tablespaces I dug a bit deeper and found out that “assuming silently” does not mean “works as intended“.

But one piece after another.

Rodolfo commented that if he

Continue reading...

DBUA and Read-Only Tablespaces – Things to Know – I

Related Blog Posts:

Some people prefer the manual upgrade on the command line, others prefer the graphical tool Database Upgrade Assistant (DBUA).

DBUA and Read-Only Tablespaces 

The DBUA offers you an option of setting your non-Oracle tablespaces read-only during the upgrade.

DBUA Read Only 1

What the option doesn’t tell you …

Continue reading...

No OS Authentication? datapatch will fail in every upgrade

Thanks to Daniel from SimCorp for bringing this to my attention:Patch
Actually, command line upgrades are affected as well, if you do not use OS authentication.
Apparently, datapatch is not able to execute in non-OS authentication mode.
See MOS note 1635007.1.


You are doing a command line upgrade to Oracle Database 12c with catctl.pl – and you don’t use OS authentication allowing connections with “/ as sysdba” then datapatch.pl won’t be able to execute the SPU/PSU/BP related SQL commands as it will fail to connect to your database with an ORA-1017 (invalid username/password) error.


Bug 18361221 …

Continue reading...

DBUA displays wrong RMAN backup for restore – Oracle

Related Blog Posts:

If you are using the Database Upgrade Assistant (DBUA) to upgrade your database to Oracle Database be aware when you choose to potentially restore your database from a existing backup in case of an error during the upgrade.

First of all I would always stop DBUA …

Continue reading...

DBUA 12c and “datapatch.pl” – things to know

For clarification:
The following blog post applies to upgrades to Oracle 12.1 done by DBUA only whenever a SPU/PSU/BP is installed into the 12.1 home prior to the upgrade (which I’d highly recommend as patching before upgrade saves you headache after upgrade!).

Update [Dec 10, 2015]:
The required patch is included in but not (Oct 2015) – it will be included in the (Jan 2016) and all following PSUs.

For Oracle Database 12.2 and newer please see:

Two customers independently reported last week that they have doubts on DBUA’s ability to apply the required SQL

Continue reading...

New MOS Notes on Database Upgrades for 12c with or without Oracle Multitenant

Please find some new MyOracle Support (MOS) Notes about Database Upgrades to Oracle Database 12c, with or without Oracle Multitenant:

Credits for the CDB/PDB Notes go to

Continue reading...

DBUA can ignore underscores with “keepHiddenParams”

Important Update (Aug 17, 2019):
This option does not exist since Oracle 18c anymore due to bug 26762080. Instead you could try to use dbua -initParam (just be aware that you can’t pass on an event with this option).


The Database Upgrade Assistant (DBUA) is the graphical tool to upgrade Oracle databases. And the DBUA removes underscore parameters by default from the SPFILE when upgrading a database. If you don’t want this, there’s a way to tell it how DBUA can ignore underscores with “keepHiddenParams”.

DBUA can ignore underscores with “keepHiddenParams”

The DBUA by default will remove all

Continue reading...