Which OCI Database Service Is Right for You? Autonomous vs Base vs Exadata

There is no single “Oracle on OCI.” There are four genuinely different services, and the gap between them — in cost, control, and operational effort — is large. Choose the wrong one and you either overpay for power you can’t use, or you inherit operational work you wanted the cloud to remove. This is a practical guide to picking correctly, written for Slovak and Czech enterprises and their compliance reality.

The four services, in one picture

• Autonomous Database (ADB) — fully managed (PaaS), built on Exadata, with machine-learning automation for tuning, patching, and scaling. You get no OS or root access; you manage schema, connections, and security policy. Comes as Serverless (shared, lowest overhead) or Dedicated (private infrastructure), and as ATP (transactional) or ADW (analytics).
• Base Database Service — Oracle EE or SE on ordinary x86/ARM VMs (or bare metal). Co-managed: you keep full root and DBA control, and you remain responsible for OS patching and tuning.
• Exadata Database Service — co-managed Oracle on dedicated engineered Exadata hardware (Dedicated, or the newer elastic Exascale). You get root on the database VMs; Oracle runs the hardware and storage cells.
• Exadata Cloud@Customer (ExaCC) — the same Exadata cloud service, but the rack sits in your own data center for data-residency or latency reasons, on a cloud subscription.

The real decision axis: automation vs control

Every other difference flows from one question: how much of the database operation do you want to own?

If your team is small or you want to move fast, ADB removes almost all DBA toil. If you run legacy applications that need specific OS packages, custom patches, or kernel-level access, the co-managed services (Base or Exadata) are the only options that give you root. ExaCC exists for one specific reason: when the data legally or physically cannot leave your premises.

Pricing: ECPU vs OCPU, BYOL vs License-Included

Two billing units appear across OCI. An OCPU is one physical core with hyper-threading (≈2 vCPUs). An ECPU is an abstracted, elastic unit — the direction Oracle is steering customers toward. The other lever is licensing: License-Included bundles the Oracle licence into the hourly rate, while BYOL (Bring Your Own Licence) reuses perpetual licences you already own.

The savings from BYOL are substantial. As of 2026, Autonomous Database runs at roughly $0.336 per ECPU/hour License-Included versus about $0.081 per ECPU/hour BYOL — BYOL cuts compute by around 76%. Under BYOL you must hold enough on-premises licences to cover usage: roughly one EE Processor licence per 8 ECPUs (or 2 OCPUs), and you keep paying the 22% annual support on those on-prem licences.

Treat all figures as as-of-2026 and confirm current Oracle pricing for your region — OCI rates and units change. The point is the structure, not the cent: Base Database is the cheapest per ECPU, Autonomous sits in the middle with zero ops, and Exadata is the premium tier for raw power and consolidation.

This is exactly where a license review pays for itself — BYOL is cheaper, but it shifts cost into licence-compliance risk if you don’t size it correctly.

High availability is a service-level decision

What you get “for free” depends on the service:

• Autonomous builds in automated backups and Autonomous Data Guard; Dedicated runs multi-node RAC behind the scenes.
• Base Database supports optional 2-node RAC (EE) and Data Guard, but you configure and operate it.
• Exadata / ExaCC run active-active RAC across the engineered nodes, with Data Guard and Active Data Guard (read-only standby, real-time query, automatic block repair, Far Sync) available.

Note that Active Data Guard is bundled with Exadata and the EE Extreme Performance package, but must be separately licensed under BYOL — a classic audit trap (see migration pitfalls below). The HA design itself is something we cover in detail in our RAC & Data Guard work.

The compliance angle for SK & CZ

For regulated organisations, the choice is narrowed by law before it’s narrowed by cost:

• DORA (financial entities under the NBS/ČNB) demands strong third-party-risk and continuity controls — favouring ADB Dedicated or ExaCC for structural isolation and clear control boundaries.
• Public sector: OCI is registered in the Czech Republic’s eGovernment Cloud Catalogue, with Oracle reporting accreditation at the catalogue’s highest commercial security tier (BU3) — which lets public bodies run co-managed Base or Exadata services in the public cloud.
• EU Sovereign Cloud (EU-only operations, EU-incorporated entities) addresses exposure to extraterritorial laws like the US CLOUD Act, reportedly at price parity with standard OCI regions.
• ExaCC keeps the workload physically on-premises when residency rules leave no other option.

Migration reality: ZDM and its traps

Most moves use Oracle’s Zero Downtime Migration (ZDM), in one of two modes:

• Physical (RMAN + Data Guard switchover): block-for-block, very predictable, downtime often under 15 minutes — but source and target must share the same major version and platform.
• Logical (Data Pump + GoldenGate): flexible, supports cross-platform moves (Solaris/AIX → Linux) and in-flight upgrades (e.g. 12c → 19c/23ai), at the cost of more CPU/IO and preparation.

The pitfalls that actually cost money:

1. Leaving compute scaled up after the load — instances bumped up for the migration keep billing at the higher rate. Scale them back down.
2. BYOL peak-licensing gap — you must own licences for the peak auto-scaled footprint, not the average. A 16-ECPU database that bursts to 48 ECPUs for one hour needs licences for 48.
3. Standard Edition ceiling — SE under BYOL caps an Autonomous instance at 32 ECPUs; high-throughput apps can hit that wall.
4. Untested failback — ZDM automates the switchover to OCI; failing back is manual. Practise it before go-live.

So, how do you choose?

• Want minimal ops, fast? Autonomous (Serverless for dev/test and most apps; Dedicated for regulated isolation).
• Need root/OS control or run legacy apps? Base Database (VM or bare metal).
• Consolidating many databases or need extreme scale? Exadata Service (Exascale for elastic cost control).
• Data can’t leave the building? Exadata Cloud@Customer.

Bottom line

The cheapest service on paper is rarely the cheapest in total — licensing model, HA requirements, and operational effort dominate the real number. The right answer depends on your team, your compliance regime, and your existing licences.

We build that comparison independently — with the licensing math and the migration plan written down — and we don’t resell any of these services. If you’re planning a move to OCI and want the decision made on evidence, let’s talk.