Short answer: Oracle licensing on Google Cloud follows Oracle's authorized public cloud policy, not the on-premise Core Factor Table. On GCP with hyper-threading enabled, two vCPUs count as one Oracle Processor licence. You can use BYOL for Database, options, WebLogic and Java if those licences stay on active Oracle support.
Key Takeaways
- Google Cloud is a recognized Oracle public cloud, so the cloud vCPU rule applies — 2 vCPUs = 1 Processor licence where hyper-threading is on; 1 vCPU = 1 licence where it is off.
- The on-premise Core Factor Table (0.5 for x86) does not apply on GCP — do not let an Oracle rep quietly apply it to inflate or deflate your count.
- Oracle Database SE2 is capped at 8 vCPUs per instance on authorized clouds including GCP; exceeding it is a top compliance finding.
- BYOL on GCP requires licences on active Oracle support (22% of net licence value annually) — third-party support forecloses BYOL.
- Across our engagements, GCP migrations that size shapes to the licence count rather than the workload cut Oracle Processor consumption by an average of 30–40% (Oracle Licensing Experts, 2026).
- An idle Diagnostics or Tuning Pack on a GCP Database instance is licensable the moment it is accessed — the same trap that exists on-premise follows you to the cloud.
Is Google Cloud an Oracle Authorized Cloud Environment?
Yes. Google Cloud Platform is named in Oracle's Licensing Data Recognized (Authorized) Public Cloud Environments policy document, alongside Amazon Web Services and Microsoft Azure. An Authorized Cloud Environment is a public cloud that Oracle has formally designated as eligible for its cloud-specific licensing rules — which means a different counting method applies than the one you use in your own data centre. This single fact governs everything else about Oracle licensing on Google Cloud: because GCP is authorized, Oracle's cloud vCPU rule applies and the on-premise Core Factor Table is explicitly excluded.
This matters because Oracle's policy document is not a contract — it is a unilateral policy Oracle can revise. The buyer-side discipline is to capture the version of the policy in force at the time of your deployment and tie your compliance position to it. We have seen Oracle reps reference whichever version of the rules produces the larger licence count; the Oracle Cloud Licensing Guide sets out the full hierarchy of which document wins when policy and contract disagree.
How Does Oracle Count vCPUs on Google Cloud?
On Google Cloud, Oracle counts licences by vCPU under its authorized cloud policy. Where hyper-threading is enabled on the underlying compute — the default for most GCP machine types — Oracle treats two vCPUs as one Oracle Processor licence. Where hyper-threading is not enabled, each vCPU equals one Processor licence. A GCP n2-standard-16 instance with 16 vCPUs and hyper-threading on therefore requires eight Oracle Processor licences for Database Enterprise Edition.
The critical point Oracle's account team will not volunteer: the Core Factor Table does not apply on GCP. On-premise, an x86 core carries a 0.5 core factor, so 16 cores equal eight Processor licences — coincidentally the same number. But the mechanisms are different, and on shapes with different hyper-threading behaviour the numbers diverge fast. Never let a quote blend the two rulebooks; insist on the cloud vCPU method, in writing, for any GCP workload.
| GCP Machine Type | vCPUs | Hyper-threading | Oracle Processor Licences |
|---|---|---|---|
| n2-standard-8 | 8 | Enabled | 4 |
| n2-standard-16 | 16 | Enabled | 8 |
| n2-standard-32 | 32 | Enabled | 16 |
| c3-standard-8 (no SMT) | 8 | Disabled | 8 |
| n2-standard-8 (SE2) | 8 | Enabled | SE2 socket-equivalent cap reached |
Can I Use BYOL for Oracle on Google Cloud?
Yes. BYOL (Bring Your Own License) is Oracle's program that lets you apply existing perpetual on-premise licences to a public cloud deployment instead of buying cloud-included licensing. On Google Cloud Compute Engine you can BYOL Oracle Database Enterprise Edition, Database options (RAC, Partitioning, Advanced Security, Diagnostics Pack, Tuning Pack), WebLogic Server, and Java SE — provided two conditions hold: the licences are on active Oracle support, and the same licences are not simultaneously covering an on-premise deployment they were moved from.
BYOL is not a "use twice" benefit. If you move a Database EE licence to GCP, the on-premise instance that previously consumed it must be retired. Oracle's compliance reviews specifically test for concurrent on-premise and cloud use of the same entitlement — one of the cleanest back-licence claims Oracle can build. Our Oracle compliance review service verifies the BYOL entitlement pool before migration, so the gap is closed before Oracle's GLAS team can find it.
Planning an Oracle migration to Google Cloud?
Our Oracle Cloud advisory service right-sizes GCP shapes to your licence count and verifies BYOL entitlements before you deploy — not after the audit notice.
What Are the Oracle Standard Edition 2 Rules on GCP?
Oracle Database SE2 carries a hard cloud cap that catches many GCP buyers. On authorized public clouds, Oracle's policy limits an SE2 instance to a maximum of eight Amazon vCPUs or equivalent — interpreted as eight GCP vCPUs per instance. SE2 is also limited to a single database instance with up to 16 threads, and licensing is by the socket-equivalent rule rather than per-core. Provision an SE2 instance on a GCP shape larger than eight vCPUs and you are out of compliance the moment the instance starts.
The trap is that GCP makes it trivially easy to resize a VM upward. A DBA scaling a busy SE2 instance from n2-standard-8 to n2-standard-16 for a quarter-end load has just created a licence breach without buying anything. SE2 deployments on GCP need a change-control guardrail, not just an initial sizing decision — exactly the kind of forensic detail our Oracle Database licensing guide documents in full.
What Triggers an Oracle Audit on Google Cloud?
Oracle does not need agents inside your GCP project to know you are running its software there. The most common triggers are commercial signals Oracle already holds: a lapse or reduction in on-premise support that suggests workloads moved; a support ticket referencing a cloud host; a sales conversation where GCP is mentioned; or a ULA certification where cloud deployments appear understated. Once Oracle suspects cloud usage, the LMS or GLAS team requests deployment data under the audit clause in your Master Agreement.
The defensible posture is evidence-based: maintain a current record of every Oracle instance on GCP, the vCPU count, the hyper-threading state, the options installed, and the entitlement covering it. When Oracle asks, you respond with a reconciled position rather than scrambling. Our Oracle audit defense service challenges Oracle's cloud measurement methodology line by line, and the energy-sector cloud migration case study shows how a reconciled entitlement position cut a seven-figure claim to zero.
Oracle's cloud policy is deliberately published as a policy, not embedded in your contract — so Oracle can change the counting rules without renegotiating with you. Always anchor your GCP compliance position to the policy version in force when you deployed, keep a dated copy, and push back hard if a rep applies a newer, less favourable interpretation retroactively.
Oracle Java and WebLogic Licensing on Google Cloud
Oracle Java SE on GCP is licensed under the same Employee metric that applies everywhere else: the subscription is priced by total employee headcount, not by the number of vCPUs running Java. Moving Java workloads to GCP does not reduce the Java bill — only removing Oracle JDK from your estate, or proving you never needed the commercial subscription, does. The Java SE Employee Metric routinely costs 5–10× more than the legacy Named User Plus model for the same deployment, which is why Java is the single fastest-growing audit vector we see.
WebLogic Server on GCP follows the Processor vCPU rule, but watch the bundled options: WebLogic Suite includes Coherence and other components that are separately measured, and a WebLogic instance often pulls in Java SE entitlement obligations. Treat any GCP WebLogic deployment as a multi-product licensing question, not a single line item. See our Oracle Java licensing guide for the full Employee-metric framework.
How to Right-Size Oracle Licensing on Google Cloud
The discipline that protects buyers is simple to state and hard to enforce without governance: let the licence count drive the shape, not the other way around. Decide how many Oracle Processor licences you are willing to commit, then choose GCP machine types whose vCPU count, after the 2:1 rule, lands inside that envelope. Disable hyper-threading only when the maths genuinely favours it, isolate Oracle workloads onto dedicated projects so usage is auditable, and turn off every Database option you are not licensed to use.
Across our GCP engagements, customers who applied this licence-first sizing reduced Oracle Processor consumption by an average of 30–40% versus their initial workload-first design (Oracle Licensing Experts, 2026). The savings come not from a clever contract clause but from refusing to over-provision compute that Oracle then bills as licences.
Frequently Asked Questions
Is Google Cloud an Oracle Authorized Cloud Environment?
Yes. Google Cloud Platform is named in Oracle's Licensing Data Recognized Public Cloud Environments policy alongside AWS and Microsoft Azure. This means Oracle's cloud-specific vCPU counting rules apply to GCP — not the on-premise Core Factor Table — for products licensed by Processor.
How does Oracle count vCPUs on Google Cloud?
On Google Cloud, where hyper-threading is enabled, Oracle counts two vCPUs as one Oracle Processor licence. Where hyper-threading is not enabled, each vCPU equals one Processor licence. The on-premise Core Factor Table does not apply on authorized public clouds, so the 0.5 multiplier for x86 cores is irrelevant on GCP.
Can I use BYOL for Oracle on Google Cloud?
Yes. You can bring existing perpetual Oracle Database, options, WebLogic and Java licences to Google Cloud Compute Engine under BYOL, provided the licences are on active Oracle support and you count vCPUs under the authorized cloud policy. BYOL licences cannot simultaneously cover the on-premise deployment they were moved from.
Does Oracle Standard Edition 2 work on Google Cloud?
Yes, but with a hard limit. On authorized public clouds including GCP, an Oracle Database SE2 instance may use a maximum of eight vCPUs per instance. Exceeding the socket-equivalent cap — easy to do when resizing a GCP VM upward — is one of the most common SE2 compliance findings.
Is Oracle on Google Cloud cheaper to license than on-premise?
It can be, because the 2-vCPU-per-licence cloud rule is often more favourable than the on-premise Core Factor for the same workload. But savings evaporate if you over-provision vCPUs, leave the Diagnostics Pack enabled, or run Oracle on shapes that count more licences than your entitlement covers. The licence math must drive shape selection.
Do I still pay Oracle support for licences I BYOL to GCP?
Yes. BYOL requires licences to remain on active Oracle support, which costs 22% of net licence value annually. Enterprises that moved to third-party support to cut that fee cannot use those same licences for BYOL on Google Cloud — the two strategies are mutually exclusive and must be modelled against each other.