Patching a DB System

This topic describes the procedures to patch bare metal and virtual machine DB systems and database homes by using the Console, the API, or the database CLI (dbcli Integration Cloud).


This topic is not applicable to Exadata DB systems. For information and instructions on patching Exadata DB systems, see Patching an Exadata DB System Manually.

The following DB system patches are currently available:

Version DB System Patch Database Patch April 2020, January 2020 April 2020, January 2020, October 2019, July 2019 April 2020, January 2020 April 2020, January 2020, October 2019, July 2019 April 2020, January 2020 April 2020, January 2020, October 2019, July 2019 April 2020, January 2020 April 2020, January 2020, October 2019, July 2019 Not applicable April 2020, January 2020, October 2019, July 2019

For information about operating system updates, see OS Updates.

Required IAM Policy

You must have the required type of access in a policy  to use Oracle Cloud Infrastructure, whether you're using the Console or the REST API with an SDK, CLI, or other tool. When running a command, if you see an error message that says you don’t have permission or are unauthorized, contact your administrator. Confirm 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 enables the specified group to do everything with databases and related Database resources.

If you're new to policies, see Getting Started with Policies and Common Policies. Details about writing policies for databases are located in Details for the Database Service.

About Patching DB Systems

Patching a DB system requires a reboot, which can take several minutes. To minimize the impact on users, run the patch at a time when the system has the fewest users. To avoid system interruption, consider implementing a high availability strategy such as Oracle Data Guard. For more information, see Using Oracle Data Guard with the Database CLI.

Oracle recommends that you back up your database and test the patch on a test system before you apply the patch. See Backing Up a Database for more information.

Always patch a DB system before you patch the databases within that system. The Console displays the latest DB system patch and the previous patch. You can use either of these patches, but we recommend using the latest patch when possible.


DB systems require access to the Oracle Cloud Infrastructure Object Storage service, including connectivity to the applicable Swift endpoint for Object Storage. We recommend using a service gateway with the VCN to enable this access. For more information, see these topics:


In addition to the prerequisites listed in this section, 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 to execute patching processes.
  • The Oracle Cluster ware is running on the DB system.
  • All DB system nodes are running.

See Patching Failures on Bare Metal and Virtual Machine DB Systems for details on problems that can result from not following these guidelines.

Using the Console

You can use the Console to:

  • View the patch history of a DB system or an individual database.
  • Apply patches
  • Monitor the status of an operation.

We recommend that you use the pre-check action to ensure that your DB system or database home has met the requirements for the patch you want to apply.

Patching a DB system

To patch a DB system.
To patch a database

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 like dbcli or the Patch utility.

To view the patch history of a DB system
To view the patch history of a 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 patching DB systems and databases.

DB systems:


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

Using the Database CLI

This topic explains how to use the command line interface on the DB system to patch a DB system. Patches are available from the Oracle Cloud Infrastructure Object Storage service. You use the DBCLI commands to download and apply patches to some or all components in your system.


To connect to the DB system via SSH, you need the path to private key associated with the public key used when the DB system was launched.

You also need the public or private IP address of the DB system. Use the private IP address to connect to the DB system from your on-premises network, or from within the virtual cloud network (VCN). This includes connecting from a host located on-premises connecting through a VPN or FastConnect to your VCN, or from another host in the same VCN. Use the DB System's public IP address to connect to the system from outside the cloud (with no VPN). You can find the IP addresses in the Oracle Cloud Infrastructure Console on the DB System Details page by clicking Nodes under the Resources list. The values are displayed in the Public IP Address and Private IP Address & DNS Name columns of the Nodes table.

To update the CLI with the latest commands
To check for installed and available patches
To patch server components
To patch database home components

Applying Interim Patches


This topic applies only to database homes in 1-node and 2-node RAC DB systems.

To apply an interim patch (previously known as a "one-off" patch) to fix a specific defect, follow the procedure in this section. Use the Opatch utility to apply an interim patch to a database home.

In the procedure example, the database home directory is /u02/app/oracle/product/ and the patch number is 26543344.

To apply an interim patch to a database home