Oracle Exadata Fleet Update: Automating Exadata Patching with Gold Images and Out-of-Place Updates

 TechVisions Technical Brief — Oracle Database Lifecycle

Oracle Exadata Fleet Update

Simplifying patching, upgrades, and software standardization across the entire Exadata estate at scale.

Author Syed Zaheer  |  Director, TechVisions  |  Cloud & Database Engineering
On-Premises  ·  Exadata Database Service  ·  Exadata Cloud@Customer

Table of Contents

1. 1. Introduction
2. 2. Understanding Exadata Fleet Update
3. 3. Why Traditional Exadata Patching Is Challenging
4. 4. Core Components & Architecture
5. 5. Supported Update Operations
6. 6. The End-to-End Workflow (with Real Output)
7. 7. Out-of-Place Patching Explained
8. 8. Security & Compliance Advantages
9. 9. Fleet Update vs Traditional Patching
10. 10. Best Practices
11. 11. Conclusion
12. 12. References

1. Introduction

Managing large-scale Oracle Exadata environments has always been a critical responsibility for database administrators and infrastructure teams. As organizations expand their database footprint across on-premises, cloud, and hybrid deployments, maintaining software consistency, applying security patches, and performing upgrades become increasingly complex.

Traditional patching approaches often require extensive planning, manual execution, maintenance windows, and significant operational effort. To address these challenges, Oracle introduced Exadata Fleet Update, a cloud-native lifecycle management service that automates patching, upgrades, and software standardization across Exadata environments.

This article explores Oracle Exadata Fleet Update — its architecture, capabilities, workflow, benefits, and best practices for enterprise deployments — and walks through a representative end-to-end maintenance cycle with realistic command output.

At a glance: Exadata Fleet Update provides Fleet Update (patch) and Upgrade capabilities for the full database stack, including Exadata Infrastructure, VM Cluster, Grid Infrastructure (GI), and Database (DB) components.

2. Understanding Exadata Fleet Update

Oracle Exadata Fleet Update is a centralized lifecycle management service designed to automate software maintenance across Exadata systems. The service leverages Oracle's proven Fleet Patching and Provisioning (FPP) technology and extends it with cloud-based orchestration, allowing administrators to manage hundreds — even thousands — of databases through a single control plane.

Rather than patching individual databases or clusters separately, administrators organize targets into logical groups and execute standardized maintenance operations across the entire fleet. The service is exposed through the OCI Console, a REST API, and the OCI CLI under the fleet-software-update command group — abbreviated as fsu in the command examples below.

3. Why Traditional Exadata Patching Is Challenging

Before appreciating the benefits of Fleet Update, it helps to examine the limitations of traditional maintenance approaches. As database fleets grow, these challenges significantly impact operational efficiency and increase security and compliance risk.

• Manual patch planning and execution
• Version inconsistencies across environments (configuration drift)
• Lengthy maintenance windows
• Increased risk of human error
• Complex, error-prone rollback procedures
• Difficulty tracking patch compliance
• High operational overhead for large deployments

Key Objectives of Fleet Update

Strategic goals behind the service design

Objective	What it delivers
Standardization	Ensures all systems adhere to approved software baselines.
Automation	Reduces manual intervention during patching and upgrades.
Scalability	Supports lifecycle management for large Exadata estates.
Risk Reduction	Uses automated validation and out-of-place methodologies.
Operational Efficiency	Enables centralized management through a single control plane.

4. Core Components & Architecture

Fleet Update is built around four primary constructs. Understanding how they fit together is key to designing an efficient maintenance strategy.

4.1 Collections

Collections are logical groups of targets that share similar maintenance requirements — for example: Production Databases, Development Databases, Data Warehouse Clusters, or Exadata Cloud@Customer systems. Administrators perform maintenance operations at the collection level instead of managing individual targets.

4.2 Gold Images

Gold Images serve as standardized software baselines. A Gold Image contains Oracle Database binaries, Grid Infrastructure binaries, required Release Updates (RUs), one-off patches, and configuration standards. The benefits are consistent software versions, faster deployment, reduced configuration drift, and easier compliance management.

4.3 Maintenance Cycles

Maintenance Cycles define the workflow for applying updates. A cycle typically moves through Precheck, Staging, Validation, Deployment, and Verification — ensuring updates are performed consistently across environments.

4.4 Work Requests

Every maintenance operation generates a Work Request. Administrators can monitor execution status, progress percentage, error messages, completion reports, and rollback activities — providing full visibility into update operations.

5. Supported Update Operations

Exadata Fleet Update supports a broad range of lifecycle management activities across the database stack.1

Database Patching

Apply Release Updates (RUs) across multiple databases simultaneously — quarterly RU deployment, security patch implementation, and one-off patch rollout.

Database Upgrades

Perform major version upgrades — for example Oracle Database 19c to 23ai. The service automates upgrade orchestration and validation.

Version note: Always confirm the currently supported source and target releases and certified upgrade paths in the official Oracle documentation before planning an upgrade, as the supported matrix evolves over time.1

Grid Infrastructure (GI) Updates

Manage Oracle Grid Infrastructure lifecycle operations including GI patching, GI upgrades, and cluster maintenance.

Exadata Guest OS & System Software

Automate operating system maintenance for Exadata database servers and update Exadata infrastructure components — storage servers, networking software, and the Exadata system software stack — for an improved security posture and consistent versions.

Full-Stack Maintenance

One of the most powerful capabilities is coordinated stack maintenance: Database Software, Grid Infrastructure, Guest OS, and Exadata System Software updated through a single unified process.

6. The End-to-End Workflow (with Real Output)

The update process follows a structured lifecycle. Below, each step is paired with a representative OCI CLI command and a SQL*Plus / shell output panel that illustrates what an administrator typically sees. Identifiers (OCIDs, names) are illustrative.

Step 1–2: Discover Targets & Create a Collection

Fleet Update identifies available Exadata resources, then resources are organized into a collection (a logical maintenance group).

oci-cli — Fleet Software Update

$ oci fsu fsu-collection create \
    --type DB --compartment-id $C \
    --display-name "PROD-DB-19c" \
    --source-major-version DB_19 \
    --fleet-discovery '{"strategy":"FILTERS","filters":[...]}'

Submitting work request...
{
  "data": {
    "display-name": "PROD-DB-19c",
    "id": "ocid1.fsucollection.oc1..aaaa...prod",
    "lifecycle-state": "ACTIVE",
    "target-count": 6
  }
}
Collection created. 6 targets discovered and added.

Step 3: Assess Drift & Create a Gold Image (Software Baseline)

First, inspect the current versions across the collection to quantify configuration drift, then register the approved software baseline as a Gold Image.

oci-cli — Drift check + Gold Image create

$ oci fsu fsu-collection list-targets \
    --fsu-collection-id $COL --query 'data[]."current-version"'

[ "19.20.0.0", "19.20.0.0", "19.18.0.0", "19.20.0.0", "19.18.0.0", "19.20.0.0" ]

Drift detected: 2 of 6 targets below baseline 19.20.0.0

$ oci fsu fsu-collection create-gold-image \
    --fsu-collection-id $COL \
    --target-db-software-image-id $IMG_19_26

Registering approved baseline...
{
  "gold-image-version": "19.26.0.0",
  "lifecycle-state": "ACTIVE"
}
Gold Image registered as the approved target baseline (19.26.0.0).

Step 4–5: Define the Maintenance Cycle & Run Prechecks

Specify the target collection, schedule, desired software image, and upgrade path. Fleet Update then validates system readiness, space availability, dependencies, and compatibility — surfacing issues before deployment begins.

FSU Cycle — STAGE: PRE_CHECK

$ oci fsu fsu-cycle list-stage-actions \
    --fsu-cycle-id $CYCLE

STAGE        STATUS        DETAILS
----------   -----------   -----------------------------------------
PRE_CHECK    SUCCEEDED     6/6 targets passed
  readiness  PASS          cluster + listener responsive
  space      PASS          /u01 free >= 15G on all nodes
  deps       PASS          opatch / patch conflicts: none
  compat     WARN          PRODDB05: stale stats — non-blocking

Precheck complete. Cycle ready for STAGE phase.

Step 6: Stage Software

Required binaries are copied and prepared on target systems. Staging happens ahead of time to minimize downtime during the deployment phase.

FSU Cycle — STAGE: STAGE

$ oci fsu fsu-action create --type STAGE --fsu-cycle-id $CYCLE

Work Request: ocid1.workrequest.oc1..aaaa...stage
[##########################] 100%  Staging new Oracle Home (out-of-place)
  -> /u01/app/oracle/product/19.26.0.0/dbhome_2   [staged]
Staged on 6/6 targets. No downtime incurred.

Step 7: Apply Updates

Fleet Update performs the maintenance operation, using out-of-place methodologies wherever possible to reduce risk and simplify rollback.

FSU Cycle — STAGE: APPLY

$ oci fsu fsu-action create --type APPLY --fsu-cycle-id $CYCLE

TARGET      ACTION              RESULT
---------   -----------------   ----------------------------
PRODDB01    move + datapatch    SUCCESS  19.20 -> 19.26
PRODDB02    move + datapatch    SUCCESS  19.20 -> 19.26
PRODDB03    move + datapatch    SUCCESS  19.20 -> 19.26
PRODDB04    move + datapatch    SUCCESS  19.18 -> 19.26
PRODDB05    move + datapatch    SUCCESS  19.18 -> 19.26
PRODDB06    move + datapatch    SUCCESS  19.20 -> 19.26

Apply complete: 6/6 databases switched to new Oracle Home.

Step 8: Validate Results

Post-update validation confirms services start successfully, cluster health remains intact, and software versions match expectations.

SQL*Plus — post-patch verification on PRODDB01

SQL> SELECT version, action, action_time FROM dba_registry_sqlpatch
     ORDER BY action_time DESC FETCH FIRST 1 ROWS ONLY;

VERSION           ACTION    ACTION_TIME
----------------  --------  -------------------------
19.26.0.0.0       APPLY     2026-06-09 02:14:55 [OK]

SQL> SELECT comp_id, status FROM dba_registry WHERE status != 'VALID';

no rows selected

$ srvctl status database -d PRODDB01
Instance PRODDB011 is running on node exadbn01  [OK]
Instance PRODDB012 is running on node exadbn02  [OK]

Step 9: Rollback if Necessary

If problems occur, administrators revert to the previous software state with minimal disruption — because the prior Oracle Home was preserved during the out-of-place apply.

FSU Cycle — STAGE: ROLLBACK

$ oci fsu fsu-action create --type ROLLBACK --fsu-cycle-id $CYCLE \
    --targets '["PRODDB05"]'

PRODDB05    switch home    ROLLED BACK  19.26 -> 19.18
  -> reverted to /u01/app/oracle/product/19.18.0.0/dbhome_1
Rollback complete in 00:01:48. Previous home intact, no restore needed.

7. Out-of-Place Patching Explained

A major differentiator of Fleet Update is its reliance on out-of-place patching. Instead of modifying the existing Oracle Home in place, the service creates a new Oracle Home, applies updates there, and switches databases over — preserving the previous environment.

The advantages of the out-of-place approach include faster rollback, reduced downtime, lower deployment risk, and better testing flexibility.

8. Security & Compliance Advantages

Organizations increasingly face strict compliance requirements. Fleet Update helps by enforcing approved software baselines, tracking patch deployment status, reducing security vulnerabilities, accelerating critical patch adoption, and providing audit visibility through Work Requests.

Regulated industries: This is particularly valuable for finance, healthcare, telecommunications, and government — where demonstrable, auditable patch compliance is a continuous obligation rather than a one-time event.

Cloud Deployment Coverage

• Exadata Database Service — automates database lifecycle management within Oracle Cloud Infrastructure (OCI).
• Exadata Cloud@Customer — provides cloud-based operational capabilities while maintaining data residency requirements.
• Hybrid environments — supports consistent maintenance practices across cloud and on-premises deployments.

9. Fleet Update vs Traditional Patching

Side-by-side comparison of maintenance approaches

Capability	Traditional Patching	Fleet Update
Management Scope	Individual systems	Entire fleet
Automation	Limited	Extensive
Standardization	Manual	Automated (Gold Images)
Rollback	Complex	Simplified (switch home)
Compliance Tracking	Manual	Centralized
Scalability	Moderate	Enterprise scale
Operational Effort	High	Reduced

10. Best Practices

1. Maintain standard Gold Images. Limit the number of image variations to control drift.
2. Use collection-based management. Group systems by business criticality and maintenance schedule.
3. Test before production. Validate updates in lower environments before broad deployment.
4. Automate maintenance windows. Schedule updates during approved periods.
5. Monitor work requests. Review execution logs and validation reports after every cycle.
6. Establish rollback procedures. Document the rollback process even when automation is available.

TechVisions field note: Treat the precheck stage as a non-negotiable gate. In our engagements, the majority of avoidable maintenance-window overruns trace back to skipped or rushed prechecks — not to the patch itself.

11. Conclusion

Oracle Exadata Fleet Update transforms how organizations manage database infrastructure by introducing automation, standardization, and scalability into the lifecycle management process. By leveraging collections, gold images, maintenance cycles, and out-of-place patching, enterprises can efficiently maintain large Exadata fleets while reducing downtime, operational complexity, and security risk.

For organizations running Oracle Exadata Database Service, Exadata Cloud@Customer, or large on-premises Exadata deployments, Fleet Update provides a modern, automated approach to patching and upgrade management that aligns with the demands of today's cloud-driven infrastructure landscape.

ZAHEER

Oracle Cloud Infrastructure · Cloud Database & Engineering · Technical Blog Series