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

Oracle Database 18.3.0 Upgrade on premises

Oracle Database 18.3.0 Upgrade on premisesAs Oracle Database 18c is now available on Linux on premises, I blogged about the installation already. And the next logical step is the Oracle Database 18.3.0 Upgrade on premises. In this case I will show an upgrade on the command line from Oracle to Oracle 18.3.0. A DBUA upgrade will follow in a separate blog post later.

Oracle Database 18.3.0 Upgrade on premises

Before you can start with the upgrade, you may download the software first, and then install it:

If …

Continue reading...

Monitoring progress during upgrades

The parallel upgrade can resume once an upgrade has stopped for unexpected reasons. Before Oracle 12.2 you can restart it with the -p option specifying the phase it stopped. And since Oracle 12.2 you can only use the -R option to resume it. This blog post will give you a bit more insights in monitoring progress during upgrades.

Monitoring progress during upgrades

Monitoring progress during upgrades

I blogged about the resume options for a while ago:

But you may ask yourself: How does the tool know where to resume? And do you need …

Continue reading...

Can I restart a failed Multitenant Upgrade as well?

A while back I did blog about the new -R option of the parallel upgrade tool in Oracle Database 12.2.

And in case you will do a real Multitenant upgrade and fail – as it happened to me today due to “no space left on device” (no audit files could be written anymore) I tried the -R option as well based on Joe’s (our lead developer) recommendation:

$ $ORACLE_HOME/perl/bin/perl -n 6 -R -l /home/oracle/mike2 catupgrd.sql

Argument list for []
Run in                c = 0
Do not run in         
Continue reading...

Upgrade to Oracle Database 12.2 and Converting it into an 12.2 PDB (plugin)

2 customers requested a bit more explanation on how to:
Convert and Plugin an Oracle 12.1 non-CDB database into an Oracle 12.2 container database

Cool, I like that 🙂 I will do this right away and use the approach to Upgrade first, then Plugin afterwards.

Upgrading an Oracle database to Oracle

First the preupgrade.jar must be executed – please download always the most recent version from MOS Note:884522.1 as the version we publish is usually newer including important improvements (and fixes) than the version you’ll get with the release drop. We are working on including always the …

Continue reading...

Restarting a failed Database Upgrade with

What if …

What if a database upgrade fails in between? First of all you should have enabled one of the common protections for issues happening during an upgrade:

  • Guaranteed Restore Point to Flashback Database
  • Restore an RMAN Online Backup
  • Restore a partial Offline Backup

See our slide’s Fallback section for further details.

But actually there are ways to restart the upgrade without the need to fallback in case of a non-destructive incident such as running out of archivelog space.

Restart the Upgrade before Oracle Database 12c

Before Oracle Database 12c the most simple way to restart an upgrade was …

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

Don’t get puzzled by “sqlpatch” messages during Upgrade

During my last Hands-On-Labs in Uruguay and Argentina I’ve had several people wondering about these messages below when running the command line upgrade with - sqlpatch

This (and another) message breaks the nicely structured format of the output. And as it ends with an “err” extension it looks to many people as if the upgrade had gotten an error,

But please don’t feel disturbed. It’s just messages from sqlpatch invocation – and the “err” extension is just pointing to an error file in case something has gone wrong.

In a future release such messages …

Continue reading...

OOW2014 – Upgrade in a Multitenant Environment

On Sept 30, 2014 at Oracle OpenWorld, Joseph Errede gave his excellent talk about all the tech details in focusing on what happens when you upgrade a multitenant environment. The presentation is very technical explaining many of the switches of If you’d like to get the slides please find them either in the Slides Download Center to the right or directly via this link:


Continue reading...

How to SET TIMING ON for parallel upgrades to 12c?

This hack is not necessary anymore since Oracle Database as TIMING ON is the standard as well as ECHO ON. Please don’t edit catupses.sql by yourself.

Have you asked yourself how to get timings in an Oracle Database 12c upgrade for all statements?

When you run the parallel upgrade via, the parallel upgrade Perl driving script in Oracle Database 12c, you may also want to get timings written in your logfile during execution. As does not offer an option yet the best way to achieve this is to edit the catupses.sql script in $ORACLE/rdbms/admin as this …

Continue reading...