Updating the Cloud Tooling by Using the dbaascli Utility

You use the patch tools subcommand of the dbaascli utility to update the cloud tooling on database deployments hosting a single-instance database or an Oracle Data Guard configuration of single-instance databases.

Note:

When updating the cloud tooling on database deployments hosting a Data Guard configuration, you must perform the following steps on both nodes; that is, on the one hosting the primary database and on the one hosting the standby database.

Connect as the opc user to the compute node.

See Connecting to a Compute Node Through Secure Shell (SSH).
Start a root-user command shell:
```
$ sudo -s
#
```
Check whether any cloud tooling updates are available:
```
# dbaascli patch tools list
```
If you receive an error message stating that this option is not supported, the cloud tooling on the compute node is too old to support this method of updating cloud tooling. In this case, follow the instructions in I can’t use dbaascli to update my cloud tooling.

The patch tools list subcommand is not yet available on Oracle Cloud at Customer. Instead, you must use the dbaascli dbpatchm list_tools command.
In the command response, locate the patch ID of the cloud tooling update.

The patch ID is listed as the "Patchid" value. If multiple patches are listed, choose the latest one.

Check your current version of cloud tooling:

# rpm -qa | grep -i dbaastools
dbaastools-version_number-release_number

After confirming that the latest update is newer than your current version, download and apply the patch containing the latest cloud tooling update:
```
# dbaascli patch tools apply --patchid LATEST
```
Note: if you get a warning message indicating that this parameter is invalid, you can ignore the message.

The patch tools apply subcommand is not yet available on Oracle Cloud at Customer. Instead, you must use the dbaascli dbpatchm toolsinst command.

Reset the backup configuration:

# /var/opt/oracle/ocde/assistants/bkup/bkup

Exit the root-user command shell and disconnect from the compute node:
```
# exit
$ exit
```
If you are updating cloud tooling on a database deployment hosting a Data Guard configuration, repeat the preceding steps on the other compute node of the deployment.