Upgrading Exadata Databases

Note

This topic applies only to Exadata Cloud Service instances using the new resource model. For information on converting an Exadata DB system to the new resource model, see Switching an Exadata DB System to the New Resource Model and APIs.

This topic describes the procedures to upgrade an Exadata database instance to Oracle Database 19c (Long Term Release) by using the Console and the API. The upgrade is accomplished by moving the Exadata database to a Database Home that uses the target software version.

Prerequisites

The following are required in order to upgrade an Exadata Oracle Database instance:

  • The Exadata Cloud Service instance system software must use Oracle Linux 7 (OL7). See How to update the Exadata System Software (DomU) to 19 from 18 on the Exadata Cloud Service in OCI for instructions on manually updating the operating system.
  • The Oracle Grid Infrastructure must be version 19c. See Upgrading Exadata Grid Infrastructure for instructions on using the Oracle Cloud Infrastructure Console or API to upgrade Grid Infrastructure. If patches are available for your Grid Infrastructure, Oracle recommends applying them prior to performing a database upgrade.
  • You must have an available Oracle Database Home that uses the two most recent version of Oracle Database 19c available in Oracle Cloud Infrastructure. See To create a new Database Home in an existing Exadata Cloud Service instance for information on creating a Database Home. You can use Oracle-published software images or a custom database software image based on your patching requirements to create Database Homes.
  • You must ensure that all pluggable databases in the container database that is being upgraded can be opened. Pluggable databases that cannot be opened by the system during the upgrade can cause an upgrade failure.

Your Oracle database must be configured with the following settings in order to upgrade:

  • The database must be in archivelog mode
  • The database must have flashback enabled

See the Oracle Database documentation for your database's release version to learn more about these settings.

About Upgrading a Database

For database software version upgrades, note the following:

  • Database upgrades involve database downtime. Keep this in mind when scheduling your upgrade.
  • Oracle recommends that you back up your database and test the new software version on a test system or a cloned version of your database before you upgrade a production database. See To create an on-demand full backup of a database for information on creating an on-demand manual backup.
  • Oracle recommends running an upgrade precheck operation for your database prior to attempting an upgrade so that you can discover any issues that need mitigation prior to the time you plan to perform the upgrade. The precheck operation does not affect database availability and can be performed at any time that is convenient for you.
  • If your databases uses Data Guard, you will need to disable or remove the Data Guard association prior to upgrading.
  • An upgrade operation cannot take place while an automatic backup operation is underway. Before upgrading, Oracle recommends disabling automatic backups and performing a manual backup. See To configure automatic backups for a database and To create an on-demand full backup of a database for more information.
  • After upgrading, you cannot use automatic backups taken prior to the upgrade to restore the database to an earlier point in time.
  • If you are upgrading an database that uses version 11.2 software, the resulting version 19c database will be a non-container database (non-CDB).

How the Upgrade Operation Is Performed by the Database Service

During the upgrade process, the Database service does the following:

  • Executes an automatic precheck. This allows the system to identify issues needing mitigation and to stop the upgrade operation.
  • Sets a guaranteed restore point, enabling it to perform a flashback in the event of an upgrade failure.
  • Moves the database to a user-specified Oracle Database Home that uses the desired target software version.
  • Runs the Database Upgrade Assistant (DBUA) software to perform the upgrade.

Rolling Back an Unsuccessful Upgrade

If your upgrade does not complete successfully, you have the option of performing a rollback. Details about the failure are displayed on the Database Details page in the Console, allowing you to analyze and resolve the issues causing the failure. A rollback resets your database to the state prior to the upgrade. All changes to the database made during and after the upgrade will be lost. The rollback option is provided in a banner message displayed on the database details page of a database following an unsuccessful upgrade operation. See To roll back a failed database upgrade for more information.

After Your Upgrade Is Complete

After a successful upgrade, note the following:

  • Check that automatic backups are enabled for the database if you disabled them prior to upgrading. See To configure automatic backups for a database for more information.
  • Edit the Oracle Database COMPATIBLE parameter to reflect the new Oracle Database software version. See What Is Oracle Database Compatibility? for more information.
  • If your database uses a <database_name>.env file, ensure that the variables in the file have been updated to point to the 19c Database Home. These variables should be automatically updated during the upgrade process.
  • If you are upgrading a non-container database to Oracle Database version 19c, you can convert the database to a pluggable database after converting. See How to Convert Non-CDB to PDB (Doc ID 2288024.1) for instruction on converting your database to a pluggable database.
  • If your old Database Home is empty and will not be reused, you can remove it. See To delete a Database Home for more information.

Using the Console

You can use the Console to:

  • Upgrade you database
  • Roll back an unsuccessful upgrade
  • View the update history of a database that has been upgraded

Oracle recommends that you use the precheck action to ensure that your database has met the requirements for the upgrade operation.

To upgrade or precheck an Exadata database
  1. Open the navigation menu. Under Oracle Database, click Bare Metal, VM, and Exadata.
  2. Choose your Compartment.
  3. Under Exadata at Oracle Cloud, click Exadata VM Clusters. In the list of VM clusters, click the name of the VM cluster that contains the database you want to upgrade.

    Note

    If your database is in an Exadata Cloud Service instance that does not use the new Exadata resource model, you will need to swtich the instance to the new model before you can upgrade your database.
  4. In the list of databases on the details page of the VM cluster, click the name of the database you want to upgrade to view the Database Details page.
  5. Click More Actions, then Upgrade.
  6. In the Upgrade Database dialogue, select the following:

    • Oracle Database version: The drop-down selector lists only Oracle Database versions that are compatible with an upgrade from the current software version the database is using. The target software version must be higher than the database's current version.
    • Target Database Home: Select a Database Home for your database. The list of Database Homes is limited to those homes using the most recent versions of Oracle Database 19c software. Moving the database to the new Database Home results in the database being upgraded to the major release version and patching level of the new Database Home.

  7. Click one of the following:

    • Run Precheck: This option starts an upgrade precheck to identify any issues with your database that need mitigation before you perform an upgrade.
    • Upgrade Database: This option starts upgrade operation. Oracle recommends performing an upgrade only after you have performed a successful precheck on the database.
To roll back a failed database upgrade
  1. Open the navigation menu. Under Oracle Database, click Bare Metal, VM, and Exadata.
  2. Choose your Compartment.
  3. Under Exadata at Oracle Cloud, click Exadata VM Clusters. In the list of VM clusters, click the name of the VM cluster that contains the database with the failed upgrade.

  4. Find the database that was unsuccessfully upgraded, and click its name to display details about it. The database should display a banner at the top of the details page that includes a Rollback button and details about what issues caused the upgrade failure.
  5. Click Rollback. In the Confirm rollback dialog, confirm that you want to initiate a rollback to the previous Oracle Database version by clicking Rollback.
To view the upgrade history of a database
  1. Open the navigation menu. Under Oracle Database, click Bare Metal, VM, and Exadata.
  2. Choose your Compartment.
  3. Under Exadata at Oracle Cloud, click Exadata VM Clusters. In the list of VM clusters, click the name of the VM cluster that contains the database you want to upgrade.

    Note

    If your database is in an Exadata Cloud Service instance that does not use the new Exadata resource model, you will need to swtich the instance to the new model before you can upgrade your database.
  4. In the list of databases on the details page of the VM cluster, click the name of the database for which you want to view the upgrade history.
  5. On the Database Details page, under Database Version, click the View link that is displayed for databases that have been upgraded. This link does not appear for databases that have not been updated.

    The Updates History page is displayed. The table displayed on this page shows precheck and upgrade operations performed on the database.

Using the API

For information about using the API and signing requests, see REST APIs and Security Credentials. For information about SDKs, see Software Development Kits and Command Line Interface.

Use the following APIs to manage database upgrades:

For the complete list of APIs for the Database service, see Database Service API.

Note

When using the UpgradeDatabase API to upgrade an Exadata Cloud Service database, you must specify DB_HOME as the upgrade source.