OCI Bare Metal Compute is Oracle's most powerful infrastructure option — dedicated physical servers with no virtualisation overhead, direct access to NVMe storage, and high-bandwidth RDMA networking. It is also the most license-efficient path for enterprises bringing existing Oracle Database licenses to OCI. Oracle's BYOL rules on bare metal are more favorable than on virtual machine shapes, but the commercial trap is in how Oracle counts processor licenses across the physical socket layout. Enterprises that deploy Oracle Database on OCI bare metal without understanding the Core Factor Table mapping and BYOL entitlement rules routinely over-license or, worse, create hidden compliance gaps. This guide provides the independent, buyer-side analysis.
OCI Bare Metal Compute delivers physical servers provisioned to a single tenant with no hypervisor layer. The absence of virtualisation is significant for Oracle Database licensing: Oracle's policy is that physical partitioning (bare metal) is compliant hard partitioning — meaning you only license the physical processors on the server, not any broader host pool or cluster. This stands in contrast to VMware, where Oracle treats the entire host pool as licensed.
The current OCI bare metal shape portfolio spans standard CPU compute, high-performance compute, GPU, and HPC configurations. For Oracle Database workloads, the most commonly deployed shapes are in the Standard and High Performance tiers:
| Shape | OCPU | RAM | Processor | Local Storage | Network |
|---|---|---|---|---|---|
| BM.Standard3.64 | 64 | 1TB | Intel Xeon (Ice Lake) | NVMe SSD | 2×25 Gbps |
| BM.Standard.A1.160 | 160 | 1TB | Ampere Altra (ARM) | NVMe SSD | 2×50 Gbps |
| BM.DenseIO2.52 | 52 | 768GB | Intel Xeon (Cascade Lake) | 51.2TB NVMe | 2×25 Gbps |
| BM.DenseIO.E4.128 | 128 | 2TB | AMD EPYC (Milan) | 54.4TB NVMe | 2×50 Gbps |
| BM.HPC2.36 | 36 | 384GB | Intel Xeon (Skylake) | 6.7TB NVMe | RDMA / RoCE |
| BM.Optimized3.36 | 36 | 512GB | Intel Xeon (Ice Lake) | 3.84TB NVMe | 2×50 Gbps RDMA |
For Oracle Database licensing purposes, the relevant parameter is not OCPU count but the physical core count and processor model — because the Core Factor Table assigns a multiplier based on processor family. A BM.Standard3.64 shape with Intel Ice Lake processors runs at a core factor of 0.5, meaning 64 physical cores require 32 Oracle Processor licenses. AMD EPYC shapes also attract a 0.5 core factor. The practical implication: AMD EPYC-based bare metal shapes such as BM.DenseIO.E4.128 are the most license-efficient Oracle Database infrastructure in OCI — 128 physical cores at 0.5 factor = 64 Oracle Processor licenses.
Critical distinction: OCI OCPUs are not physical cores. One OCPU equals two vCPUs (one physical core with hyperthreading). Oracle Database license counting on bare metal must be done against physical core count, not OCPU count. Confusing these metrics is one of the most common errors in OCI BYOL deployments.
Oracle's BYOL (Bring Your Own License) program on OCI allows enterprises to apply existing on-premise Oracle Database licenses to OCI infrastructure, receiving a corresponding discount on the OCI compute pricing. On bare metal shapes, BYOL is typically more advantageous than on virtual machine shapes because bare metal maps directly to physical processor and core counts — the same units used in on-premise Oracle licensing agreements.
The BYOL mechanics on OCI bare metal work as follows. Oracle applies the Core Factor Table to the physical processor(s) in the bare metal shape to determine how many Oracle Processor licenses are required. If you have existing Oracle Database Enterprise Edition licenses covering 32 Processor licenses, you can deploy Oracle Database EE on a bare metal shape requiring exactly 32 Processor licenses and pay only the OCI infrastructure cost — no additional Oracle license fees. The BYOL discount on OCI compute ranges from 25% to over 50% depending on shape and Oracle Database edition.
| Oracle Database Edition | BYOL Compute Discount (Approx.) | Full License Rate (No BYOL) |
|---|---|---|
| Enterprise Edition | ~50% | Included in "Oracle DB System" pricing |
| Standard Edition 2 | ~25% | Lower base compute rate |
| Autonomous Database | N/A | Consumption-based (ECPU/OCPU) |
The key condition for BYOL on bare metal: the Oracle Database licenses being applied must be current on annual support (Oracle's 22% support charge must be paid up). Licenses on third-party support from providers like Rimini Street are generally not eligible for OCI BYOL, because Oracle's OCI terms require the licenses to be under Oracle's support schedule. This creates a strategic tension: enterprises who have moved to third-party support to reduce the 22% annual bill cannot simultaneously use those licenses for OCI BYOL savings.
Our Oracle Cloud Advisory service maps your existing license portfolio against OCI bare metal shapes to identify the most BYOL-efficient deployment configuration and surface any entitlement gaps before they become audit exposure.
Oracle's Core Factor Table was originally designed for on-premise server licensing, but it applies identically to OCI bare metal compute. The Core Factor determines how many Oracle Processor licenses are required per physical core, based on the processor vendor and architecture family. This table has significant commercial consequences for OCI bare metal deployments.
| Processor Family | Core Factor | OCI Bare Metal Shapes | Licenses per Physical Core |
|---|---|---|---|
| Intel Xeon (any generation) | 0.5 | BM.Standard3.64, BM.Optimized3.36, BM.DenseIO2.52 | 0.5 Processor licenses |
| AMD EPYC (any generation) | 0.5 | BM.DenseIO.E4.128, BM.Standard.E4.128 | 0.5 Processor licenses |
| Ampere Altra (ARM) | 0.5 | BM.Standard.A1.160 | 0.5 Processor licenses |
| IBM POWER (for reference) | 1.0 | N/A on OCI | 1.0 Processor license |
The current OCI bare metal portfolio is entirely composed of processors at 0.5 core factor, which means all OCI bare metal shapes require half the Oracle Processor licenses of equivalent IBM POWER deployments. This is identical to standard x86 on-premise servers and gives OCI bare metal parity with on-premise x86 infrastructure from a licensing standpoint.
Where complexity arises is in the interaction between physical socket count and the minimum NUP rules. For Oracle Database Enterprise Edition on bare metal, the Named User Plus (NUP) minimum is 25 NUP per Processor license. On a BM.Standard3.64 (64 physical cores at 0.5 factor = 32 Processor licenses), the minimum NUP deployment would be 32 × 25 = 800 Named User Plus licenses. Most enterprise Database EE deployments on bare metal use Processor metric rather than NUP precisely to avoid this minimum calculation complexity.
OCPU vs physical core trap: Oracle's OCI documentation frequently uses OCPU counts. One OCPU = one physical core (one thread with hyperthreading disabled for licensing purposes). The Core Factor Table calculation uses physical cores, not OCPUs, not vCPUs. Always verify the physical core count for your selected bare metal shape before calculating license requirements.
The choice between bare metal and VM shapes on OCI has direct license cost implications. On bare metal, Oracle's policy allows you to license only the physical processors on that specific server. On VM shapes within a multi-tenant infrastructure, Oracle does not require you to license the entire physical host — unlike VMware environments — because OCI VM shapes use Oracle's own KVM-based hypervisor, which Oracle accepts as hard partitioning when shapes are properly configured.
However, the practical licensing efficiency differs between bare metal and VM shapes:
The conclusion: bare metal is not always the most license-efficient option for Oracle Database. If your workload requires fewer than the full physical core count of the bare metal shape, a VM shape will require fewer Oracle Processor licenses. Bare metal makes sense when you need the full compute capacity of the shape, require dedicated hardware for performance or security, or are migrating a workload that was licensed on an equivalent-capacity on-premise server.
Our license optimization service identifies the OCI shape configuration that minimises your combined Oracle Processor license count and OCI infrastructure cost. Clients typically reduce total OCI Oracle Database TCO by 20–40%.
OCI bare metal compute is priced competitively against AWS EC2 Bare Metal and Azure Bare Metal instances — particularly when Oracle Universal Credits are applied. The cost comparison, however, must include the Oracle Database license cost (or BYOL credit) to be meaningful for enterprises running Oracle workloads.
| Platform | Shape / Instance | Compute Cost ($/hr, list) | Oracle DB EE License Cost ($/hr, non-BYOL) | Total (Non-BYOL) |
|---|---|---|---|---|
| OCI Bare Metal | BM.Standard3.64 | ~$3.20 | ~$51.20 (64 cores × $0.80) | ~$54.40 |
| AWS EC2 Bare Metal | m6i.metal (128 vCPU) | ~$7.68 | ~$102.40 (64 cores × $1.60) | ~$110.08 |
| Azure Bare Metal | M416ms v2 | ~$44.00 | ~$102.40 | ~$146.40 |
| OCI Bare Metal (BYOL) | BM.Standard3.64 | ~$1.60 (BYOL discount) | $0 (own licenses) | ~$1.60 |
| AWS EC2 (BYOL) | m6i.metal | ~$7.68 | $0 (own licenses) | ~$7.68 |
The headline finding: for enterprises with existing Oracle Database EE licenses on current support, OCI bare metal BYOL is dramatically cheaper than equivalent AWS or Azure bare metal. OCI compute pricing is substantially lower than both hyperscalers for bare metal, and Oracle's BYOL program applies the full license credit to OCI infrastructure. AWS BYOL pricing for Oracle Database on bare metal does not receive equivalent infrastructure discounts — you pay full AWS EC2 pricing and simply avoid the hourly Oracle license charge.
This cost advantage is Oracle's primary commercial argument for OCI migration, and it is legitimate for enterprises with large on-premise Oracle Database EE estates. The advisory question is whether the Oracle infrastructure lock-in created by deep OCI commitment — and the continuing 22% annual support cost required to maintain BYOL eligibility — outweighs the infrastructure cost savings. That is a financial model calculation, not a technology decision.
Enterprises deploying Oracle Database on OCI bare metal encounter several recurring compliance exposures that Oracle's LMS team targets during audits of cloud deployments.
Oracle Database options — Diagnostics Pack, Tuning Pack, Partitioning, Advanced Security, In-Memory, RAC — must be separately licenced even on OCI. Oracle Database 19c and 21c deployed on bare metal retain the same options architecture as on-premise. Diagnostics Pack and Tuning Pack are enabled by default in many DBA configurations, creating accidental license exposure. Our team encounters this issue in the majority of compliance reviews we conduct for enterprises migrating to OCI.
BYOL calculations are based on the full physical core count of the bare metal shape, regardless of Oracle Database CPU utilization. An enterprise with 20 Oracle Database EE Processor licenses cannot BYOL a BM.Standard3.64 (which requires 32 Processor licenses at the 0.5 core factor). Partial coverage is not permitted under BYOL — you must have licenses for the full shape requirement or use a smaller VM shape. We regularly identify entitlement gaps in initial BYOL mapping exercises.
Oracle Real Application Clusters on OCI bare metal requires a separate RAC license in addition to Oracle Database EE licenses. Each node's full processor count is licenced. Many enterprises assume OCI's managed RAC deployment handles the licensing automatically — it does not. The BYOL RAC deployment on OCI bare metal requires the same license count as an equivalent on-premise RAC cluster.
If Oracle Database licenses supporting OCI BYOL deployments fall off Oracle's Annual Support, Oracle can retroactively claim back-license fees for the OCI deployment period during which those licenses were used without valid support. Unlike on-premise deployments where support lapse is sometimes missed by Oracle, OCI deployments are visible to Oracle through the infrastructure layer — Oracle knows precisely which licenses are applied to which OCI tenancy.
For enterprises approaching an Oracle audit involving OCI bare metal deployments, our audit defense service provides pre-audit discovery to surface and remediate these exposure points before Oracle's LMS scripts run.
Enterprise buyers running Oracle Database on OCI bare metal have several proven levers to reduce total Oracle licensing cost without reducing database functionality or performance.
Choose AMD EPYC shapes where workload requirements allow. BM.DenseIO.E4.128 (128 physical cores at 0.5 factor = 64 Processor licenses) provides roughly twice the raw compute of Intel Xeon shapes for the same license count. High-NVMe storage directly on the bare metal eliminates the need for additional Oracle storage software options in many I/O-intensive configurations.
Oracle's Support Rewards program returns up to 33% of OCI consumption spend as credits against Oracle Annual Support costs. For enterprises with large Oracle Database EE bare metal BYOL deployments, this creates a feedback loop: OCI infrastructure spending reduces Oracle support bills, making BYOL on OCI even more commercially attractive. Our Support Rewards guide covers the mechanics and optimization approach in detail.
Enterprises migrating on-premise Oracle Database workloads to OCI bare metal frequently over-provision the initial bare metal shape based on on-premise server specifications rather than actual workload utilization. A comprehensive workload analysis before shape selection routinely identifies opportunities to deploy on a smaller shape — reducing both the Oracle Processor license requirement and the OCI infrastructure cost. This is the highest-ROI activity in any OCI Database migration planning exercise.
Oracle Database Standard Edition 2 on OCI bare metal is limited to 16 physical cores (8 OCPU per instance maximum) and does not support RAC on OCI. However, SE2's significantly lower license cost — roughly 20% of Enterprise Edition per Processor — makes it economically compelling for Oracle Database workloads that do not require Enterprise Edition options. The SE2 assessment should always be part of OCI Database migration planning for workloads not dependent on EE-only features.
We advised an energy company migrating 40 Oracle Database EE instances to OCI bare metal. Right-sizing analysis reduced their Processor license requirement by 35%, and BYOL application cut infrastructure costs by 52% versus maintaining on-premise. Read the full case study.
Practical Oracle licensing analysis — audit trends, negotiation benchmarks, and cloud strategy updates for enterprise buyers. No Oracle spin.
Unsubscribe anytime. No Oracle affiliation.
Our Oracle Cloud Advisory team maps your existing license portfolio against OCI bare metal shapes, calculates exact BYOL entitlement requirements, and identifies optimization opportunities before you commit to infrastructure spend. Former Oracle insiders — not affiliated with Oracle.
Related Resources