Oracle Core Factor Table – The Definitive License Calculator Guide

1. What Is the Oracle Core Factor Table?

Oracle's Core Factor Table is an official reference document that assigns a specific multiplier (core factor) to every processor type on the market. That multiplier determines how many Oracle processor licenses you need for a given number of physical CPU cores. It is, in practical terms, the single most important variable in your Oracle licensing cost equation.

The concept exists because not all CPU cores deliver the same throughput. Oracle designed the core factor to normalise licensing across different hardware architectures — so a high-performance RISC core and a commodity x86 core are not treated identically. The result is a sliding scale of factors, typically ranging from 0.25 to 1.0, where a lower factor means fewer licenses per core (and lower cost).

For a broader view of Oracle's licensing mechanics, see our Oracle Database Licensing Models guide.

Key characteristics of the Core Factor Table:

Scope of application. The core factor applies exclusively to Oracle products licensed on a processor metric — principally Oracle Database Enterprise Edition, WebLogic Server, middleware suites, and other technology products. It does not apply to Standard Edition 2 (which uses per-socket licensing) or to products licensed by Named User Plus, Application User, or other metrics. For more on Oracle license types, see our detailed guide.

Official publication. Oracle publishes and periodically updates the Core Factor Table on its website. When new processor families launch, Oracle adds entries. Until a processor is listed, Oracle's default policy is to treat each core as 1.0 — the maximum factor.

On-premises focus. The core factor table is designed for physical, on-premises hardware. Cloud environments follow separate rules (covered in Section 7). However, understanding core factors remains essential even in hybrid architectures because BYOL calculations often reference processor-equivalent counts.

2. How the Core Factor Calculation Works

The core factor calculation is mathematically simple but operationally critical. Every licensing assessment in an Oracle estate begins with this formula:

That single equation governs hundreds of millions of dollars in global Oracle licensing spend. Let's break it down step by step.

Step 1 — Count physical cores. Identify the total number of physical CPU cores on each server running Oracle software. This means actual cores, not threads. Hyper-threading (Intel) or SMT (AMD/IBM) creates logical threads, but Oracle counts physical cores only. A 2-socket server with 16-core CPUs has 32 physical cores.

Step 2 — Identify the core factor. Look up your processor model in Oracle's official Core Factor Table. Intel Xeon and AMD EPYC are 0.5. IBM POWER9/10 is 1.0. Oracle SPARC M8 is 0.5. Oracle Ampere (ARM) is 0.25.

Step 3 — Multiply and round up. Multiply total physical cores by the core factor. If the result is a fraction, always round up to the next whole number. Oracle licenses are sold in whole units only.

Step 4 — Apply per product. The license calculation applies independently to each Oracle product installed on that server. If you run Oracle Database Enterprise Edition plus three options (Partitioning, Diagnostics Pack, Tuning Pack), each requires the same number of processor licenses. This multiplicative effect is where costs escalate rapidly.

3. Complete Core Factor Reference by Processor Family

The following table summarises core factors for the most common enterprise processor families. Always verify against Oracle's latest official publication, as new processors are added periodically.

4. Cost Impact: How Core Factors Swing Your Oracle Bill

The core factor's financial impact is direct and dramatic. Since Oracle Database Enterprise Edition lists at $47,500 per processor license, every fractional difference in the core factor translates to tens or hundreds of thousands of dollars — and that's before options and annual support.

Comparative Cost Analysis: Same Workload, Different Hardware

Consider a standard database server with 2 sockets × 16 cores = 32 physical cores, running Oracle Database Enterprise Edition with Partitioning and Diagnostics Pack:

The same 32-core server costs $532K on ARM, $1.06M on Intel, and $2.13M on IBM POWER — a 4× range driven entirely by the core factor. And this analysis covers just one server. Enterprises with dozens of Oracle database servers face cumulative differences measured in the tens of millions.

Annual Support Amplifies the Difference

Oracle charges 22% of list license fees annually for Technical Support. This compounds the core factor's impact year after year. For the 32-core Intel server above, annual support is approximately $234,000. For the IBM POWER equivalent, it's $468,000 — an extra $234K every year for the same application. Over a typical 10-year hardware lifecycle, support costs can exceed the initial license investment.

For strategies to reduce support spend, see our Oracle Support Renewal Optimization guide.

5. Step-by-Step License Calculator with Worked Examples

Example 1: Standard x86 Database Server

Example 2: IBM POWER Server

Example 3: Rounding Up with Odd Core Counts

6. The Virtualization Trap: Soft vs. Hard Partitioning

Virtualization is where the core factor calculation becomes dangerous. The formula itself does not change, but the definition of which cores to count expands dramatically depending on your virtualization technology.

Soft Partitioning = Full Host Licensing

Oracle classifies most mainstream virtualization technologies as "soft partitioning" — meaning they do not limit your licensing requirement. Under Oracle's policy, you must license all physical cores on every host in the cluster where the Oracle VM can potentially run.

Technologies Oracle considers soft partitioning include: VMware vSphere/ESXi, Microsoft Hyper-V, KVM (when using live migration), Citrix XenServer, and most other commercial hypervisors.

For detailed guidance on VMware environments, see our Oracle Licensing in VMware guide. For Hyper-V, see Oracle Licensing on Hyper-V.

Hard Partitioning = Subset Licensing

Oracle recognises certain partitioning methods that do legally limit your licensing requirement to a subset of cores. These "hard partitioning" technologies include:

Using hard partitioning effectively can reduce your Oracle licensing footprint by 80–90% compared to soft partitioning. However, the configuration must be documented rigorously — Oracle auditors will verify that VMs are truly pinned and cannot migrate to unlicensed hosts.

7. Cloud Licensing Rules: AWS, Azure, OCI

In cloud environments, Oracle replaces the traditional Core Factor Table with platform-specific vCPU conversion rules. Understanding these rules is essential for enterprises pursuing cloud migration or hybrid architectures.

For comprehensive cloud licensing guidance, see our Oracle Licensing in Public Cloud Environments guide.

AWS and Azure (Authorised Cloud Providers)

Oracle treats AWS and Azure as "authorised cloud environments" with a specific conversion: 2 vCPUs = 1 Oracle Processor License. This applies to hyper-threaded instances (which most are). For instances without hyper-threading, each vCPU equals one full processor license.

The traditional Core Factor Table does not apply in AWS/Azure. Instead, you count vCPUs and divide by 2. Example: an AWS r6i.4xlarge instance with 16 vCPUs requires 16 ÷ 2 = 8 Oracle processor licenses under BYOL.

Oracle Cloud Infrastructure (OCI)

On OCI, Oracle offers two licensing models: License Included (Oracle licenses bundled into the cloud service price) and Bring Your Own License (BYOL). Under BYOL, 1 OCPU (Oracle Compute Unit) = 1 Oracle processor license. OCI's pricing is designed to make BYOL attractive, especially through programmes like Oracle Support Rewards.

For Ampere (ARM) instances on OCI, 1 OCPU = 1 physical core with a 0.25 core factor equivalent, making ARM instances the most license-efficient option in Oracle's cloud.

Cloud Licensing Comparison Table

8. Common Pitfalls and Misconceptions

Even with a straightforward formula, organisations routinely miscalculate Oracle core factor licensing. These are the most dangerous mistakes we see across enterprise engagements:

Pitfall 1: Assuming VM vCPUs Limit License Scope

This is the most expensive mistake in Oracle licensing. As detailed in Section 6, allocating 4 vCPUs to an Oracle VM on a VMware host does not mean you need only 4 × 0.5 = 2 licenses. Under Oracle's soft partitioning policy, you must license every physical core on every host in the vMotion-enabled cluster. A 4-vCPU VM on a 10-host cluster can generate a licensing requirement 50 times larger than expected.

Pitfall 2: Confusing Threads with Cores

Oracle counts physical cores, not logical threads. Intel Hyper-Threading and AMD SMT double the apparent CPU count in operating system tools, but Oracle ignores these logical threads for licensing purposes. A server reporting 64 logical CPUs in the OS may have only 32 physical cores. Always verify physical core counts through hardware documentation or BIOS settings, not software utilities.

Pitfall 3: Using Outdated Core Factor Data

Oracle periodically updates the Core Factor Table as new processor families are released. Using stale data can cause under-licensing (if a new processor has a higher factor than assumed) or over-licensing (if Oracle has assigned a favourable factor you haven't captured). Always reference the latest official table directly from Oracle's website.

Pitfall 4: Forgetting License Minimums

If you license Oracle Database Enterprise Edition by Named User Plus, there is a minimum of 25 NUP licenses per processor (as calculated using the core factor). This minimum can force higher license counts than your actual user population warrants. Cross-check your NUP requirements against the processor license calculation to determine which metric is more cost-effective.

Pitfall 5: Standard Edition vs. Enterprise Edition Confusion

Oracle Standard Edition 2 uses per-socket licensing and does not use the Core Factor Table. Each occupied socket counts as one license, regardless of core count. Enterprises migrating from Standard Edition to Enterprise Edition often underestimate the cost increase because the licensing metric shifts from sockets to cores × factor. Plan for this transition carefully.

Pitfall 6: Ignoring Disabled or Decommissioned Servers

Oracle auditors will look for evidence of Oracle software on any server — including development, test, staging, and disaster recovery environments. An old server with Oracle installed but "not in production" still requires licensing. Ensure your asset inventory is complete and that decommissioned servers have Oracle software fully removed.

9. Strategies to Optimise License Costs

The core factor table is not just a compliance tool — it's a strategic lever. Enterprises that manage it proactively can generate substantial savings.

Strategy 1: Hardware Selection Aligned to Licensing

Always evaluate Oracle licensing cost before finalising hardware procurement. Choosing commodity x86 (factor 0.5) over IBM POWER (factor 1.0) halves the Oracle license requirement for the same core count. In some cases, the licensing savings from a hardware platform change exceed the entire hardware investment. Run the Oracle price calculation as part of every server procurement decision.

Strategy 2: Core Reduction and Right-Sizing

Some enterprises deliberately disable CPU cores in BIOS to reduce their Oracle licensing footprint. This is legitimate and Oracle-recognised, provided the disabled cores cannot be re-enabled without physical intervention. Additionally, right-sizing servers — using smaller, purpose-built machines for Oracle workloads instead of large shared servers — can reduce the total core count subject to licensing.

Strategy 3: Hard Partitioning for Virtualized Environments

If you must run Oracle on virtualized infrastructure, use Oracle-approved hard partitioning. Migrate Oracle VMs to Oracle VM Server (OVM), Oracle Linux KVM, or dedicated physical hosts. The upfront effort of re-platforming can eliminate 80–90% of your virtual licensing exposure compared to VMware or Hyper-V.

Strategy 4: Workload Consolidation

Consolidating multiple Oracle databases onto fewer, right-sized servers can reduce the total core count and therefore the total license requirement. However, balance this against the risk of creating large servers with high core counts. The optimal approach is typically moderate-sized dedicated Oracle hosts rather than either large shared clusters or many small servers.

Strategy 5: Edition Downgrades

If your workload does not require Enterprise Edition features (RAC, Partitioning, Advanced Security, etc.), downgrading to Standard Edition 2 eliminates the core factor entirely. SE2 is licensed per socket (maximum 2 sockets), and the list price is $17,500 per socket vs. $47,500 per core-factor-adjusted license. For workloads with moderate requirements, the savings are dramatic.

Strategy 6: Evaluate Alternative Licensing Models

For large Oracle estates, a ULA (Unlimited License Agreement) may cap costs during a defined period. A ULA allows unlimited deployment of specified products for a fixed annual fee. At ULA certification, deployed licenses are counted and become perpetual entitlements. This can be cost-effective for rapidly growing environments where core-factor-based procurement would escalate annually.

Strategy 7: Engage Independent Advisors

Oracle licensing is high-stakes and complex. Independent advisors like Redress Compliance provide objective analysis of your licensing position, identify optimisation opportunities, and defend against audit over-claims. Our Oracle Cost Optimization Playbook provides a comprehensive framework for reducing Oracle spend across licensing, support, and cloud.

10. 10-Point Compliance Checklist

Follow this governance checklist to ensure your Oracle core factor licensing is accurate, compliant, and cost-optimised:

1. 1 Inventory all Oracle servers. Compile a complete list of every physical server and VM host where Oracle software is installed or can run — including dev, test, staging, and DR. Record CPU model, socket count, and physical core count for each.
2. 2 Look up core factors. Obtain Oracle's latest Core Factor Table and match each server's processor to its official factor. If any processor is unlisted, assume 1.0 and verify with Oracle.
3. 3 Calculate license requirements per product. For each Oracle product, compute: physical cores × core factor = required licenses. Remember to calculate separately for each product and option/pack.
4. 4 Assess virtualization exposure. Identify all VMware, Hyper-V, and other soft-partitioned environments. Calculate the full-cluster licensing requirement (all physical cores on all accessible hosts). Compare against hard-partitioning alternatives.
5. 5 Compare with current entitlements. Cross-reference your calculated requirements against your purchased Oracle license entitlements. Identify any shortfall or surplus by product and metric.
6. 6 Model cloud licensing equivalents. For any cloud or hybrid workloads, calculate the vCPU-based license requirement separately using cloud-specific rules (2 vCPUs = 1 license on AWS/Azure; 1 OCPU = 1 license on OCI).
7. 7 Evaluate NUP vs. processor economics. For products with moderate user counts, compare the cost of Named User Plus vs. Processor licensing. NUP may be cheaper for small user populations; processor may be cheaper for large or unpredictable user bases.
8. 8 Review options and packs. Audit which Oracle options and management packs are actually enabled (check DBA_FEATURE_USAGE_STATISTICS). Disable any that are not operationally required — each enabled option multiplies your license cost by the full processor count.
9. 9 Document everything. Maintain auditable records of all calculations, hardware configurations, virtualization settings, and core factor references. This documentation is your primary defence in an Oracle audit.
10. 10 Engage independent advisors. Before major hardware refreshes, cloud migrations, or Oracle contract renewals, engage independent licensing experts to validate your position and identify optimisation opportunities. See our Oracle License Management Services.

11. Frequently Asked Questions

Our Oracle Advisory Services

Vendor-independent. Fixed-fee. Proven results across hundreds of Fortune 500 engagements.