Home/Insights/OCI Database

OCI Database Support Matrix: DBCS vs ExaDB-D vs ExaDB-XS

Which Oracle Database versions and deployment topologies are available on Base Database Service, Exadata Database Service on Dedicated Infrastructure and Exadata Database Service on Exascale Infrastructure, and what has actually changed for RAC.

Database architects reviewing a two-node database cluster beside Exadata racks

Current view: August 2026. OCI service capabilities change often, so this article links every claim back to Oracle's documentation.

Executive summary

A common OCI architecture question is which Oracle Database versions and deployment topologies are available on Base Database Service (DBCS), Exadata Database Service on Dedicated Infrastructure (ExaDB-D, formerly commonly referred to as ExaCS) and Exadata Database Service on Exascale Infrastructure (ExaDB-XS).

DBCS

Base Database Service

26ai21c19c
Single instanceRAC, EE-EP retiring

Shape and storage type affect topology.

ExaDB-D / ExaCS

Exadata on Dedicated Infrastructure

26ai21c19c
Single instanceRAC

Older releases can remain supported on existing 19c VM clusters with upgrade support.

ExaDB-XS

Exadata on Exascale Infrastructure

26ai21c19c
Single instanceRAC

Single-VM VM clusters are available for single-instance workloads.

The key clarification is that Oracle RAC has not been removed from DBCS. Oracle's current documentation explicitly states that Base Database Service provides both single-node DB systems and multi-node RAC DB systems, with Enterprise Edition, Extreme Performance (EE-EP) required for multi-node RAC.

Effective31Jul 2026
Important, My Oracle Support KB921246

EE-EP retirement on Base Database Service

Oracle has announced the retirement of the EE-EP software edition on Base Database Service, effective July 31, 2026. Existing deployments continue to run, but new provisioning and contract renewals are affected. Because multi-node RAC on DBCS requires EE-EP, validate any new DBCS RAC deployment with Oracle. Oracle points EE-EP workloads to ExaDB-XS.

  1. Existing deploymentsContinue to run
  2. July 31, 2026EE-EP retirement effective
  3. New provisioning and renewalsAffected; Oracle points EE-EP workloads to ExaDB-XS

1. Current high-level matrix

Service26ai21c19cSingle instanceRACImportant qualification
Base Database Service (DBCS)YesYesYesYesYesRAC requires EE-EP, which is retiring for new provisioning from July 31, 2026. Shape and storage type affect topology.
ExaDB-D / ExaCSYesNo*YesYesYesCurrent service documentation lists 26ai and 19c; older releases can remain supported on existing 19c VM clusters with upgrade support.
ExaDB-XS / ExascaleYesNoYesYesYesSupports 26ai and 19c. Single-VM VM clusters are available for single-instance workloads.
SupportedNot listedSwipe sideways to see every column

* 21c is not listed as a currently supported ExaDB-D database version in the current service description. Check existing environments and older releases against Oracle's current support and upgrade documentation before making a migration decision.

2. Base Database Service (DBCS)

Oracle Base Database Service supports Oracle AI Database 26ai, Oracle Database 21c and Oracle Database 19c. It supports both single-node DB systems and two-node RAC DB systems.

DBCS version availability depends on the shape

DBCS shape26ai21c19cNotes
Ampere A1YesNoYesSingle-node only
AMD E5YesNoYesRAC possible, subject to RAC requirements
AMD E4YesYesYesRAC possible, subject to RAC requirements
Intel X9YesYesYesRAC possible, subject to RAC requirements
Intel X7YesYesYesRAC supported subject to shape constraints; VM.Standard2.1 is single-node only
VM.BaseDB.x86YesNoYesGeneration-agnostic. Single-node only; SE, EE and EE-HP on LVM
VM.Standard.x86YesNoNoGeneration-agnostic. Single-node only; shape retiring July 31, 2026
SupportedNot listedSwipe sideways to see every column

Version support on Ampere A1, AMD E5, AMD E4 and Intel X9 starts at specific minimum Release Updates (for example, 19.19 or later on Ampere A1 and 19.21 or later on AMD E5). Check the shape documentation for the exact RU.

RAC constraints on DBCSImportant

Oracle states that multi-node RAC DB systems require a minimum of two OCPUs per node and ASM; RAC DB systems cannot be created using Logical Volume Manager. Ampere A1 and the generation-agnostic x86 shapes are single-node only.

3. Exadata Database Service on Dedicated Infrastructure (ExaDB-D / ExaCS)

The current Oracle service description lists Oracle AI Database 26ai and Oracle Database 19c as supported database versions. Older database versions (12.2, 12.1 and 11.2) are also documented as supported with Upgrade Support, primarily in the context of existing 19c cloud VM clusters.

Exadata Database Service uses Enterprise Edition, Extreme Performance or an eligible BYOL model. The Extreme Performance option includes Oracle RAC. ExaDB-D therefore remains the Exadata option when the architecture requires Exadata infrastructure and RAC, while still allowing single-instance database deployments.

4. Exadata Database Service on Exascale Infrastructure (ExaDB-XS)

The current ExaDB-XS documentation lists Oracle AI Database 26ai and Oracle Database 19c as supported database releases. Enterprise Edition, Extreme Performance includes Oracle RAC.

Single-node ExaDB-XS is now availableGA January 2025

A point that often causes confusion is that ExaDB-XS is no longer effectively "RAC only". Oracle made single-VM VM clusters generally available in January 2025. A VM cluster can run with one VM for a single-instance workload, or be scaled to multiple VMs for a RAC deployment.

Even with a single VM, Oracle notes that the RAC components and RAC networking setup are still present. The single-VM capability is intended for workloads that do not require the availability characteristics or licensing of a multi-node RAC cluster.

5. RAC: what has actually changed?

The statement "RAC is no longer available on DBCS" is not supported by the current Oracle documentation, which still describes multi-node RAC DB systems. What has changed is the edition RAC depends on: EE-EP on DBCS is being retired for new provisioning from July 31, 2026, so plan any new DBCS RAC deployment with that in mind.

DBCSAffected by EE-EP retirement

Single-node and multi-node RAC are documented. New EE-EP provisioning, and therefore new RAC, is affected by the July 31, 2026 retirement.

ExaDB-DRAC available

RAC is available through the Enterprise Edition, Extreme Performance capability.

ExaDB-XSRAC and single-VM

RAC is available, and single-VM VM clusters also allow single-instance workloads.

6. Architecture decision guide

Interactive guide

Find the likely fit

Choose a requirement to see which services fit and why.

DBCSBase Database ServiceEE-EP retirement applies
ExaDB-DExadata on Dedicated InfrastructureEE-EP retirement applies
ExaDB-XSExadata on Exascale InfrastructureEE-EP retirement applies
Likely fit19c + RAC + VM-based OCI database serviceExaDB-D / XS, or DBCS

All three can support 19c. DBCS RAC is subject to the EE-EP retirement; choose based on Exadata and workload requirements.

View the full decision table
RequirementLikely fitWhy
19c + RAC + VM-based OCI database serviceExaDB-D / XS, or DBCSAll three can support 19c. DBCS RAC is subject to the EE-EP retirement; choose based on Exadata and workload requirements.
21c + RACDBCSCurrent DBCS documentation lists 21c, with availability depending on shape. Subject to the EE-EP retirement; ExaDB-XS is Oracle's stated target for EE-EP workloads.
26ai + RACExaDB-XS, ExaDB-D or DBCSAll three support 26ai. DBCS RAC is subject to the EE-EP retirement; topology and infrastructure requirements determine the best fit.
26ai + single instanceDBCS, ExaDB-D or ExaDB-XSAll can support single-instance deployment, subject to shape and VM-cluster constraints.
Exadata infrastructure requiredExaDB-D or ExaDB-XSUse the Exadata service family.
Single instance on ExaDB-XSExaDB-XSUse a single-VM VM cluster.

7. Key takeaways

  1. RAC is still documented on DBCS, but its required edition (EE-EP) is being retired for new provisioning from July 31, 2026.
  2. DBCS currently supports 26ai, 21c and 19c, but version availability varies by compute shape and minimum Release Update.
  3. DBCS RAC requires EE-EP and a supported RAC configuration, and RAC requires ASM rather than LVM.
  4. ExaDB-D currently lists 26ai and 19c as its primary supported database versions, with older versions available under documented upgrade-support conditions.
  5. ExaDB-XS currently supports 26ai and 19c and supports both multi-node RAC and single-VM deployments (single-VM clusters still run the RAC components).
  6. The right architecture decision weighs database release, shape or VM-cluster type, RAC requirement, licensing, Exadata requirement and operational requirements together.

Note: OCI service capabilities and regional availability can change. Validate the target OCI region, shape, database software image and RU, licensing model and current Oracle documentation before production deployment.

8. Oracle references

More insights

All insights
Oracle EBS, 15 Sep 2026, 6 min read

Beyond WebLogic: The EBS 12.2 FMW 14c Journey

What changes, what to prepare, and how Oracle is planning the EBS 12.2 Next Generation Technology Stack.

Read article

Choosing between DBCS, ExaDB-D and ExaDB-XS?

Our specialists help teams pick the right service, topology and licensing model, and run it afterwards.