Oracle Cloud Infrastructure offers several services for patching and lifecycle operations, but they are not interchangeable. Choosing the right tool depends on what you are patching: Exadata infrastructure, a standard Base Database Service system, an external database, or a broader application stack.
This guide clarifies when to use Exadata Fleet Update, OCI Database Management, Base Database Service update workflows, also Important notes on Fleet Application Management.
1. Exadata Fleet Update: Best for Exadata Stack Maintenance
Use Exadata Fleet Update, or EFU, when you need to patch or upgrade Exadata database stack components. EFU is providing fleet update and upgrade capabilities for the Exadata database stack, including Exadata Infrastructure, VM Cluster, Grid Infrastructure, and Database components.
EFU is the right choice for Exadata environments because it is built for fleet-level maintenance and understands Exadata-specific lifecycle operations. It helps automate patching across multiple Exadata targets, run prechecks, stage updates, apply patches, and manage maintenance cycles with less custom scripting.
Use EFU for:
| Scenario | Recommended Tool |
| Exa Infrastructure patching | Exadata Fleet Update |
| VM Cluster maintenance | Exadata Fleet Update |
| Grid Infrastructure updates on Exa | Exadata Fleet Update |
| Database software updates on Exa | Exadata Fleet Update |
| Fleet-level Exa systems orchestration | Exadata Fleet Update |
EFU is not a general-purpose application patching tool. It should be used when the target is part of a supported Exadata database stack.
2. OCI Database Management: Best for Database Visibility and Supported External DB Patching
OCI Database Management is primarily a database observability, diagnostics, performance, and management service. It is useful for monitoring database health, reviewing performance, analyzing workloads, and managing database fleets.
Database Management also includes Vulnerability Detection and Patching, but this feature has a specific scope. It currently supports External Databases running on-premises or OCI Virtual Machines on Linux.
Use OCI Database Management for:
| Scenario | Recommended Tool |
| Database monitoring | OCI Database Management |
| Performance analysis | OCI Database Management |
| Database fleet visibility | OCI Database Management |
| CVE insight for supported external databases | OCI Database Management |
| Patching supported external databases | OCI Database Management Vulnerability Detection and Patching |
Database Management may not be treated the default native patching tool for all OCI databases. For native OCI Base Database Service systems, use the Base Database Service update workflows instead.
3. Base Database Service Updates: Best for Standard OCI DB Systems
For standard OCI Base Database Service environments, use the native Base Database Service update workflows. Oracle documents separate update procedures for DB system updates, Database Home updates, and database updates using the Console and API.
You can also use dbcli for supported DB system resource updates, including DB system, operating system, and Database Home updates.
Use Base Database Service updates for:
| Scenario | Recommended Tool |
| Standard OCI VM DB system update | Base Database Service update workflow |
| Database Home update | Base Database Service update workflow |
| Database update inside a DB system | Base Database Service update workflow |
| Supported host-level DB system updates | dbcli or supported OCI workflow |
This is the correct path for routine patching of native OCI Base Database Service systems.
4. Fleet Application Management: Deprecated, Do Not Use for New Designs
OCI Fleet Application Management, or FAMS, was designed for centralized lifecycle operations, IT automation, resource management, and patch compliance for technologies deployed on OCI.
However, FAMS has been deprecated effective May 6, 2026, is not available for new adoption, and reaches end of life on May 1, 2027. Existing customers can continue using it only in existing tenancies and regions until that date.
Alternative Solutions
We recommend that you evaluate and transition to appropriate Oracle Cloud Infrastructure services based on your workload and monitoring needs:
Use Java Management Service (JMS) for Java workloads.
Use Database Management to monitor Oracle Database and Exadata resources.
For other resource types, use the applicable OCI Observability & Management services.
For new architecture, do not choose FAMS. Existing customers should treat it as a transition-only service and plan migration before the end-of-life date.
Quick Decision Guide
| What are you patching or managing? | Use This |
| Exa Infrastructure, VM Cluster, GI, or DB software | Exadata Fleet Update |
| Standard OCI Base Database Service DB system | Base Database Service update workflows |
| Database Home or database update in Base DB Service | Base Database Service update workflows |
| Database monitoring and performance analysis | OCI Database Management |
| CVE detection and patching for supported external databases | OCI Database Management |
| Full-stack patch automation using FAMS | Do not adopt FAMS for new designs |
Final Recommendation
Use Exadata Fleet Update for Exadata stack maintenance.
Use Base Database Service update workflows for standard OCI Base Database Service patching.
Use OCI Database Management for database monitoring, performance analysis, fleet visibility, and supported external database vulnerability workflows.
Do not use Fleet Application Management for new designs. It is deprecated and reaches end of life on May 1, 2027.
The safest patching strategy is to follow the lifecycle boundary of each platform: Exadata through EFU, Base Database Service through its native update workflow, and database observability through OCI Database Management.
