Set Up the Environment

Exadata Infrastructure patching with Fleet Maintenance is enabled by integrating Fleet Maintenance with the Fleet Patching and Provisioning (FPP) solution. Before you begin patching your Exadata fleet, provision and register the FPP server and client.

Topics

Prerequisites for Exadata Patching

Before provisioning and registering the FPP server and client, ensure that the following prerequisites are met:

Exadata patching is supported for Oracle Enterprise Manager 13c Release 5 Update 23 (13.5.0.23) and above.
To support Exadata patching, ensure that you have properly setup your infrastructure for Enterprise Manager. See Setting Up Your Infrastructure in Database Lifecycle Management Administrator's Guide.
Perform the Exadata Database Machine discovery prerequisites. See Prerequisites in Oracle Exadata Database Machine Getting Started Guide.
Review and download Exadata patches. See MOS Note 888828.1.
Unzip the Patch Manager zip file and copy the contents into Computenode(domU) image folder. This is only for Computenode(domU) patching.

The latest Patch Manager zip file can be obtained from 21634633.
FPP Server and Client must be version 19.23 or higher.

For more details for setting up and upgrading your FPP server, see Oracle Fleet Patching and Provisioning Administrator's Guide.

Supported Components

Exadata Patching with Fleet Maintenance supports patching multiple Exadata components and targets simultaneously. However, each patch operation must focus on a single component type such as hosts and storage servers.

Following is a list of supported Exadata types for patching:

Database Server Bare Metal
Kernel-based Virtual Machine (KVM) Guest
XEN DomU
Storage Server
InfiniBand (IB) Switch in a physical Exadata