Patching an Exadata Cloud Service Instance

This topic explains how to perform patching operations on Exadata Cloud Service resources by using the Console, API, or the CLI.

Tip

Oracle recommends patching databases by moving them to a Database Home that uses the target patching level. See To patch a database by moving it to another Database Home for instructions on this method of database patching.

For information and instructions on patching the system by using the dbaascli utility, see Patching an Exadata Cloud Service Instance Manually.

Required IAM Policy

To use Oracle Cloud Infrastructure, you must be granted security access in a policy  by an administrator. This access is required whether you're using the Console or the REST API with an SDK, CLI, or other tool. If you get a message that you don’t have permission or are unauthorized, verify with your administrator what type of access you have and which compartment  you should work in.

For administrators: The policy in Let database admins manage Oracle Cloud database systems lets the specified group do everything with databases and related Database resources.

If you're new to policies, see Getting Started with Policies and Common Policies. If you want to dig deeper into writing policies for databases, see Details for the Database Service.

About Patching Exadata Cloud Service Resources

Patching an Exadata Cloud Service instance updates the components on all the compute nodes in the instance. A VM cluster or DB system patch updates the Oracle Grid Infrastructure (GI) on the resource.

Note

The cloud Exadata resource model the instance is using determines whether you patch the Grid Infrastructure on a DB system resource or a cloud VM cluster resource. VM clusters are used by the new resource model. DB systems can be easily migrated to the new resource model with no system downtime.

A Database Home patch updates the Oracle Database software shared by the databases in that home. Thus, you patch a database by either moving it to a Database Home that has the correct patch version or you patch the Database Home the database is currently in.

Consider the following best practices:

  • Back up your databases before you apply any patches. For information about backing up the databases, see Managing Exadata Database Backups.
  • Patch a VM cluster or an Exadata DB system before you patch the Databases Homes and databases on that resource.
  • Before you apply any patch, run the precheck operation to ensure your VM cluster, Exadata DB system, or Database Home meets the requirements for that patch.
  • To patch a database to a version other than the database version of the current home, move the database to a Database Home running the target version. This technique requires less downtime and allows you to easily roll back the database to the previous version by moving it back to the old Database Home. See To patch a database by moving it to another Database Home.
  • For the Oracle Database and Oracle Grid Infrastructure major version releases available in Oracle Cloud Infrastructure, patches are provided for the current version plus the two most recent older versions (N through N - 2). For example, if an instance is using Oracle Database 19c, and the latest version of 19c offered is 19.8.0.0.0, patches are available for versions 19.8.0.0.0, 19.7.0.0 and 19.6.0.0.

Prerequisites

The Exadata Cloud Service instance requires access to the Oracle Cloud Infrastructure Object Storage service, including connectivity to the applicable Swift endpoint for Object Storage. Oracle recommends using a service gateway with the VCN to enable this access. For more information, see these topics:

Important

In addition to the prerequisites listed, ensure that the following conditions are met to avoid patching failures:

  • The /u01 directory on the database host file system has at least 15 GB of free space for the execution of patching processes.
  • The Oracle Clusterware is up and running on the Exadata Cloud Service instance.
  • All nodes of the instance are up and running.

Using the Console

You can use the Console to view the history of patch operations on Exadata Cloud Service instances, apply patches, and monitor the status of patch operations.

Patching Exadata Instances That Use the DB System Resource Model

The tasks in this section describe how to apply patches and monitor the status of patch operations on Exadata DB systems and their Database Homes.

To patch the Oracle Grid Infrastructure on an Exadata DB system
  1. Open the navigation menu. Under Oracle Database, click Bare Metal, VM, and Exadata.
  2. Choose your Compartment.
  3. In the list of DB systems, click the name of the Exadata DB system you want to patch to display the DB system details.
  4. Under DB System Version, click the View link beside the Latest Patch Available field.
  5. Review the list of available patches for the DB system.
  6. Click the Actions icon (three dots) for the patch you are interested in, and then click one of the following actions:

    • Run Precheck: Check for any prerequisites to make sure that the patch can be successfully applied.
    • Apply: Applies the selected patch. Oracle highly recommends that you run the precheck operation for a patch before you apply it.
  7. Confirm when prompted.

    The patch list displays the status of the operation. While a patch is being applied, the patch's status displays as Patching and the DB system's status displays as Updating. Lifecycle operations on the DB system and its resources might be temporarily unavailable. If patching completes successfully, the patch's status changes to Applied and the status of the DB system changes to Available. You can view more details about an individual patch operation by clicking Patch History.

To patch the Oracle Database software in a Database Home (DB system)
Note

This patching procedure updates the Oracle Database software for all databases located in the Database Home. To patch an individual database, you can move it to another Database Home that uses the desired Oracle Database software configuration.
  1. Open the navigation menu. Under Oracle Database, click Bare Metal, VM, and Exadata.
  2. Choose your Compartment.
  3. In the list of DB systems, click the name of the Exadata DB system with the Database Home you want to patch to display the DB system details.
  4. Under Resources, click Database Homes.
  5. Click the name of the Database Home you want to patch to display the Database Home details.
  6. Under Database Software Version, click View.
  7. Review the list of available patches for the Database Home.
  8. Click the Actions icon (three dots) for the patch you are interested in, and then click one of the following actions:

    • Precheck: Check for any prerequisites to make sure that the patch can be successfully applied.
    • Apply: Applies the selected patch. Oracle highly recommends that you run the precheck operation for a patch before you apply it.
  9. Confirm when prompted.

    The patch list displays the status of the operation. While a patch is being applied, the status of the patch displays as Patching and the status of the Database Home and the databases in it display as Updating. During the operation, each database in the home is stopped and then restarted. If patching completes successfully, the patch's status changes to Applied and the Database Home's status changes to Available. You can view more details about an individual patch operation by clicking Patch History.

Patching Exadata Instances That use the New Resource Model

The tasks in this section describe how to apply patches and monitor the status of patch operations on cloud VM clusters and their Database Homes.

To patch the Oracle Grid Infrastructure on an Exadata cloud VM cluster
  1. Open the navigation menu. Under Oracle Database, click Bare Metal, VM, and Exadata.
  2. Choose your Compartment.
  3. Click Exadata VM Clusters.
  4. In the list of cloud VM clusters, click the name of the cluster you want to patch to display the cluster details.
  5. Under Version, click the View Patches link beside the Updates Available field.
  6. Review the list of available patches for the cloud VM cluster.
  7. Click the Actions icon (three dots) for the patch you are interested in, and then click one of the following actions:

    • Run Precheck: Check for any prerequisites to make sure that the patch can be successfully applied.
    • Update Grid Infrastructure: Applies the selected patch. Oracle highly recommends that you run the precheck operation for a patch before you apply it.
  8. Confirm when prompted.

    The patch list displays the status of the operation. While a patch is being applied, the patch's status displays as Patching and the cloud VM cluster's status displays as Updating. Lifecycle operations on the cluster and its resources might be temporarily unavailable. If patching completes successfully, the patch's status changes to Applied and the status of the cluster changes to Available. You can view more details about an individual patch operation by clicking Update History.

To patch the Oracle Database software in a Database Home (cloud VM cluster)
Note

This patching procedure updates the Oracle Database software for all databases located in the Database Home. To patch an individual database, you can move it to another Database Home that uses the desired Oracle Database software configuration.
  1. Open the navigation menu. Under Oracle Database, click Bare Metal, VM, and Exadata.
  2. Choose your Compartment.
  3. Click Exadata VM Clusters.
  4. In the list of cloud VM clusters, click the name of the cluster you want to patch to display the cluster details.
  5. Under Resources, click Database Homes.
  6. Click the name of the Database Home you want to patch to display the Database Home details.
  7. Under Latest Patch Available, click View.
  8. Review the list of available patches for the Database Home.
  9. Click the Actions icon (three dots) for the patch you are interested in, and then click one of the following actions:

    • Precheck: Check for any prerequisites to make sure that the patch can be successfully applied.
    • Apply: Applies the selected patch. Oracle highly recommends that you run the precheck operation for a patch before you apply it.
  10. Confirm when prompted.

    The patch list displays the status of the operation. While a patch is being applied, the status of the patch displays as Patching and the status of the Database Home and the databases in it display as Updating. During the operation, each database in the home is stopped and then restarted. If patching completes successfully, the patch's status changes to Applied and the Database Home's status changes to Available. You can view more details about an individual patch operation by clicking Update History.

Patching Individual Oracle Databases in an Exadata Cloud Service Instance

This task explains how to patch a single Oracle Database in your Exadata Cloud Service instance by moving it to another Database Home. For information on patching Database Homes, see To patch the Oracle Database software in a Database Home (cloud VM cluster) and To patch the Oracle Database software in a Database Home (DB system).

To patch a database by moving it to another Database Home
  1. Open the navigation menu. Under Oracle Database, click Bare Metal, VM, and Exadata.
  2. Choose your Compartment.
  3. Navigate to the cloud VM cluster or DB system that contains the database you want to move.

    Cloud VM clusters (new resource model): 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 move.

    DB systems: Under Bare Metal, VM, and Exadata, click DB Systems. In the list of DB systems, click the name of the DB system that contains the database you want to move.

  4. In the list of databases on the details page of the VM cluster or DB system, click the name of the database you want to move to view the Database Details page.
  5. Click Move to Another Home.
  6. Select the target Database Home.
  7. Click Move Database.
  8. Confirm the move operation.

    The database will be stopped in the current home and then restarted in the destination home. While the database is being moved, the Database Home status displays as Moving Database. When the operation completes, Database Home is updated with the current home. If the operation is unsuccessful, the status of the database displays as Failed, and the Database Home field provides information about the reason for the failure.

Viewing Patch History

Each patch history entry represents an attempted patch operation and indicates whether the operation was successful or failed. You can retry a failed patch operation. Repeating an operation results in a new patch history entry.

Patch history views in the Console do not show patches that were applied by using command line tools such as dbaascli.

If your service instance uses the new resource model, the patch history available by navigating to the VM Cluster Details page. If your service instance uses the DB system resource model, the patch history is available by navigating to the DB System Details page.

To view the patch history of a cloud VM cluster
  1. Open the navigation menu. Under Oracle Database, click Bare Metal, VM, and Exadata.
  2. Choose your Compartment.
  3. Click Exadata VM Clusters.
  4. In the list of cloud VM clusters, click the name of the cluster you want to patch to display the cluster details.
  5. Under Version, click the View Patches link beside the Updates Available field.
  6. Click Update History.

    The Update History page displays the history of patch operations for that cloud VM cluster and for the Database Homes on that cloud VM cluster.

To view the patch history of a DB system
  1. Open the navigation menu. Under Oracle Database, click Bare Metal, VM, and Exadata.
  2. Choose your Compartment.
  3. In the list of DB systems, click the name of the Exadata DB system with the information you want to view to display the DB system details.
  4. Under DB System Version, click the View beside the Latest Patch Available field.
  5. Click Patch History.

    The Patch History page displays the history of patch operations for that DB system and for the Database Homes on that DB system.

To view the patch history of a Database Home
  1. Open the navigation menu. Under Oracle Database, click Bare Metal, VM, and Exadata.
  2. Choose your Compartment.
  3. Navigate to the cloud VM cluster or DB system that contains the Database Home.

    Cloud VM clusters (new resource model): Under Exadata at Oracle Cloud, click Exadata VM Clusters. In the list of VM clusters, find the VM cluster you want to access and click its highlighted name to view the details page for the cluster.

    DB systems: Under Bare Metal, VM, and Exadata, click DB Systems. In the list of DB systems, find the Exadata DB system you want to access, and then click its name to display details about it.

  4. Under Resources, click Database Homes.
  5. Click the name of the Database Home you want to view to display the Database Home details.
  6. Under Database Software Version, click View by the Latest Patch Available field.
  7. Click Patch History (DB systems) or Update History (cloud VM clusters).

    The history page displays the history of patch operations for that Database Home and for the cloud VM cluster or DB system to which it belongs.

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 these API operations to manage patching the following Exadata resources: cloud VM clusters, DB systems, databases, and Database Homes.

Cloud VM clusters (for systems using the new resource model):

DB systems:

Databases:

  • UpdateDatabase - Use this operation to patch a database by moving it to another Database Home

Database Homes:

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