How the Core Factor Table Works, Why It Determines Your Oracle Licensing Costs, The Complete Calculation Methodology with Worked Examples, Core Factors by Processor Family, The Virtualisation Trap That Multiplies Licence Requirements, How Core Factors Apply in Cloud and ULA Scenarios, Common Audit Findings from Miscalculation, and the Governance Framework That Keeps You Compliant
Oracle's Processor Core Factor Table is the official reference that determines how many Oracle processor licences an organisation requires for any given server. It assigns a multiplier (the 'core factor') to each processor family, which is applied to the physical core count to calculate the number of Oracle licences needed. The core factor ranges from 0.25 (most favourable — Oracle's Ampere ARM processors) to 1.0 (least favourable — IBM POWER), with most enterprise x86 processors (Intel Xeon, AMD EPYC) at 0.5.
This single variable — the core factor — can double or halve your Oracle licensing costs for identical workloads. An 8-core IBM POWER server requires 8 processor licences ($380,000 at Database EE list price), while the same 8-core Intel server requires only 4 ($190,000). Hardware selection, virtualisation strategy, and core factor awareness are therefore fundamental to Oracle cost management.
For the broader context of Oracle's licensing metrics and how processor licensing interacts with Named User Plus, see Oracle License Metrics & Definitions. For detailed NUP vs Processor selection guidance, see Named User Plus vs Processor: Which to Choose. For the complete Oracle ULA framework (where core factor counting is critical during certification), visit our Oracle ULA guide.
| Processor Family | Core Factor | 8-Core Licence Requirement | Cost at DB EE List ($47,500/licence) | Relative Cost |
|---|---|---|---|---|
| Oracle Ampere ARM (Altra) | 0.25 | 2 licences | $95,000 | Baseline (1×) |
| Intel Xeon (all generations) | 0.5 | 4 licences | $190,000 | 2× ARM |
| AMD EPYC (all generations) | 0.5 | 4 licences | $190,000 | 2× ARM |
| Oracle SPARC (M-series, T-series) | 0.5 | 4 licences | $190,000 | 2× ARM |
| IBM POWER (POWER8/9/10) | 1.0 | 8 licences | $380,000 | 4× ARM / 2× Intel |
| Unlisted/unknown processors | 1.0 (default) | 8 licences | $380,000 | Oracle assumes worst case for unlisted CPUs |
The core factor calculation is a four-step process that converts physical server hardware into Oracle processor licence requirements. For the complete processor licence calculation methodology, see Oracle Processor License Calculation.
| Step | Action | Example (2-Socket Intel Xeon, 16 cores/socket) | Key Rule |
|---|---|---|---|
| 1. Count physical cores | Identify the total number of physical CPU cores on the server that will run Oracle software | 2 sockets × 16 cores = 32 cores | Count cores, not threads — hyperthreading/SMT does not increase core count |
| 2. Look up core factor | Find the processor family in Oracle's published Core Factor Table | Intel Xeon = 0.5 | If processor is not listed, default is 1.0 — always verify |
| 3. Multiply cores × factor | Total cores × core factor = required processor licences | 32 × 0.5 = 16 licences | This applies to each Oracle product independently |
| 4. Round up to whole licences | If the result is not a whole number, round up | 16.0 — no rounding needed | Oracle does not sell fractional licences — always round up |
Critical Rule — Options and Packs:
Every Oracle database option or pack (Diagnostics Pack, Tuning Pack, Advanced Security, Partitioning, RAC, etc.) must be licensed on the same number of processors as the base database product. If you need 16 Database EE processor licences, and you use 3 options, you need 16 licences for each — 64 licences total (16 DB EE + 16 Diagnostics + 16 Tuning + 16 Partitioning). For minimum licence requirements that interact with core factor calculations, see Oracle License Minimums and Counting Rules.
Standard Edition Exception:
Oracle Database Standard Edition 2 (SE2) does not use the Core Factor Table. SE2 is licensed per socket (up to 2 sockets maximum), regardless of core count. This means a 2-socket server with 32 total cores requires only 2 SE2 licences, not 16. However, SE2 has significant feature and scalability limitations — if you need Enterprise Edition features, you must use core factor-based processor licensing.
Oracle publishes the Core Factor Table on its website and updates it as new processors enter the market. The following table covers the major processor families encountered in enterprise Oracle environments. For Oracle's pricing structure across all products, see Oracle Technology Price List: How to Calculate Pricing.
| Vendor | Processor Family | Core Factor | Common Use Case | Licence Impact vs Intel x86 |
|---|---|---|---|---|
| Intel | Xeon (all generations: Skylake, Cascade Lake, Ice Lake, Sapphire Rapids, Emerald Rapids, Granite Rapids) | 0.5 | Industry standard for enterprise Oracle Database and middleware | Baseline — most common deployment platform |
| AMD | EPYC (all generations: Rome, Milan, Genoa, Bergamo, Turin) | 0.5 | Increasing adoption for Oracle workloads; identical factor to Intel | Same as Intel — no licence cost difference |
| Oracle/Ampere | Ampere Altra (ARM-based) | 0.25 | OCI cloud instances; on-prem Ampere servers | 50% fewer licences than Intel/AMD for same core count |
| Oracle | SPARC M-series (M7, M8, M12) | 0.5 | Legacy Oracle-on-Oracle deployments; Solaris environments | Same as Intel |
| Oracle | SPARC T-series (T4, T5, T7, T8) | 0.5 | Legacy SPARC environments | Same as Intel |
| Fujitsu | SPARC64 (XII, X+) | 0.5 | Fujitsu SPARC servers running Oracle | Same as Intel |
| IBM | POWER8, POWER9, POWER10 | 1.0 | AIX environments; legacy IBM infrastructure | 2× more licences than Intel/AMD for same core count |
| Any | Unlisted or unidentified processor | 1.0 (default) | New processors not yet added to Oracle's table | Oracle assumes worst case until processor is officially listed |
Hardware Selection Implication: Choosing Intel or AMD over IBM POWER for an Oracle workload halves the processor licence requirement. For a 64-core server, that difference is 32 licences vs 64 — a $1.52M cost difference at Database EE list price. This makes hardware selection one of the most impactful Oracle cost optimisation decisions an enterprise can make.
The single most expensive Oracle licensing mistake related to core factors is virtualisation. Oracle's partitioning policy determines whether you licence only the cores assigned to an Oracle VM, or the entire physical host (or cluster). For the complete virtualisation licensing guide, see Oracle Licensing in Virtualized Environments.
| Virtualisation Type | Oracle's Position | Licence Calculation | Example (4 vCPU Oracle VM on 32-core host, Intel 0.5 factor) |
|---|---|---|---|
| VMware vSphere (soft partitioning) | Licence all cores on all hosts in the cluster where the Oracle VM could run | All cluster cores × core factor | 4-host cluster, 32 cores each = 128 cores × 0.5 = 64 licences ($3.04M) — expected: 2 licences ($95K) |
| Microsoft Hyper-V (soft partitioning) | Same as VMware — licence all cores on all hosts | All cluster cores × core factor | Same calculation as VMware — Oracle treats identically |
| Oracle VM (hard partitioning with pinned vCPUs) | Licence only the pinned/capped vCPUs | Pinned vCPUs × core factor | 4 pinned vCPUs × 0.5 = 2 licences ($95K) |
| Oracle Solaris Zones (hard partitioning with capped CPU) | Licence only the capped CPU resources | Capped cores × core factor | 4 capped cores × 0.5 = 2 licences ($95K) |
| IBM LPAR (hard partitioning with capped CPU) | Licence only the capped LPAR cores | Capped LPAR cores × core factor | 4 capped cores × 1.0 = 4 licences ($190K) |
| Physical server (dedicated — no virtualisation) | Licence all cores on the server | Server cores × core factor | 32 cores × 0.5 = 16 licences ($760K) — clear and predictable |
The VMware Cost Multiplier: The difference between expected and actual licence requirements under VMware soft partitioning is the largest source of Oracle audit findings globally. Organisations routinely face $1M–$10M+ compliance gaps because they assumed Oracle licensing applied only to their VM allocation, not the entire cluster. This is the single most important concept to understand when applying core factors in virtualised environments.
In cloud environments, Oracle replaces the traditional Core Factor Table with cloud-specific equivalence rules. The mapping depends on the cloud provider and the instance type.
| Cloud Provider | Licence Equivalence Rule | Effective Core Factor | Example |
|---|---|---|---|
| Oracle Cloud Infrastructure (OCI) | 1 OCPU = 1 Processor licence (OCPU = 1 physical core with hyperthreading) | Effectively 0.5 (since 1 OCPU = 2 vCPUs) | 4 OCPU instance = 4 Processor licences |
| AWS (Dedicated Host / metal instances) | 2 vCPUs = 1 Processor licence (on authorised instance types) | Effectively 0.5 | 8 vCPU instance = 4 Processor licences |
| Azure (Dedicated Host) | 2 vCPUs = 1 Processor licence (on authorised instance types) | Effectively 0.5 | 8 vCPU instance = 4 Processor licences |
| AWS/Azure (shared tenancy — non-dedicated) | Oracle may require licensing the entire physical host | Depends on host core count — can be extremely expensive | Small EC2 instance on a 128-core host → 64 licences under Oracle's interpretation |
| OCI Flexible Shapes | Customer selects exact OCPU count; 1 OCPU = 1 Processor licence | Best for right-sizing — choose exactly the OCPUs you can licence | Select 4 OCPUs = 4 licences (no over-provisioning) |
For ULA customers, core factor calculations become critical during certification when all Oracle deployments across on-prem and cloud must be counted. For ULA certification guidance, see Oracle ULA Certification: Oracle Will Try to Stop You.
When a ULA (Unlimited License Agreement) reaches its term end, the organisation must 'certify' — count all Oracle deployments and convert them to fixed perpetual licences. The core factor calculation determines the number of licences certified, which in turn determines the ongoing annual support cost. For the complete ULA framework, see our Oracle ULA guide. For ULA pricing and renewal strategies, see Decoding Oracle ULA Pricing and Oracle ULA Renewal Tactics.
| ULA Certification Scenario | Core Factor Impact | Post-ULA Support Cost | Optimisation Strategy |
|---|---|---|---|
| All Oracle on Intel x86 (factor 0.5) | 128 total cores × 0.5 = 64 certified licences | 64 × $10,450 support/year = $669K/year | Favourable — x86 halves the certified count |
| Mix of Intel x86 and IBM POWER | 64 Intel cores × 0.5 + 32 POWER cores × 1.0 = 64 certified licences | 64 × $10,450 = $669K/year (POWER doubles the count from those servers) | Migrate POWER workloads to x86 before certification to reduce certified count |
| Oracle on VMware cluster (soft partitioning) | 4-host cluster, 32 cores each = 128 × 0.5 = 64 licences per product | Entire cluster licensed — even if Oracle uses a fraction | Move Oracle to dedicated physical hosts or hard-partitioned VMs before certification |
| Oracle on OCI (BYOL during ULA) | 4 OCPU = 4 licences certified | Cloud deployments count toward certification total | Right-size OCI instances before certification to minimise certified count |
For ULA exit planning that incorporates core factor optimisation, see Oracle ULA Exit Strategy: When and How to Walk Away.
The following worked examples demonstrate how core factor calculations apply in typical enterprise scenarios, including the financial impact of different hardware and virtualisation choices.
| Scenario | Hardware | Cores | Core Factor | Licences Required | DB EE Cost at List | Key Insight |
|---|---|---|---|---|---|---|
| Small database server | 1-socket Intel Xeon, 8 cores | 8 | 0.5 | 4 | $190,000 | Straightforward calculation |
| Large database server | 2-socket Intel Xeon, 24 cores/socket | 48 | 0.5 | 24 | $1,140,000 | Socket count doesn't matter — only total cores × factor |
| IBM POWER equivalent | 2-socket IBM POWER10, 24 cores/socket | 48 | 1.0 | 48 | $2,280,000 | 2× the Intel cost for the same core count |
| With 3 database options | 2-socket Intel Xeon, 24 cores/socket | 48 | 0.5 | 24 × 4 products = 96 total | $4,560,000 | Each option requires the same 24 licences as the base DB |
| VMware cluster (soft partitioning) | 4 hosts, 2-socket Intel, 16 cores/socket each | 128 (all cluster cores) | 0.5 | 64 | $3,040,000 | Even if Oracle runs on 1 VM with 4 vCPUs |
| Dedicated physical server (same workload) | 1-socket Intel Xeon, 8 cores | 8 | 0.5 | 4 | $190,000 | $2.85M cheaper than VMware cluster for same workload |
| OCI cloud (flexible shape) | OCI VM.Flex, 4 OCPUs | 4 OCPU | 1 OCPU = 1 licence | 4 | $190,000 (licence value) | Right-sized to match available licences |
Oracle's audit team (LMS/GLAS) specifically targets core factor miscalculations because they are among the most financially significant findings. Each error below is a real-world pattern seen across Oracle audits. For comprehensive audit defence guidance, see our Oracle Audit Defense Service.
| Audit Finding | What Went Wrong | Oracle's Calculation | Typical Exposure | Prevention |
|---|---|---|---|---|
| VMware cluster fully licensed | Oracle VM ran on a VMware cluster; organisation licensed only the VM's vCPUs | All cluster cores × 0.5 — 10× to 30× the expected licence count | $1M–$10M+ | Dedicate physical servers or use hard partitioning for Oracle |
| Wrong core factor applied | Used 0.5 for IBM POWER servers (correct factor is 1.0) | All POWER cores × 1.0 — double the expected count | $500K–$5M+ | Always verify processor model against Oracle's published table |
| Unlisted processor defaulted to 1.0 | New processor not yet in Oracle's table; organisation assumed 0.5 | All cores × 1.0 (Oracle's default for unlisted CPUs) | $200K–$2M+ | Check Oracle's table before deploying on new hardware; request clarification from Oracle |
| Database options not counted | Organisation calculated base DB licences but not options (Diagnostics, Tuning, etc.) | Same processor count × each option = 2×–5× the expected licence count | $500K–$5M+ | Count every option separately at the same processor count as the base product |
| Hyperthreading counted as cores | Organisation counted logical threads instead of physical cores | Oracle uses physical cores only — thread count is irrelevant | $200K–$1M+ (double-counted) | Always count physical cores, not threads/logical processors |
| SE2 treated as processor-based | Organisation applied core factor to Standard Edition 2 (SE2 uses per-socket licensing) | SE2 = 1 licence per socket (max 2 sockets) regardless of cores | Over-licensing (paying for more than required) | Know which metric applies: SE2 = per socket; EE = per core with factor |
The core factor table creates opportunities for strategic hardware decisions that can reduce Oracle licensing costs by 50% or more. For comprehensive Oracle licence management and cost optimisation, see our Oracle License Management Services and Oracle Contract Negotiation Service.
| Optimisation Strategy | How It Works | Typical Savings | Consideration |
|---|---|---|---|
| Migrate POWER workloads to x86 | Moving Oracle from IBM POWER (factor 1.0) to Intel/AMD (factor 0.5) halves the licence requirement | 50% licence cost reduction per migrated server | Requires OS migration (AIX → Linux); performance validation needed |
| Isolate Oracle on dedicated physical servers | Move Oracle off VMware clusters onto dedicated physical hosts to avoid soft-partitioning cluster licensing | 70–95% reduction vs licensing the full VMware cluster | Requires infrastructure planning; may reduce virtualisation flexibility |
| Use Oracle VM with hard partitioning | Deploy Oracle VMs on Oracle VM Server with pinned/capped vCPUs to licence only the allocated cores | 60–90% reduction vs VMware soft partitioning | Requires Oracle VM infrastructure; operational overhead |
| Disable/cap unused cores | Deactivate cores in BIOS to reduce the physical core count that Oracle counts | 20–50% reduction (depends on cores disabled) | Reduces server capacity; must document for audit evidence |
| Right-size OCI instances | Use OCI flexible shapes to select exactly the OCPUs covered by available BYOL licences | Eliminates over-provisioning — 0% waste | Requires workload performance analysis to determine minimum viable OCPUs |
| Consolidate databases | Reduce total server count by consolidating multiple databases onto fewer, right-sized servers | 20–40% total licence reduction through efficient core utilisation | Increases dependency on fewer servers; DR planning required |
| # | Action | Owner | Frequency | Key Outcome |
|---|---|---|---|---|
| 1 | Inventory all servers running Oracle software: document CPU model, socket count, physical core count, and core factor for each | SAM / IT Operations | Annually + at every hardware change | Complete server-to-core-factor mapping for the entire Oracle estate |
| 2 | Verify core factors against Oracle's latest published table: do not rely on assumptions — confirm every processor model | SAM | At inventory; whenever Oracle updates the table | No incorrect core factor assumptions in licence calculations |
| 3 | Calculate processor licence requirements per server per product: cores × factor, rounded up, for each Oracle product and option | SAM | Annually; at every deployment change | Accurate licence requirement for the entire Oracle estate |
| 4 | Assess virtualisation impact: for every Oracle VM on VMware/Hyper-V, calculate the full cluster licence requirement under Oracle's soft partitioning policy | SAM / Infrastructure | Quarterly | No virtualisation surprise — the #1 source of audit findings |
| 5 | Compare licence requirements to entitlements: identify any gaps (under-licensed) or excess (over-licensed) | SAM / Procurement | Quarterly | Proactive compliance — gaps identified before Oracle audits |
| 6 | Evaluate hardware optimisation: model licence cost savings from migrating POWER → x86, VMware → dedicated hosts, or cluster → hard partitioning | Enterprise Architecture / SAM | At infrastructure refresh cycles | Data-driven hardware decisions that incorporate Oracle licence cost impact |
| 7 | Include Oracle licence cost in hardware procurement: before purchasing any server for Oracle workloads, run the core factor calculation to understand total cost of ownership | Procurement / SAM | Every hardware purchase | No hardware decisions that inadvertently double Oracle licence costs |
| 8 | Count database options separately: for every Oracle database, verify which options are enabled and calculate licence requirements for each option at the same processor count | DBA / SAM | Quarterly | No unlicensed options — the #2 most common audit finding |
| 9 | Prepare for ULA certification: if under a ULA, maintain current core-factor-based deployment counts that can be used for certification at any time | SAM | Semi-annually | Certification-ready data; optimised certified licence count |
| 10 | Conduct annual core factor compliance review: verify every calculation, check for new processors or virtualisation changes, and reconcile with licence entitlements | SAM / Advisory | Annually | Zero surprise audit findings; continuous processor licence compliance |
For expert assistance with Oracle processor licence calculations, virtualisation compliance, ULA certification counting, and audit defence, Redress Compliance provides independent advisory through our Oracle License Management Services, Oracle Audit Defense Service, and Oracle Contract Negotiation Service.
It is an official Oracle reference that assigns a multiplier (core factor) to each processor family, used to calculate the number of Oracle processor licences required for a given server. The factor ranges from 0.25 (Ampere ARM) to 1.0 (IBM POWER). Most enterprise x86 processors (Intel Xeon, AMD EPYC) have a factor of 0.5, meaning each physical core counts as half a processor licence.
Multiply the total number of physical cores on the server by the core factor for your processor family, then round up to a whole number. Formula: Physical Cores × Core Factor = Processor Licences Required. For example, a 32-core Intel server: 32 × 0.5 = 16 processor licences. This calculation must be repeated for each Oracle product and option deployed on that server.
No. Oracle Database Standard Edition 2 (SE2) is licensed per socket, not per core. SE2 is limited to a maximum of 2 sockets per server, and each socket requires one licence regardless of core count. The Core Factor Table applies only to processor-based licensing, which is used for Enterprise Edition, middleware, and other technology products.
Both Intel Xeon (all generations) and AMD EPYC (all generations) have a core factor of 0.5. This means each physical core requires half a processor licence. A 16-core Intel or AMD server would require 8 Oracle processor licences for any Enterprise Edition product.
IBM POWER processors (POWER8, POWER9, POWER10) have a core factor of 1.0 — each core requires a full processor licence. This is double the cost of Intel/AMD (factor 0.5) for the same core count. A 32-core POWER server needs 32 licences vs 16 for an identical Intel server, creating a $760,000 cost difference for Database Enterprise Edition alone.
Under Oracle's soft partitioning policy, VMware and Hyper-V do not limit the licence requirement to the VM's allocated cores. Oracle requires licensing all physical cores across all hosts in the cluster where the Oracle VM could run. This can multiply licence requirements by 10×–30×. Hard partitioning technologies (Oracle VM, Solaris Zones, IBM LPAR) allow licensing only the allocated cores.
Oracle defaults to a core factor of 1.0 for any processor not explicitly listed in the table. This is the least favourable factor, meaning each core requires a full processor licence. Before deploying Oracle on new hardware, verify the processor appears in Oracle's table or contact Oracle for clarification.
Yes. Every Oracle database option or pack (Diagnostics Pack, Tuning Pack, Advanced Security, Partitioning, RAC, etc.) must be licensed on the same number of processors as the base database product. If the server requires 16 Database EE processor licences, each enabled option also requires 16 licences — calculated using the same core factor.
In OCI, Oracle uses OCPU-based licensing: 1 OCPU = 1 Processor licence. Since 1 OCPU equals 1 physical core (2 vCPUs), the effective core factor is 0.5 (equivalent to Intel x86). OCI flexible shapes allow selecting exact OCPU counts to match available BYOL licences, preventing over-provisioning.
When certifying a ULA, all Oracle deployments must be counted using the core factor calculation. Every server, VM, and cloud instance running Oracle products is counted: physical cores × core factor = licences certified. The certified count determines ongoing support costs, so organisations should optimise their deployment (migrate POWER → x86, move off VMware clusters) before certification to minimise the certified licence base.
Yes. Some organisations deactivate cores in the server BIOS to reduce the physical core count that Oracle counts. This directly reduces the licence requirement. However, it also reduces server capacity, so performance testing is essential. All core disabling must be documented for Oracle audit evidence.
For a mid-size enterprise with 500 Oracle cores across Intel servers, the core factor (0.5) means 250 processor licences. At Database EE list ($47,500 each), that is $11.875M in licence value. If the same 500 cores were on IBM POWER (factor 1.0), the requirement would be 500 licences — $23.75M. Hardware selection alone can create an $11.875M cost difference.
Absolutely. The Oracle licence cost associated with a server can exceed the hardware cost many times over. Before purchasing any server for Oracle workloads, calculate the licence requirement using the core factor. A server that is $50,000 cheaper in hardware but requires $500,000 more in Oracle licences is not a good deal.
Oracle publishes the Processor Core Factor Table on its website (oracle.com). The table is updated periodically as new processors enter the market. Always use the latest version for licence calculations — do not rely on cached or historical copies, as new processor families may have been added with different factors.
This article is part of our Oracle ULA pillar. Explore related guides:
Redress Compliance has helped hundreds of Fortune 500 enterprises — typically saving 15–35% on Oracle renewals, ULA negotiations, and audit defense.
100% vendor-independent · No commercial relationships with any software vendor