Patching Failures on Bare Metal and Virtual Machine DB Systems

Patching operations can fail for various reasons. Typically, an operation fails because a database node is down, there is insufficient space on the file system, or the database host cannot access the object store.

This topic includes information to help you determine the cause of the failure and fix the problem. The information is organized into several sections, based on the error condition. If you already know the cause, you can skip to the section with the suggested solution. Otherwise, use the procedure in Determining the Problem to get started.

Determining the Problem

In the Console, you can identify a failed patching operation by viewing the patch history of a DB system or an individual database. A patch that was not successfully applied displays a status of Failed and includes a brief description of the error that caused the failure. If the error message does not contain enough information to point you to a solution, you can use the database CLI and log files to gather more data. Then, refer to the applicable section in this topic for a solution.

To identify the root cause of the patching operation failure

Database Service Agent Issues

Your Oracle Cloud Infrastructure Database makes use of an agent framework to allow you to manage your database through the cloud platform.

Resolving Patching Failures Caused By a Stopped Agent

Occasionally you might need to restart the dcsagent program if it has the status of stop/waiting to resolve a patching failure.

To restart the database service agent

Resolving Patching Failures Caused By an Agent That Needs to Be Updated

Patching can also fail if your agent needs to be updated. The system gives the following error message for this failure:

Current DcsAgent version is less than or equal to minimum required version.

To resolve this issue, perform the steps in To have Oracle Support update the Oracle Cloud Infrastructure Database service agent.

To have Oracle Support update the Oracle Cloud Infrastructure Database service agent

Object Store Connectivity Issues

Oracle Cloud Infrastructure DB system and database patches are stored in Oracle Cloud Infrastructure Object Storage. Therefore, successful patching operations require connectivity between the DB system host and the Object Storage location from which the patches are downloaded.

To ensure your database host can connect to Oracle Cloud Infrastructure Object Storage

Host and Oracle Clusterware Issues

One or more of the following conditions on the database host can cause patching operations to fail:

Database Node Not Running During the Patching Operation

All nodes of the database must be active and running while a patching operation is in progress, whether you are patching the DB system or the database home. Use the Console to check that the status of each node is AVAILABLE, and start the node, if needed.

The File System Is Full

Patching operations require a minimum of 15 GB of free space in the /u01 directory on the host file system. Use the df -h command on the host to check the available space. If the file system has insufficient space, you can remove old log or trace files to free up space.

The Oracle Clusterware Is Not Running

Oracle Clusterware enables servers to communicate with each other so that they can function as a collective unit. The cluster software program must be up and running on the DB system for patching operations to complete. Occasionally you might need to restart the Oracle Clusterware to resolve a patching failure.

To restart the Oracle Clusterware

The Oracle Grid Infrastructure (GI) Is Not Updated

This problem occurs when you try to patch a database before you patch the DB system of that database. The error description indicates that the Oracle Grid Infrastructure must be updated first. To resolve this issue, patch the DB system to latest available version. After you patch the DB system, you can retry the database patching operation.

To get the current and latest-available GI versions for the DB system, use the following command:

dbcli describe-component

Database Issues

An improper database state can lead to patching failures.

Database Not Running During the Patching Operation

The database must be active and running for all of the patching tasks to complete. Otherwise, you must run the datapatch task manually.

To check that the database is active and running
To run the datapatch task

Obtaining Further Assistance

If you were unable to resolve the problem using the information in this topic, follow the procedures below to collect relevant database and diagnostic information. After you have collected this information, contact Oracle Support.

To collect diagnostic information regarding failed jobs
To collect DCS agent log files
To collect Oracle Grid Infrastructure and Database log files