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 blog post as this is showcased in the documentation already:
Starting the database upgrade with DBUA
I will upgrade the UPGR database well known from our Hands-On Lab.
And please don’t put in your credentials in the fields below – if you are logged in as the oracle user then this will lead to failure and drive you crazy …
Another thing which puzzles me:
I still have to execute the olspreupgrade.sql script from the newer (in my case the 12.2) home by myself. I’d wish
the DBUA would do this for me as well as I’ll have to open an xterm, set my environment and type in a very long path name to point to the new 12.2 home in order to execute this script in my source environment.
Ok, let’s kick off the upgrade:
The progress bar is very imprecise in relation to the duration – you can ignore it more or less.
And – very sad – the Alert and Activity Monitor buttons disappeared – but they may reappear in a later release of the DBUA.
The Error Scenario
It’s always fun to kill pmon finding out how cool this database is 😉 It survives the deadly attack 🙂 Of course it does … it’s the Oracle Database 😉
The DBUA recognizes the failure
Even though the DBUA recognized the failure quite quickly it still tries to complete the upgrade – which of course results in a ton of errors. It just means that you’ll have to wait until the DBUA has “progressed” the upgrade till the end – and DON’T CLOSE THE DBUA as otherwise you’ll lose the ability to RETRY.
You’ll see the error count going up until the DBUA has reached the “end” of the (failed) upgrade.
And then it displays the RETRY button:
Rerun the Database Upgrade
Once you hit RETRY the DBUA will try to solve the situation – and in my case it will start up my source database in STARTUP UPGRADE mode again – and then process the upgrade using the -R option of catctl.pl (described in the previous blog post)
You’ll find also a new set of logfiles in $ORACLE_BASE/cfgtoollogs/dbua/ subdirectories indication with a number (here: 1) and an “R” that this is the first restart attempt’s logs: