8.5.8 Downloading and Distributing Exadata Database Server Updates

Each Exadata database server update is packaged as an compressed ISO image file and as a channel on the Oracle Unbreakable Linux Network (ULN). Oracle curates, tests, and certifies the packages in each release across the entire Exadata hardware and software stack. The Exadata ISO and ULN channel include only packages needed to run Exadata System Software and Oracle Database (including Oracle Grid Infrastructure).

You can utilize Exadata database server updates in the following ways:

  • Using a Local YUM Repository Mirror

    This method uses a YUM repository server to mirror the ULN channel for each Exadata database server software update. This approach is recommended when:

    • There is a large number of Exadata database servers to update.

    • You already have a YUM repository server in your network or the infrastructure exists for building a local ULN mirror on a separate Linux server.

    • The YUM repository server is accessible to all the Exadata database servers.

  • Using the ISO File as a YUM Repository

    This method uses a standard Web server to present the ISO file containing an Exadata database server software update as a YUM repository. This approach is recommended when:

    • There is a large number of Exadata database servers to update.

    • You don't already have a YUM repository server in your network and you don't want to build one.

    • You have a Web server on your network that is accessible to all the Exadata database servers.

  • Using the ISO File Directly

    This method uses the Exadata patchmgr utility to directly access the ISO file containing an Exadata database server software update.

    The main benefit of this approach is simplicity, as it only requires a copy of the ISO file on the server running the Exadata patchmgr utility. However, using this approach, the patchmgr utility must propagate the entire ISO file to every Exadata database server that is the target of the update. In contrast, patchmgr only propagates individual packages to the update targets when using other methods. Consequently, this approach requires additional free local storage space on every server being updated.

The following topics describe these methods in greater detail: