OCI Compute Licensing: Shapes, OCPUs and Tiers

How OCI shapes drive licensing

On OCI, a shape is the compute template that defines how many OCPUs and how much memory an instance receives, and the OCPU count of that shape is the number that drives Oracle licensing. Because one OCPU equals one Enterprise Edition processor licence, as set out in OCPU versus vCPU, choosing a shape is choosing a licence requirement. A four OCPU shape needs four processor licences under BYOL; an eight OCPU shape needs eight. The shape is the lever, and sizing it deliberately is the first cost control in the Oracle OCI licensing model.

This is a sharper relationship than on premise, where servers come in fixed core counts and the core factor blurs the link between hardware and licences. On OCI the link is direct and linear: every OCPU you allocate is a licence you must hold or a per OCPU rate you must pay. There is no core factor to soften it. That directness is an advantage for the disciplined buyer, because right sizing the shape produces an immediate, predictable licence saving.

The directness also makes forecasting cleaner. Because each OCPU is exactly one licence, a capacity plan expressed in OCPUs translates one to one into a licence plan and a cost plan, with no core factor table to interpret. Finance and architecture can work from the same number, which removes a common source of disagreement between the team that sizes the infrastructure and the team that owns the Oracle contract. Naming OCPUs as the shared planning unit aligns both functions on a single figure.

Flexible shapes and precise sizing

OCI flexible shapes let you specify the exact OCPU count rather than choosing from fixed sizes, and this granularity is a genuine licensing lever. Where a legacy fixed shape might force you to a power of two, a flexible shape lets you provision the precise number of OCPUs the workload needs, so you licence exactly that and no more. A database that genuinely needs six OCPUs can run on six rather than being rounded up to eight, saving two processor licences outright.

The discipline is to size for steady state and scale deliberately, not to over provision against a worst case. Because OCPUs map one to one to licences, an over sized shape is an over licensed workload paying for cores it rarely uses. The cleaner pattern for spiky workloads is a service that scales on consumption, discussed under Autonomous Database.

Flexible shapes also enable a genuine scale to zero pattern for non production. A development or test database can be sized small, scaled up only for a load test, and scaled back afterwards, with the BYOL entitlement checked against the brief peak rather than carried at the peak all year. Where the peak is rare and short, License Included on the same flexible shape may be cheaper still, because it bills the burst by the hour rather than requiring entitlement to sit idle between tests.

BYOL or License Included for compute?

For any OCI compute shape running a database, the licensing model is either BYOL, where you supply owned licences and pay a reduced infrastructure rate, or License Included, where Oracle bundles the licence into a higher per OCPU hourly rate. The shape is the same; only the billing election differs. BYOL suits stable workloads where you hold spare supported licences; License Included suits new or variable workloads where you would otherwise have to buy.

The two decisions are independent and both matter. You first size the shape to the workload, then choose the model that is cheaper for that workload over its life. A common error is to fix the model first, by policy, and then accept whatever licence cost the shape implies. The better sequence is to size, then price both models, then elect. The break even between the two is worked in License Included.

How options change the compute cost

The compute shape sets the base database licence, but options and packs ride on top of the same OCPU count, so they multiply the per OCPU cost. Under BYOL, each option enabled across the shape needs its own per OCPU entitlement. Under License Included, options come bundled in the High Performance and Extreme Performance tiers, which carry a higher per OCPU rate than the base Enterprise Edition tier. Either way, the option decision is a per OCPU decision, so it scales with the shape.

This is why shape sizing and option selection must be considered together. A large shape with the Extreme Performance tier is paying the top per OCPU rate across every core, so trimming two unnecessary OCPUs saves not just two base licences but the option premium on those cores as well. The full option mechanics are in OCI database options, and they compound directly with the compute decision here.

Bare metal and dedicated shapes

Bare metal shapes give a full physical server with no hypervisor, and they are licensed on the full physical OCPU count of the machine, not on a sub allocation. This removes any partitioning argument: you licence every core in the box. Dedicated VM hosts behave similarly, because you control the whole host. For a buyer, the implication is that bare metal is only economic when you genuinely use most of the cores, since you cannot licence a fraction of the server.

The contrast with flexible VM shapes is the key planning point. Flexible shapes let you licence exactly the OCPUs you allocate; bare metal commits you to the whole machine. Workloads that need isolation or maximum performance justify bare metal, but most database workloads are better served by a right sized flexible shape that licences only what it uses. The dedicated infrastructure question recurs in Exadata Cloud Service.

What happens to licensing when you scale?

Scaling a shape changes the OCPU count, and under BYOL that immediately changes the licence requirement. Scaling up from four to eight OCPUs doubles the processor licences you must hold for that workload, at the instant the scale takes effect. OCI lets you scale without checking entitlement, so a scale up event can move a compliant workload into shortfall silently. Scaling down releases the requirement, but only while the smaller shape is in force.

The governance control is to treat any BYOL scale up as a licence event that must be checked against held entitlement before it is actioned, and to cap automated scaling at the licensed ceiling. Where a workload genuinely needs to scale freely, License Included removes the entitlement question because Oracle meters the OCPUs and charges accordingly. Choosing the model to match the scaling pattern is the heart of cloud and OCI licensing advisory.

How to optimise compute cost

Compute optimisation on OCI is a short list applied consistently. Right size every shape to steady state demand using flexible OCPU counts. Choose the licensing model per workload after pricing both. Select the minimum sufficient option tier under License Included. Cap autoscaling at the licensed ceiling under BYOL. And reconcile the running OCPU total against entitlement so scaling never outruns licences. Each control is small; together they typically remove a fifth or more of an unmanaged OCI database bill.

The reconciliation is the load bearing control, because it is the one that turns a set of good intentions into a defensible position. A dated record of every shape, its OCPU count, the model elected, and the entitlement consumed is what an audit reads as governance. Building and maintaining it is the practical work the database licensing practice performs alongside the cloud desk.

One further saving is often overlooked: aligning the database edition to the workload. A small departmental database forced onto Enterprise Edition because that is what the estate standardised on carries the full per OCPU Enterprise cost, when Standard Edition 2 with its more generous cloud mapping might cover it for a fraction. Reviewing edition alongside shape size, rather than treating edition as fixed, frequently surfaces the largest single line of compute saving on an estate.

The buyer side view

On OCI the shape sets the licence count, one OCPU to one Enterprise Edition processor licence, with no core factor to soften it. Size shapes precisely using flexible OCPUs, choose BYOL or License Included per workload after pricing both, pick the minimum sufficient option tier, and cap autoscaling at the licensed ceiling. Keep a dated reconciliation of OCPUs against entitlement so scaling never creates a silent shortfall. To right size and re model your OCI compute estate, request a consultation.