Oracle Cloud Infrastructure Documentation

Updating an Exadata DB System

This topic covers how to update the operating system and the tooling on the database server nodes (also known as "compute nodes") of an Exadata DB system. Review all of the information carefully before you begin the updates.

OS Updates

You update the operating systems of Exadata compute nodes by using the patchmgr tool. This utility manages the entire update of one or more compute nodes remotely, including running pre-reboot, reboot, and post-reboot steps. You can run the utility from either an Exadata compute node or a non-Exadata server running Oracle Linux. The server on which you run the utility is known as the "driving system." You cannot use the driving system to update itself. Therefore, if the driving system is one of the Exadata compute nodes on a system you are updating, you must run a separate operation on a different driving system to update that server.

The following two scenarios describe typical ways of performing the updates:

Scenario 1: Non-Exadata Driving System

The simplest way to run the update the Exadata system is to use a separate Oracle Linux server to update all Exadata compute nodes in the system.

Scenario 2: Exadata Node Driving System

You can use one Exadata compute node to drive the updates for the rest of the compute nodes in the system, and then use one of the updated nodes to drive the update on the original Exadata driver node.

For example: You are updating a half rack Exadata system, which has four compute nodes - node1, node2, node3, and node4. First, use node1 to drive the updates of node2, node3, and node4. Then, use node2 to drive the update of node1.

The driving system requires root user SSH access to each compute node the utility will update.

Preparing for the OS Updates

Warning

Do not install NetworkManager on the DB system. Installing this package and rebooting the system results in severe loss of access to the system.

  • Before you begin your updates, review Exadata Cloud Service Software Versions (Doc ID 2333222.1) to determine the latest software version and target version to use.
  • Some steps in the update process require you to specify a YUM repository. The YUM repository URL is:

    http://yum-<region_key>.oracle.com/repo/EngineeredSystems/exadata/dbserver/<latest_version>/base/x86_64.

    Region keys are three-letter abbreviations, for example PHX.

    You can run the following curl command to determine the latest version of the YUM repository for your DB system region:

    curl -s -X GET http://yum-<region_key>.oracle.com/repo/EngineeredSystems/exadata/dbserver/index.html |egrep "18.1."

    This example returns the most current version of the YUM repository for the us-phoenix-1:

    curl -s -X GET http://yum-phx.oracle.com/repo/EngineeredSystems/exadata/dbserver/index.html |egrep "18.1."
    <a href="18.1.4.0.0/">18.1.4.0.0/</a> 01-Mar-2018 03:36 -
  • To apply OS updates, the DB system's A virtual version of a traditional network—including CIDRs, subnets, route tables, and gateways—on which your instance runs. must be configured to allow access to the YUM repository. If you are using a service gateway instead of an internet gateway, see Known Issues.
To update the OS on all compute nodes of an Exadata DB system

Updating Tooling on an Exadata DB System

You can update the cloud-specific tooling included on an Exadata DB system compute node by downloading and applying an RPM file containing the latest version of the tools.

Note

Oracle highly recommends that you maintain the same version of cloud tooling across your Exadata DB system environment. Perform the following procedure on every compute node in the Exadata DB system.

Prerequisite

The compute nodes in the Exadata DB system must be configured to access the Oracle Cloud Infrastructure Object Storage service. For more information, see Configuring a Static Route for Accessing the Object Store.

Updating the Cloud Tooling on Each Compute Node

The method for updating the tooling depends on the tooling release that is currently installed on the compute node. Regardless of the method you use, be sure to repeat the update process on each compute node in the cluster.

To check the installed tooling release
To update the tooling if the release label is higher than 17430
To update the tooling if the release label is 17430 or lower