Oracle on GCP Bare Metal: Licensing Rules

Does Oracle's Authorized Cloud Policy Apply to GCP Bare Metal?

No — and this is the most expensive misunderstanding buyers carry into a bare-metal deployment. Oracle's Authorized Cloud Environment policy, with its favourable rule of two vCPUs per Processor licence, applies only to recognized virtualized public cloud services such as standard GCP Compute Engine VMs, AWS EC2, and Azure VMs. Bare-metal infrastructure — whether GCP's Bare Metal Solution or any dedicated single-tenant physical server — exposes the underlying physical processors directly to the customer.

Because Oracle can see physical cores, it treats bare metal the way it treats hardware in your own data centre: the on-premise rulebook governs. That means the Core Factor Table applies, the full physical core count is in scope, and the cloud vCPU concession is off the table. An Oracle rep who quotes bare metal using the 2:1 cloud rule is either mistaken or optimistic — verify the licensing model in writing before you sign. The Oracle Cloud Licensing Guide sets out exactly which deployments qualify as authorized clouds and which do not.

How Are Oracle Cores Counted on GCP Bare Metal?

On bare metal, Oracle counts every physical core in the server and multiplies by the Core Factor Table value for that processor type. For Intel and AMD x86 processors the factor is 0.5, so a server with 56 physical cores requires 28 Oracle Processor licences for Database Enterprise Edition. The count is based on the hardware, not on utilization — Oracle does not care whether your database touches four cores or fifty-four; if the cores are physically present and the software can run on them, they are licensable.

This is the heart of the bare-metal cost problem. Cloud VMs let you provision exactly the vCPUs you need; bare-metal servers come in fixed physical configurations, and you license the whole box. Choosing a bare-metal shape with more cores than the workload requires is the single most common way enterprises over-buy Oracle licences on Google Cloud.

Can I Use BYOL for Oracle on GCP Bare Metal?

Yes. BYOL (Bring Your Own License) applies to bare-metal compute exactly as it does elsewhere, with one non-negotiable caveat: you must license the full physical core count of the server using the Core Factor Table, not the cloud vCPU rule. The licences must be on active Oracle support, and any on-premise instance the licences were moved from must be retired — BYOL is never a "use twice" benefit, and Oracle's GLAS team specifically tests for concurrent on-premise and bare-metal use of the same entitlement.

The discipline here is to count the licences you hold first, then choose a bare-metal configuration whose physical core count, after the Core Factor, fits inside that pool. Provisioning the hardware first and reconciling licences later is how a clean migration becomes a back-licence claim. Our Oracle compliance review service verifies the bare-metal entitlement position before deployment, so the gap is closed before Oracle can find it.

Can Hard Partitioning Reduce Oracle Licensing on Bare Metal?

Only with an Oracle-approved hard partitioning technology, and only if it is documented and verifiable. Oracle recognizes a narrow list of approved hard partitioning methods — such as Oracle Linux KVM with hard-partition configuration, Solaris Zones with capped resources, and certain physical-domain technologies — that can limit the licensable core count to the partition rather than the whole server. Soft partitioning — VMware, generic KVM without the approved configuration, and most hypervisors — does not reduce the count in Oracle's view; you license the entire physical machine.

On GCP bare metal, the practical reality is that you usually license the whole server unless you implement and document an approved hard partition. The mistake we see most often is a customer assuming their hypervisor caps the licensable cores, then facing a claim for the full box during an audit. If you intend to rely on hard partitioning, the configuration must be designed to Oracle's published specification and evidenced — exactly the forensic detail our Oracle Database licensing guide documents in full.

Bare Metal vs Standard GCP VMs: Which Is Cheaper to License?

For Oracle workloads, standard GCP VMs are usually cheaper to license than bare metal for the same compute, because VMs qualify for the 2-vCPUs-per-licence cloud rule while bare metal is counted on physical cores. The infrastructure price of bare metal can look attractive in isolation, but the Oracle licence bill frequently swings the total cost of ownership the other way. The decision must be made on the combined hardware-plus-licence cost, not the GCP rate card alone.

There are legitimate reasons to choose bare metal — latency-sensitive workloads, specific certification requirements, or applications that cannot run virtualized — but "it felt cheaper" is not one of them. Across our engagements, buyers who modelled the two options against each other before committing avoided an average licence over-spend of more than 40% on the same workload (Oracle Licensing Experts, 2026). See the energy-sector cloud migration case study for how shape selection drove a multi-million-dollar swing in licence cost.

What Triggers an Oracle Audit on GCP Bare Metal?

The triggers mirror those for any cloud deployment: a reduction in on-premise support that suggests workloads moved, a support ticket referencing bare-metal hosts, a sales conversation that surfaces the deployment, or a ULA certification where bare-metal cores appear understated. Once Oracle suspects bare-metal usage, the LMS or GLAS team requests the physical configuration — core counts, processor type, and partitioning evidence — under the audit clause in your Master Agreement.

The defensible posture is documentary: keep a current record of every bare-metal server running Oracle, its full physical core count, the Core Factor applied, any approved hard partition with its configuration evidence, and the entitlement covering it. Our Oracle audit defense service challenges Oracle's core-counting and partitioning conclusions line by line, and the broader framework lives in the Oracle audit defense guide.

Frequently Asked Questions