Oracle Cloud Infrastructure Documentation

Patching and Updating an Exadata Cloud at Customer System

This topic describes the responsibilities and procedures for patching and updating various components in Exadata Cloud at Customer.

Note

For more guidance on achieving continuous service during patching operations, see the Continuous Availability white paper.

Patching Performed by Oracle

Oracle performs patches and updates to all of the Oracle-managed system components. This includes the physical compute nodes (Dom0), network switches, power distribution units (PDUs), integrated lights-out management (ILOM) interfaces, and the Exadata Storage Servers.

In all but rare exceptional circumstances, you receive advance communication about these updates to help you plan for them. If there are corresponding recommended updates for your compute node virtual machines (VMs), then Oracle provides notification about them.

Wherever possible, scheduled updates are performed in a manner that preserves service availability throughout the update process. However, there may be some noticeable impact on performance and throughput while individual system components are unavailable during the update process.

For example, Dom0 patching typically requires a reboot. In such cases, wherever possible, the compute nodes are rebooted in a rolling manner, one at a time, to ensure that the service remains available throughout the process. However, each compute node is unavailable for a short time while it reboots, and the overall service capacity diminishes accordingly. Also, if your applications cannot tolerate the reboots, you may need to take mitigating action. For example, you may need to shut down an application while Dom0 patching occurs.

Managing Oracle Database and Oracle Grid Infrastructure Patches

You are responsible for routine patching of the Oracle Database and Oracle Grid Infrastructure software. On Exadata Cloud at Customer, routine patching of the Oracle Database and Oracle Grid Infrastructure software is facilitated by using the dbaascli utility. The dbaascli utility provides a simple means for applying routine patches, which Oracle periodically loads on to the Cloud Control Plane servers.

The dbaascli utility is part of the cloud-specific tooling bundle that is included with Exadata Cloud at Customer. Therefore, before performing the following procedures, ensure that you have the latest version of the cloud-specific tooling on all of the compute nodes in the VM cluster. For more information, see Cloud Tooling Updates.

To list available patches
To check prerequisites before applying a patch
To apply a patch
To list applied patches
To roll back a patch

Manually Patching Oracle Database and Oracle Grid Infrastructure Software

In general, Oracle recommends that you use the facilities provided by Exadata Cloud at Customer to perform routine patching of Oracle Database and Oracle Grid Infrastructure software. However, you may need to manually patch the Oracle Database or Oracle Grid Infrastructure software in the following circumstances:

  • Oracle Java Virtual Machine (OJVM) Patching: Because they cannot be applied in a rolling fashion, patches for the Oracle Database OJVM component are not included in the routine patch sets for Exadata Cloud at Customer. If you need to apply patches to the OJVM component of Oracle Database, you must do so manually. See Oracle JavaVM Component Database PSU and RU (OJVM PSU and OJVM RU) Patches.
  • Daylight Savings Time (DST) Patching: Because they cannot be applied in a rolling fashion, patches for the Oracle Database DST definitions are not included in the routine patch sets for Exadata Cloud at Customer. If you need to apply patches to the Oracle Database DST definitions, you must do so manually. See Updated DST Transitions and New Time Zones in Oracle RDBMS and OJVM Time Zone File Patches.
  • Non-routine or One-off Patching: If you encounter a problem that requires a patch which is not included in any routine patch set, work with Oracle Support Services to identify and apply the appropriate patch.

For general information about patching Oracle Database, see "Patch Set Updates and Requirements for Upgrading Oracle Database" in the Oracle Database Upgrade Guide for Release 19,18, 12.2, 12.1, or 11.2.

Updating the Compute Node Operating System

You are responsible for managing patches and updates to the operating system environment on the compute node VMs. This section outlines the standard Exadata tools and techniques that you can use to update the operating system components on the Exadata Cloud at Customer compute nodes. For further information, see Updating Exadata Database Servers in the Oracle Exadata Database Machine Maintenance Guide.

Preparing for an OS update
To update the OS on all compute nodes of an Exadata Cloud at Customer system

Installing additional OS packages

You are permitted to install and update OS packages on Exadata Cloud at Customer as long as you do not modify the kernel or InfiniBand-specific packages. However, Oracle technical support, including installation, testing, certification and error resolution, does not apply to any non-Oracle software that you install.

Also, adding or updating packages may introduce problems when applying an Exadata software update because the additional software may add new dependencies that may interrupt an Exadata update. For this reason, minimal customization is recommended.

If you install additional packages, it is recommended that you have scripts to automate the removal and reinstallation of those packages. After an Exadata update, verify that the additional packages are still compatible and are still needed, before reinstalling them.

See also Installing, Updating, and Managing Non-Exadata Software in the Oracle Exadata Database Machine Maintenance Guide.

Cloud Tooling Updates

You are responsible for updating the cloud-specific tooling included on the Exadata Cloud at Customer compute nodes. You can update the cloud-specific tooling by downloading and applying a software package containing the updated tools as described in this section.

To check the installed cloud tooling release and check for updates
To update the cloud tooling