Not one ExaCC business case had modelled the support bill that keeps running under bring your own license
The rack is a subscription and the database compute is metered, and both arrive on an Oracle invoice you can read. The third meter is the 22 percent support you keep paying on licences you already own, and it is the only one that never appears on a bill from Oracle Cloud.
Prepared by Redress Compliance · August 16, 2026 · Oracle advisory. 21 ExaCC and Exadata models built, 2024 to 2025.
Executive summary
Three meters run, and the third one is invisible. The infrastructure subscription is fixed for the term, the database compute varies with enabled cores, and the support on your own licences bills separately and permanently.
At 100 enabled OCPUs, Enterprise Edition alone means 50 processor licences, about $2.375m at list, carrying $522,500 a year in support at 22 percent. That is the line no business case we reviewed had modelled.
Bring the full option stack and the support line reaches $1.23m a year, because RAC, Multitenant, Partitioning, and the Diagnostics and Tuning packs each convert at the same ratio as the database itself.
Scaling database compute to zero does not stop the bill. The rack charges for every month of the committed term whether you run a query or not, which makes an underused rack the same bill with less work done on it.
Three meters, and who carries the risk on each
ExaCC is a cloud subscription with a physical footprint, not a machine. Oracle owns the rack, installs it in your facility, operates it against the Oracle Cloud Infrastructure control plane, and takes it away at the end of the term. The hardware never appears on your balance sheet and the database licences never come with it.
| Layer | What it is | How it is charged | Who owns the risk |
|---|---|---|---|
| Infrastructure | The Exadata rack, in your room, operated by Oracle | Fixed subscription for the committed term | You, for the term. It bills whether used or not |
| Database compute | Enabled cores on the database servers | Metered per core hour, scaled online | You, monthly, through scaling discipline |
| Database licence | Enterprise Edition and every option in use | Bundled in the license included rate, or brought and supported by you | You, permanently, including the audit exposure |
ExaCC is not a managed database service. Oracle operates the infrastructure up to the virtual machine cluster boundary: hardware, firmware, storage cells, network fabric, and the control plane. Above that line the databases, schemas, performance, patching decisions, backup configuration, data, and option compliance are all yours. If the business case assumed the database administration team gets smaller, test that assumption against this boundary before the subscription is signed.
The conversion math, and the line nobody carries forward
Bring your own license converts at two OCPUs per Oracle Database Enterprise Edition processor licence, because the 0.5 core factor is already inside the cloud unit. Every priced option converts at the same ratio, so the option stack scales with the compute rather than with the workload. At 100 enabled OCPUs:
| Component | List per processor | Licences needed | List value to own | Support at 22% a year |
|---|---|---|---|---|
| Database Enterprise Edition | $47,500 | 50 | $2,375,000 | $522,500 |
| Real Application Clusters | $23,000 | 50 | $1,150,000 | $253,000 |
| Multitenant | $17,500 | 50 | $875,000 | $192,500 |
| Partitioning | $11,500 | 50 | $575,000 | $126,500 |
| Diagnostics and Tuning packs | $12,500 combined | 50 | $625,000 | $137,500 |
| Full stack | List, before discount | 50 of each | $5,600,000 | $1,232,000 |
The right hand column is the addition. Over a three year term the support alone on a fully brought option stack is roughly $3.7m before any uplift, and it continues after the ExaCC term ends because it attaches to licences you own rather than to the rack you rented. Terminate the support line to save money and the bring your own license rate is no longer available to you, which is what makes it a genuinely permanent commitment.
The Oracle Exadata licensing strategy
The core sizing method, the bring your own license conversion math, and the option coverage checks that decide an Exadata business case.
Get the brief →Bring your own license wins on a condition nobody checks
The standard pitch is that license included is the clean choice because it bundles the options Exadata workloads need. The benchmarking says otherwise, but with a condition attached that decides the whole question. In roughly two of three ExaCC estates modelled, a buyer already holding Enterprise Edition plus RAC and Partitioning paid 12 to 22 percent less on bring your own license across a three year term, even after support. That is a real finding and it is routinely quoted without its second half: bring your own license only wins if your option entitlements actually match what your teams enable.
The platform makes that condition hard to satisfy. The Exadata service presents the full Enterprise Edition feature set, including the options an on premises buyer would have to purchase separately. Real Application Clusters is the obvious one, because Exadata is a clustered platform by design. Partitioning, Multitenant, In Memory, Advanced Compression, Active Data Guard, and the Diagnostics and Tuning packs are all available to anyone with the privilege to enable them. Bring Enterprise Edition alone, let a developer switch on Partitioning because the platform offers it, and you have bought a compliance finding rather than a discount. Option coverage was double paid or genuinely unclear in roughly two of five contracts reviewed.
Then there is the line the arithmetic above exists to make visible. Not one business case we were shown had modelled the on premises support bill that continues under bring your own license. It is easy to miss because it does not arrive from Oracle Cloud, it arrives from the support renewal team, in a different month, against a different budget, and it was already being paid before ExaCC was contemplated. But it is $522,500 a year on Enterprise Edition alone at 100 OCPUs and $1.23m with the option stack, and it rises with every support uplift for as long as the licences are held. A three year comparison that omits it is not close to correct.
The operational counterpart is scaling discipline. Cores scale online to meet demand, which is genuinely useful and genuinely expensive, and every estate modelled had enabled cores still running weeks after the peak that justified them. Idle enabled cores wasted 10 to 20 percent of the database charge, and putting a named owner on the scale down with a monthly review recovered a median 17 percent. One caution on the unit itself: Oracle has been moving cloud database services from the OCPU to the smaller ECPU, and the two are not interchangeable, so rebuild the model in whichever unit your ordering document names rather than the one the marketing page uses. The rack sizing question is worked in the Exadata guide, the support arithmetic in Oracle support costs, and the wider library sits in the Oracle practice.
- Your agreements decoded into plain English before the auditor interprets them for you
- Option entitlements matched line by line against what the platform lets teams enable
- Three year cost modelled per path, including the 22 percent support you keep paying
The option controls that make bring your own license safe
- Baseline option usage before migration, and again 30 days after go live, because usage on a new platform drifts fastest in the first month and nobody reports it.
- Restrict the privileges that enable priced options, and make enabling one a change request rather than a technical decision available to anyone with the rights.
- Match every option in use against a specific entitlement line, not against a general belief that you are covered. Two of five contracts we reviewed could not do this cleanly.
- Put a named owner on core scale down with a monthly review of enabled cores against actual demand, and treat an unexplained increase as an incident. That single discipline recovered a median 17 percent of the database charge.
- Read the compute unit in the ordering document, OCPU or ECPU, and rebuild the model in that unit. A rate that looks lower per unit is not automatically lower per workload.
- Re run the option check before every renewal, because on a shared platform one team's decision creates the whole estate's liability.
What the ExaCC models showed, 2024 to 2025
Across roughly 18 to 24 ExaCC and Exadata models built, the licence path and the enabled core count drove the number rather than the rack shape:
What buyers already holding Enterprise Edition plus RAC and Partitioning saved over three years, support included.
Contracts where option coverage was double paid or genuinely unclear, which is the condition that decides whether bring your own license wins at all.
Idle enabled cores left running after peaks wasted 10 to 20 percent of the database charge, and scale down discipline recovered a median 17 percent. License included remains the right answer in three situations worth naming plainly: when you hold no spare entitlements, when the workload is short lived, and when you want the option compliance question to disappear. It is not a bad product, it is a rental priced like a rental, and it becomes expensive precisely when the workload turns out to be permanent.
The exit positions differ more than the rates do. Under bring your own license you still hold perpetual licences when the term ends. Under license included you hold nothing.
Watch the briefing · 4:41How to Negotiate an Oracle OCI Deal: The Discount Is Set. The Deal Is Not.Where the commitment, the unit, and the term decide an Oracle cloud bill more than the rate does.
Your first five moves
- Add the support line to the business case at 22 percent of the list value of every licence you intend to bring, held for the full comparison period.
- Inventory option usage before you choose a path, and match each option against a specific entitlement line rather than a general belief in coverage.
- Model both paths at realistic enabled core counts, including scale down, rather than at the peak the rack was sized for.
- Confirm whether your ordering document names OCPUs or ECPUs and rebuild every figure in that unit before comparing rates.
- Put a named owner on scale down with a monthly review before go live, not after. The Oracle practice builds both models with you.
Frequently asked questions
Do the Oracle Database licences come with ExaCC?
No. The infrastructure subscription includes no database licences whatsoever, and that is the budget surprise on most ExaCC deals. You choose between renting the licence inside the compute rate under license included, or bringing licences you already own and supporting them yourself.
What does bring your own license actually cost each year?
At 100 enabled OCPUs you need 50 Enterprise Edition processor licences, about $2.375m at list, carrying $522,500 a year in support at 22 percent. Bring the full option stack of RAC, Multitenant, Partitioning, and the Diagnostics and Tuning packs and the annual support line reaches $1.23m.
Why is the support line so often missed?
Because it does not arrive from Oracle Cloud. It comes from the support renewal team, in a different month, against a different budget, and it was already being paid before ExaCC was contemplated. Not one business case we reviewed had carried it into the comparison.
What is the bring your own license conversion ratio?
Two OCPUs per Oracle Database Enterprise Edition processor licence, because the 0.5 core factor is already baked into the cloud unit. Every priced option converts at the same ratio, so the option stack scales with the compute rather than with the workload.
Does scaling cores to zero stop the bill?
It stops the database compute meter. The rack keeps charging for every month of the committed term whether you run a query or not. That asymmetry is the most useful thing to understand before sizing an ExaCC, because an underused rack is the same bill with less work done on it.
What is the options trap on Exadata?
The service presents the full Enterprise Edition feature set, including options an on premises buyer would purchase separately. Bring Enterprise Edition alone, let a developer enable Partitioning because the platform offers it, and you have bought a compliance finding rather than a discount.
When is license included genuinely right?
In three situations. When you hold no spare entitlements, when the workload is short lived, and when you want the option compliance question to disappear. It is a rental priced like a rental, and it becomes expensive precisely when the workload turns out to be permanent.
Is ExaCC a managed database service?
No. Oracle operates the infrastructure up to the virtual machine cluster boundary. The databases, schemas, performance, patching decisions, backup configuration, data, and option compliance stay with you. Test any business case that assumed a smaller database administration team against that boundary.
What is the difference between OCPU and ECPU here?
Oracle has been moving cloud database services from the OCPU to the smaller ECPU, and the two are not interchangeable. A rate that looks lower per unit is not automatically lower per workload, so read the metric in your ordering document and rebuild the model in whichever unit the contract names.
How much does scale down discipline actually recover?
A median 17 percent of the database charge in our engagement file. Every estate modelled had enabled cores still running weeks after the peak that justified them, and idle cores wasted 10 to 20 percent. A named owner and a monthly review is the whole control.
How to Negotiate an Oracle ULA: No Price List, Just Your Business Case
There is no price list: the ULA fee is a story built from your estate and your growth. Give conservative growth answers, keep the product list narrow, model the breakeven yourself, and negotiate the certification exit before you sign.
