Configuring Automatic Cloud Tooling Updates

This topic does not apply to Oracle Cloud at Customer.

You can configure automatic cloud tooling updates for compute nodes hosting Oracle Database Cloud Service database deployments that use a single-instance database or an Oracle Data Guard configuration of single-instance databases.

An entry is added to the /etc/crontab file to regularly check for cloud tooling updates and apply new updates to the compute node when they become available.

Note:

Currently, automatic cloud tooling updates are not supported for Database Classic Cloud Service database deployments that use Oracle Real Application Clusters (RAC).

Here are the tasks for configuring automatic cloud tooling updates:

Enabling Automatic Cloud Tooling Updates

To enable automatic cloud tooling updates for a database deployment:

Connect as the opc user to the compute node.

For detailed instructions, see Connecting to a Compute Node Through Secure Shell (SSH).
Start a root-user command shell:
```
$ sudo -s
#
```
Enter the following command:
```
# dbaascli patch tools auto enable
```
Exit the root-user command shell and disconnect from the compute node:
```
# exit
$ exit
```
If you are enabling automatic cloud tooling updates for a database deployment hosting a Data Guard configuration, repeat the preceding steps on the other compute node of the deployment.

Disabling Automatic Cloud Tooling Updates

To disable automatic cloud tooling updates for a database deployment:

Connect to the compute node as the opc user.

For detailed instructions, see Connecting to a Compute Node Through Secure Shell (SSH).
Start a root-user command shell:
```
$ sudo -s
#
```
Enter the following command:
```
# dbaascli patch tools auto disable
```
Exit the root-user command shell and disconnect from the compute node:
```
# exit
$ exit
```
If you are disabling automatic cloud tooling updates for a database deployment hosting a Data Guard configuration, repeat the preceding steps on the other compute node of the deployment.

Checking the Status of Automatic Cloud Tooling Updates

To check whether automatic cloud tooling updates are enabled or disabled for a database deployment:

Connect as the opc user to the compute node.

For detailed instructions, see Connecting to a Compute Node Through Secure Shell (SSH).
Start a root-user command shell:
```
$ sudo -s
#
```
Enter the following command:
```
# dbaascli patch tools auto status
```
- If the command response includes “INFO: auto rpm update is enabled”, then automatic updates are enabled.
- If the command response includes “INFO: auto rpm update is disabled”, then automatic updates are disabled.
Exit the root-user command shell and disconnect from the compute node:
```
# exit
$ exit
```
If you are checking whether automatic cloud tooling updates are enabled or disabled for a database deployment hosting a Data Guard configuration, repeat the preceding steps on the other compute node of the deployment.

Performing On-Demand Cloud Tooling Updates

If you cannot wait for the next automatic cloud tooling update, you can perform an on-demand cloud tooling check and update. A check is performed to determine whether the latest available cloud tooling update is newer than the current version. If so, the update is downloaded and applied to the compute node.

Note:

In order to perform an on-demand cloud tooling update, automatic updates must be enabled for the compute node. See Enabling Automatic Cloud Tooling Updates.

To perform an on-demand cloud tooling update for a database deployment:

Connect as the opc user to the compute node.

For detailed instructions, see Connecting to a Compute Node Through Secure Shell (SSH).
Start a root-user command shell:
```
$ sudo -s
#
```
Perform an on-demand cloud tooling check and update:
```
# dbaascli patch tools auto execute
```
Exit the root-user command shell and disconnect from the compute node:
```
# exit
$ exit
```
If you are performing an on-demand cloud tooling update for a database deployment hosting a Data Guard configuration, repeat the preceding steps on the other compute node of the deployment.