On OCI, the shape you pick decides how many Oracle licenses you owe, and bare metal can force a 32 to 64 OCPU commitment you never intended. This guide shows the exact OCPU to license math for flex and fixed shapes, where bare metal flips it against you, and the moves that protect your position.
How to Negotiate Your Oracle SaaS Renewal: The Five Moves at the Table
Scope before price: strip the 18 to 32 percent of inactive bundle modules first. Kill the escalator with a 0 to 3 percent cap that survives the term, trade term for protections, refuse the easiest-path module bundling, and close on Oracle's May 31 clock.
On OCI, the shape you pick decides how many Oracle licenses you owe, and bare metal can force a 32 to 64 OCPU commitment you never intended. This guide shows the exact OCPU to license math for flex and fixed shapes, where bare metal flips it against you, and the moves that protect your position.
Oracle Cloud Infrastructure prices and provisions compute in OCPUs, but Oracle also reports capacity in vCPUs, and that dual vocabulary is where most buyers miscount. On x86 shapes, one OCPU equals one physical core with hyperthreading enabled, which surfaces to the operating system as two vCPUs. Oracle's Bring Your Own License (BYOL) rules for OCI count OCPUs directly. Under the OCI-specific conversion, one Oracle Processor license (or 25 Named User Plus) covers 2 OCPUs. That is materially more generous than the authorized cloud rules Oracle applies elsewhere: on AWS and Azure, one Processor license covers only 2 vCPUs, so OCI delivers roughly twice the compute capacity per Oracle license on x86.
The trap sits in the translation layer. Teams migrating from AWS or Azure plan capacity in vCPUs, then carry that mental model onto OCI and either under-buy or over-buy. Remember the two facts that matter for your position: one OCPU equals two vCPUs on x86, and Oracle BYOL counts OCPUs, not vCPU pairs. If you size an OCI instance at 8 OCPUs (16 vCPUs) for Enterprise Edition, you owe 4 Processor licenses, not 8 and not 16. This is the same discipline we cover for other clouds in our note on Oracle Database BYOL on AWS, where the counting ratio is different and less favorable.
ARM changes the ratio. On Ampere Altra shapes, the cores do not use simultaneous multithreading, so each physical core runs one thread and 1 OCPU equals 1 vCPU. The license math on ARM is therefore one-to-one against OCPUs, but the same rule holds: license the OCPUs you assign, subject to the OCI conversion ratio. In our market experience, few Oracle Database production workloads run on ARM today, so this is a corner case, but it is worth confirming before you assume the x86 numbers apply.
On OCI x86, one Oracle Processor license covers 2 OCPUs (4 vCPUs). Count OCPUs, never raw vCPUs, and you avoid the most common migration overcharge.
Flex shapes are the buyer's friend. On a VM.Standard.E4.Flex or E5.Flex instance you choose the exact OCPU and memory allocation within the shape's range. An E4.Flex can run from 1 OCPU and 1 GB of RAM up to 64 OCPUs and 1,024 GB. When you deploy Oracle Database on a flex VM, your BYOL requirement is set by the OCPU count you assign to that instance, not by the physical cores present on the underlying host. Oracle treats OCI VM shapes as hard partitioned for licensing, so you license only the OCPUs configured on the VM.
The financial swing is large. An environment that would demand 32 licenses on a dedicated bare metal host may require only 8 licenses if you configure a flex VM at 8 OCPUs, which at 2 OCPUs per Processor license is 4 licenses of Enterprise Edition. That is the single most important lever on OCI: choose flex, size the OCPU count to actual demand, and you decouple your license liability from the raw hardware. This is a legitimate Oracle-sanctioned hard partition, unlike the contested soft-partitioning positions we document in the Oracle soft partitioning audit-defense guide.
One caveat that bites in audits: your licenses must cover the instance's maximum OCPU allocation. You cannot throttle CPUs at runtime and claim a lower count. If you provision 16 OCPUs and disable some, Oracle still counts 16. Set the shape at the number you intend to license and resize the shape itself if demand drops, rather than masking cores inside a fixed allocation. This is the same evidentiary principle we test in the CPU pinning evidence test: runtime tricks do not reduce the count, configuration does.
Bare metal shapes have no hypervisor. You get a dedicated physical server, and for Oracle Database on a Bare Metal (BM) shape, you are required to license all OCPUs on the physical host. There is no partition to shelter behind, so the full core count counts. The problem is that bare metal configurations start high. The minimum practical bare metal database footprint typically lands in the 32 to 64 OCPU range, and you cannot right-size below the shape's fixed OCPU allocation.
Work an example. A BM.Standard.E4.128 with 64 OCPUs obligates you to license 64 OCPUs, which at 2 OCPUs per Processor license is 32 Enterprise Edition Processor licenses. At Oracle's list price of $47,500 per Processor plus 22 percent support ($10,450 per Processor per year), that is $1.52 million list in licenses and $334,400 per year in support, before you add any options. Compare that with an 8 OCPU flex VM at 4 Processor licenses ($190,000 list, $41,800 annual support). The delta is entirely a function of shape choice, not workload.
Bare metal is not automatically wrong. It is the right call when you genuinely need 32-plus cores of dedicated compute, when you require physical isolation for security, or when license-compliance simplicity (physical cores, no partition arguments) is worth more than the license count. But if your database workload needs 8 or 16 OCPUs, bare metal is an expensive default. Decide bare metal on capacity and isolation grounds, then accept the license consequence, never the reverse.
| Shape example | OCPUs licensed | EE Processor licenses | List license cost | Annual support |
|---|---|---|---|---|
| VM.Standard.E5.Flex (8 OCPU) | 8 | 4 | $190,000 | $41,800 |
| VM.Standard.E5.Flex (16 OCPU) | 16 | 8 | $380,000 | $83,600 |
| BM.Standard3 (32 core config) | 32 | 16 | $760,000 | $167,200 |
| BM.Standard.E4.128 (64 OCPU) | 64 | 32 | $1,520,000 | $334,400 |
| BM.Standard.E5.192 (192 OCPU) | 192 | 96 | $4,560,000 | $1,003,200 |
The table uses Oracle's published $47,500 per Processor list and 22 percent support. Real negotiated discounts typically run 40 to 70 percent off license list in our experience, but support is calculated on the discounted license fee and then escalates, so the annual support figures move proportionally. The point is directional: every step up in shape size doubles or triples your standing liability, and bare metal removes the option to size down later without redeploying.
Bare metal licenses every core on the host. A 64 OCPU box is 32 Enterprise Edition licenses whether you use them or not. Size the workload, then pick the shape, never the other way around.
Standard Edition 2 (SE2) is not licensed the same way as Enterprise Edition, and the OCI-specific rules matter. For each supported SE2 Processor license, you may activate up to 4 OCPUs in the BYOL cloud service, with a maximum of 8 OCPUs per SE2 database. That caps the practical database size but also means SE2 covers more compute per license than EE. If you are using Named User Plus for SE2, you must meet a minimum of 10 NUP licenses for each instance running up to 8 OCPUs.
For smaller databases that fit within the 8 OCPU SE2 ceiling and do not need EE-only features, SE2 on a flex VM is frequently the lowest-cost compliant path on OCI. The decision hinges entirely on whether you use any Enterprise Edition feature or option (Partitioning, Advanced Compression, and similar), because a single EE feature invalidates SE2 entirely and forces the far more expensive EE count. Audit your feature usage before you assume SE2 is available; that check is where SE2 buyers most often trip.
The base Database license is the start, not the total. Every Enterprise Edition option and management pack carries its own BYOL line and must be licensed on the same OCPU count as the database. Partitioning, Advanced Security, Advanced Compression, Diagnostics Pack, and Tuning Pack each add cost per Processor. Two packs are especially treacherous because they self-enable inside Enterprise Manager without a purchase gate: the Oracle Cloud Management Pack and the Data Masking and Subsetting Pack. If they are switched on and you have not licensed them, that is an audit finding waiting to surface.
When you size options, use the same OCPU-to-license ratio as the base database. If your EE database runs on 16 OCPUs (8 Processor licenses) and you use Partitioning, you owe 8 Partitioning licenses too. Buyers routinely license the database correctly and forget the options, which is exactly the gap Oracle's LMS teams look for. Build the option count into your OCI shape sizing from day one, not after the audit letter arrives.
BYOL on OCI is worth roughly a 75 to 80 percent reduction against the License Included rate. The published gap is stark: an Enterprise Edition workload on an 8 OCPU OCI instance lists at approximately $4.03 per OCPU per hour without BYOL, versus about $1.34 per OCPU per hour with BYOL. If you already own Oracle Database Processor licenses with active support, BYOL is almost always the correct financial choice for any steady-state OCI workload, the same conclusion we reach for Azure in BYOL versus License Included on Azure.
Layer in Support Rewards. Oracle rebates 25 cents per dollar of OCI consumption against your on-prem support bill, rising to 33 cents for ULA customers. On a large OCI spend, that materially offsets the support renewal that BYOL keeps you paying. Model the combined position: BYOL keeps your support live, OCI consumption then earns Support Rewards that reduce that same support invoice. For ULA holders, the 33 cent rate and the deployment flexibility of OCI create a genuine planning lever, but count carefully at certification because cloud cores are treated differently, a point we detail in Oracle ULA on AWS.
Default to flex VM shapes for any Oracle Database workload that does not need dedicated hardware. Flex lets you license only the OCPUs you assign, decoupling liability from the host, and lets you resize later. Reserve bare metal for workloads that genuinely require 32-plus cores or physical isolation, and price the full-host license obligation into the business case before you commit.
Before signing any OCI expansion, run the shape decision through a licensing lens the same way you would evaluate on-prem virtualization, using the framework in our virtualization platform decision matrix. The cheapest Oracle license on OCI is the one you never had to buy because you sized the shape correctly the first time.
On x86 shapes, one OCPU equals one physical core with hyperthreading (two vCPUs), and Oracle's OCI BYOL conversion covers 2 OCPUs per Enterprise Edition Processor license. So 8 OCPUs require 4 EE Processor licenses. On ARM shapes, one OCPU equals one vCPU because there is no hyperthreading, but the 2 OCPUs per license ratio still applies.
Yes. Bare metal shapes have no hypervisor and no supported hard partition, so Oracle requires you to license all OCPUs on the physical host. A 64 OCPU bare metal box is 32 Enterprise Edition Processor licenses regardless of how many cores you actually use. This is the key difference from flex VMs, where you license only the OCPUs you assign.
No. Oracle counts the instance's maximum OCPU allocation, not the number of cores active at any moment. Throttling or disabling CPUs at runtime does not reduce your license obligation. To lower the count, resize the flex shape itself to a smaller OCPU allocation.
For databases up to 8 OCPUs with no Enterprise Edition features, SE2 is usually the lowest-cost compliant option. Each SE2 Processor license covers up to 4 OCPUs, with a maximum of 8 OCPUs per SE2 database, and Named User Plus requires a minimum of 10 NUP per instance. Using any single EE-only feature invalidates SE2 and forces the more expensive EE count.
BYOL reduces the cost by roughly 75 to 80 percent against the License Included rate. Published figures put an 8 OCPU Enterprise Edition workload at about $4.03 per OCPU per hour without BYOL versus about $1.34 per OCPU per hour with BYOL. If you already own licenses with active support, BYOL is almost always correct for steady-state workloads.
Yes. Every Enterprise Edition option and management pack carries its own BYOL line and must be licensed on the same OCPU count as the base database. Partitioning, Advanced Security, and the Diagnostics and Tuning packs each add cost. Watch the Cloud Management Pack and Data Masking Pack, which self-enable in Enterprise Manager and become audit findings if unlicensed.
Oracle licenses cores times a core factor, not raw cores. The 0.5 x86 factor, the worked counting, the virtualization trap, and where the factor does not apply.
Gated with a work email on the download page. No sales follow up you did not ask for.
Get the White Paper →
500+ enterprise clients. 11 vendor practices. Industry recognized. One conversation can change what you pay for the next three years.
One buyer side briefing a week. Renewal signals, audit moves, and the levers that work. No vendor spin.
