Patching an Exadata Cloud@Customer System

Learn how to perform patching operations on Exadata database compute nodes and Database Homes by using the Console, API, or the CLI.

For information and instructions on patching the system by using the dbaascli utility, see "Patching and Updating an Exadata Cloud@Customer System Manually".

Required IAM Policy for Patching an Exadata Cloud@Customer System

Review the identity access management (IAM) policy for Patching an Exadata Cloud@Customer System

A policy is an IAM document that specifies who has what type of access to your resources. It is used in different ways: to mean an individual statement written in the policy language; to mean a collection of statements in a single, named "policy" document (which has an Oracle Cloud ID (OCID) assigned to it); and to mean the overall body of policies your organization uses to control access to resources.

A compartment is a collection of related resources that can be accessed only by certain groups that have been given permission by an administrator in your organization.

To use Oracle Cloud Infrastructure, you must be given the required type of access in a policy written by an administrator, whether you're using the Console, or the REST API with a software development kit (SDK), a command-line interface (CLI), or some other tool. If you try to perform an action, and receive a message that you don’t have permission, or are unauthorized, then confirm with your administrator the type of access you've been granted, and which compartment you should work in.

For administrators: The policy in "Let database admins manage DB systems" lets the specified group do everything with databases, and related database resources.

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

About Patching VM Clusters and Database Homes

Patching an VM Clusters updates the components on all the compute nodes in that system. VM cluster patching updates the grid infrastructure (GI) and Database Home patching updates the Oracle Database software shared by the databases in that home.

Currently, the following patches are available:

Table 12-1 VM Cluster and Oracle Database patches

Version VM Cluster Patch Database Patch

19.0.0.0

April 2020, January 2020

April 2020, January 2020, October 2019, July 2019

18.0.0.0

April 2020, January 2020

April 2020, January 2020, October 2019, July 2019

12.2.0.1

April 2020, January 2020

April 2020, January 2020, October 2019, July 2019

12.1.0.2

April 2020, January 2020

April 2020, January 2020, October 2019, July 2019

11.2.0.4

Not applicable

April 2020, January 2020, October 2019, July 2019

Consider the following best practices:
  • Because patching a system requires a reboot, plan to run the operations at a time when they will have minimal impact on users.
  • Oracle recommends that you back up your databases before you apply any patches. For information about backing up the databases, see Managing Database Backup and Recovery on Exadata Cloud@Customer.
  • Your Oracle Grid Infrastructure must be at or higher version than the database version you want to patch to. This may require you to first patch a VM cluster before you patch the Databases Homes within that system.
  • 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. See Moving Databases to Another Home.

Prerequisites for Patching an Exadata Cloud@Customer System

Check and apply the latest Cloud patches that are dowloaded and made available by Oracle on the CPS host.

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 VM cluster.
  • All nodes of the VM cluster are up and running.

Using the Console for Patching an Exadata Cloud@Customer System

Learn how to use the console to view the history of patch operations on VM cluster and Database Homes, apply patches, and monitor the status of patch operations.

Oracle recommends that you use the precheck action to ensure your VM cluster or Database Home has met the requirements for the patch you want to apply.

Using the Console to Perform a Patch Operation on a VM Cluster

Learn to apply patches on a VM cluster.

  1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
    VM Clusters is selected by default.
  2. Choose your Compartment.
    A list of VM Clusters is displayed for the chosen Compartment.
  3. In the list of VM clusters, click the VM cluster on which you want to perform a patch operation.
  4. Under Oracle Grid Infrastructure Version, click View Patches.
  5. Review the scope:
    • VM Cluster: Automatically set to the context from which you have launched this page.
    • Database Home: Automatically set to the context from which you have launched this page. If you have not set the context, then select the Database Home first.
  6. Review the list of available patches for the 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. Oracle highly recommends that you run this operation before you apply a patch.
    • Apply Patch: Applies the selected patch.
  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 VM cluster's status displays as Updating. Lifecycle operations on the VM clusterand its resources might be temporarily unavailable. If patching completes successfully, the patch's status changes to Applied and the VM cluster's status changes to Available. You can view more details about an individual patch operation by clicking Patch History.

Using the Console to Perform a Patch Operation on a Database Home

Learn to apply patches on a Database Home.

  1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
    VM Clusters is selected by default.
  2. Choose your Compartment.
    A list of VM Clusters is displayed for the chosen Compartment.
  3. In the list of VM clusters, click the VM cluster where the Database Home is located.
  4. Under Resources, click Database Homes.
  5. In the list of Database Homes, click the Database Home on which you want to perform a patch operation.
  6. Under Database Software Version, click View Patches.
  7. Review the scope:
    • Database Home: Automatically set to the context from which you have launched this page.
  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:
    • Run Precheck: Check for any prerequisites to make sure that the patch can be successfully applied. Oracle highly recommends that you run this operation before you apply a patch.
    • Apply Patch: Applies the selected patch.
  10. 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 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.

Using the Console to View 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.

Using the Console to View the Patch History of a VM Cluster

Learn how to view the history of patches applied on a VM cluster.

  1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
    VM Clusters is selected by default.
  2. Choose your Compartment.
    A list of VM Clusters is displayed for the chosen Compartment.
  3. In the list of VM clusters, click the VM cluster you are interested in.
  4. Under Oracle Grid Infrastructure Version, click View Patches.
  5. Click Patch History.

The history of patch operations for that VM cluster is displayed, along with the history of patch operations on its Database Homes.

Using the Console to View the Patch History of a Database Home

Learn how to view the history of patches applied on a Database Home.

  1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
    VM Clusters is selected by default.
  2. Choose your Compartment.
    A list of VM Clusters is displayed for the chosen Compartment.
  3. In the list of VM clusters, click the VM cluster where the Database Home is located.
  4. Under Resources, click Database Homes.
    A list of Database Homes is displayed.
  5. In the list of Database Homes, click the Database Home you are interested in.
  6. Under Database Software Version, click View Patches.
  7. Click Patch History.

The history of patch operations for that Database Home is displayed, along with the history of patch operations on the VM cluster to which it belongs.

Using the Console to Move a Database to Another Home

You can update the version of a VM cluster database by moving it to a Database Home that is running the version of Oracle Database you are interested in.

  1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
    VM Clusters is selected by default.
  2. Choose your Compartment.
    A list of VM Clusters is displayed for the chosen Compartment.
  3. In the list of VM clusters, click the VM cluster where the database you want to move is located.
  4. Under Resources, click Database Homes.
  5. In the list of Database Homes, click the Database Home you are interested in.
    A list of databases is displayed.
  6. In the list of databases, click the database you are interested in.
  7. Go to Actions, and then click Move to Another Home.
  8. Select the target Database Home.
  9. Click Move Database.
    The database will be stopped in the current home and then restarted in the destination home.
  10. 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.

Using the API for Patching an Exadata Cloud@Customer System

Use various API features to help manage patching an Oracle Exadata Cloud@Customer system.

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 VM clusters and Database Homes.

VM cluster:

  • UpdateVmCluster

Database Homes:

  • CreateDbHome
  • UpdateDbHome
  • DeleteDbHome

Database:

  • CreateDatabase
  • UpdateDatabase
  • DeleteDatabase

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