From the Provisioning Menu Select the Upgrade Database Option

From the Provisioning menu select the Upgrade Database option Select the target Oracle 12c home and enter the named credentials for the database set up earlier.

Validation of prerequisites is done automatically.

Note the options selected for the database upgrade.

We need to provide the degree of parallelism which will be used by the catctl.pl upgrade utility which is internally run to upgrade the database.

Also provide a location for the diagnostic destination and audit dump file destination.

We have chosen the option to disable archive logging for the duration of the upgrade as well as selected a number of post upgrade tasks which need to be run like upgrading the timezone data and gathering optimizer statistics.

An RMAN backup can be taken before the database upgrade commences or we can use an existing backup. If the database is running with flashback logging enabled we can specify a guaranteed restore point which the database can be flashed back to.

In this case we have got a warning about insufficient disk space available because although the mount point /u01 has adequate disk space, the value of the DB_RECOVERY_FILE_DEST_SIZE is not sufficient. It is set to 4 GB while the recommended value is 7.4 GB. We can connect to the database from another session and increase the DB_RECOVERY_FILE_DEST_SIZE to the recommended value. We can create a new listener or register the database with an existing Oracle 12c listener

Review the database upgrade and options chosen

If we click the Running link we can monitor the progress of the upgrade job. Click on the Oracle_Server.log link

Click on Results tab While the database upgrade is in progress we can see that the archive logging has been turned off for the database.

SQL> archive log list Database log mode No Archive Mode Automatic archival Disabled Archive destination USE_DB_RECOVERY_FILE_DEST Oldest online log sequence 28 Current log sequence 30

In this case the database upgrade and post-upgrade tasks has taken around 55 minutes and the status of all tasks shows Succeeded.

We can click on the Status link and get further details. For example click on Succeeded link in the step Post Configuration ….

No custom scripts to execute. Successfully deleted the temporary staging location(s). [/u01/app/oracle/dbupgrade_job_temp/0d9bd323bccf6407e0538a58f00a6e95] Oracle Home property for database target db11g updated to /u01/app/oracle/product/12.1.0/dbhome_1. Port property for database target db11g updated to 1521. Verifying connection to database target db11g using sysdba credentials. Connection to database target db11g using sysdba credentials successfully verified. Verifying connection to database target db11g using credentials of monitoring user. Connection to database target db11g using credentials of monitoring user dbsnmp successfully verified. Stopping blackout of target db11g. Blackout of target stopped. Successfully evaluated the Response metric for the database target db11g. Post configuration complete.

Verify that the database has been upgraded to 12.1.0.2 and is up and running