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 catctl.pl in Oracle Database 12.2. Restarting a failed Database Upgrade with catctl.pl 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 catctl.pl developer) recommendation: $ $ORACLE_HOME/perl/bin/perl catctl.pl -n 6 -R -l /home/oracle/mike2 catupgrd.sql Argument list for [catctl.pl] Run in c = 0 Do not run in C =…

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: Restarting a failed Database Upgrade with catctl.pl 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 blog…

Restarting a failed Database Upgrade with catctl.pl

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…