The complete reference guide to Oracle Database licensing: all editions, Processor vs Named User Plus metrics, the Core Factor Table, Standard Edition 2 rules, options and packs, virtualisation pitfalls, cloud deployment models, and cost optimisation strategies.
Part of the Oracle Database pillar. See also: NUP vs Processor: Which to Choose | Standard Edition 2 Guide | Oracle Licensing Calculator.
| Edition | Price | Key Characteristics |
|---|---|---|
| Enterprise Edition | $47,500/Processor | Full-featured, no technical limits. Supports all extra-cost options (RAC, Partitioning, Advanced Security). Licensed per Processor or NUP. Most expensive and most common source of audit exposure |
| Standard Edition 2 | $17,500/Socket | Licensed per socket (not per core). Maximum 2 sockets per server, 16 CPU threads. No extra-cost options available. Significantly cheaper than EE. Upgrading to Enterprise is expensive with no credits |
| Express Edition (XE) | Free | No licence cost. Strict limits on CPU, memory, and storage. Suitable only for learning, prototyping, or ultra-small applications. No support available. Not viable for production |
Getting it wrong is expensive: upgrading from SE2 to Enterprise requires purchasing new licences at full EE pricing (Oracle does not offer upgrade credits). Running Enterprise Edition on workloads that would function identically on SE2 wastes 60-75% of your licence spend on unnecessary capability. Audit every deployment: does it genuinely require Enterprise Edition features?
| Factor | Processor Metric | Named User Plus (NUP) |
|---|---|---|
| What is counted | Physical cores x Core Factor | Each individual user or device with access |
| Unlimited users? | Yes: no user cap | No: every user must be named and counted |
| Hardware upgrades | More cores = more licences needed | More cores may raise NUP minimums per Processor |
| Minimums | None | 25 NUP/Processor (EE); 10 NUP/server (SE2) |
| List price (EE) | $47,500 per Processor | $950 per Named User Plus |
| Best for | High/unpredictable user counts, internet-facing apps | Small, known user groups (under 100 users per server) |
| Break-even point | Typically 100-200 users per server: above this Processor is cheaper | Below 100 users per server: NUP is cheaper |
Switching from NUP to Processor (or vice versa) requires purchasing new licences. Oracle does not offer free metric conversions. Choose once, choose correctly, and model your growth trajectory before committing.
| Processor Type | Physical Cores | Core Factor | Required Licences | List Cost (EE) |
|---|---|---|---|---|
| Intel Xeon (dual socket, 16 cores each) | 32 | 0.5 | 16 | $760,000 |
| AMD EPYC (dual socket, 32 cores each) | 64 | 0.5 | 32 | $1,520,000 |
| Oracle SPARC T-series | 32 | 0.25 | 8 | $380,000 |
| IBM POWER9 | 16 | 1.0 | 16 | $760,000 |
Formula: Required Licences = Physical Cores x Core Factor. The table is updated when new processor families are released. Always verify the current factor for your specific CPU model. Hardware procurement should consider Core Factor impact: choosing 0.5 instead of 1.0 halves your Oracle licence requirement for the same core count.
| SE2 Rule | Detail |
|---|---|
| Maximum 2 sockets per server | Cannot deploy on servers with more than 2 CPU sockets. Exceeding this limit requires Enterprise Edition |
| 16 CPU thread limit | Database utilises maximum 16 threads at any time, regardless of available hardware. Caps performance |
| No extra-cost options | Partitioning, Advanced Security, RAC (in recent versions), Diagnostics Pack, and all other EE options are unavailable |
| NUP minimum: 10 per server | If using NUP metric, at least 10 Named User Plus licences required per server |
| Socket-based pricing | $17,500 per socket. Significantly cheaper than EE's per-Processor model |
| Case Study: Healthcare Provider | Detail |
|---|---|
| Situation | US healthcare provider running Oracle Database EE across 12 servers for departmental applications (HR, scheduling, patient administration). None required Enterprise Edition features. Total EE licence cost: $2.28M plus $500K/yr support |
| Assessment | All 12 workloads operated within SE2's 2-socket, 16-thread limits. No Enterprise Edition features enabled or required |
| Result | Migrated all 12 databases to SE2. New licence cost: $420K (24 sockets x $17,500). Annual support dropped to $92K. Net savings: $1.4M in licences and $408K/yr in ongoing support with zero loss of functionality |
| Option / Pack | List Price (per Processor) | Annual Support (~22%) | Common Audit Trap |
|---|---|---|---|
| Partitioning | $11,500 | $2,530 | Enabled via CREATE TABLE PARTITION without licence |
| Advanced Security (TDE) | $15,000 | $3,300 | Transparent Data Encryption enabled by default in some configurations |
| Diagnostics Pack | $7,500 | $1,650 | AWR/ADDM accessed via Enterprise Manager without licence |
| Tuning Pack | $5,000 | $1,100 | Requires Diagnostics Pack: both must be licensed |
| Active Data Guard | $11,500 | $2,530 | Opening standby for read queries triggers full licence requirement |
| Real Application Clusters | $23,000 | $5,060 | RAC on every node in the cluster must be licensed |
A single server with Database EE plus Diagnostics Pack, Tuning Pack, and Partitioning costs $71,500 per Processor in licences alone, 50% more than the base database. Across a 20-Processor estate, that is $1.43M in licence costs and $314K/yr in support. Options are the most common source of Oracle audit findings because they are frequently enabled by default or activated inadvertently by DBAs.
| Virtualisation Type | Oracle's Position | Licensing Requirement |
|---|---|---|
| Soft Partitioning (VMware, Hyper-V, KVM, Nutanix AHV) | Oracle does not recognise software-based CPU limits. If Oracle runs on any VM in a VMware cluster with vMotion or DRS enabled, you must licence all physical cores across all hosts in the cluster | Full cluster licensing. A single Oracle VM on a 6-node cluster requires licensing all 6 hosts. Routinely generates $1-10M+ in audit findings |
| Hard Partitioning (Oracle VM, Solaris Zones, IBM LPAR) | Oracle-approved technologies that physically restrict software to designated cores. You licence only the allocated partition | Contained licensing. Reduces costs by 60-90% versus full-host licensing. Oracle VM with pinned CPUs is the most practical approved method for x86 |
| Case Study: Insurance Group VMware Audit | Detail |
|---|---|
| Situation | European insurance group deployed Oracle Database EE with Diagnostics Pack and Partitioning on 3 VMs within an 8-node VMware cluster with DRS enabled. Licensing team calculated 6 Processors needed (3 VMs x 4 vCPUs x 0.5) |
| Audit finding | Oracle required all 8 hosts: 192 physical cores x 0.5 = 96 Processors. Database EE ($47,500) + Diagnostics ($7,500) + Partitioning ($11,500) = $66,500 per Processor x 96 = $6.38M at list |
| Result | Migrated Oracle workloads to dedicated 2-node cluster, reducing footprint to 24 Processors. Settled for $1.6M: a $4.8M reduction. Annual support restructured saving $340K/yr |
| Takeaway | The multiplying effect of options in virtualised environments is the most expensive Oracle trap. Isolate Oracle workloads on dedicated hosts and disable unused options before any audit |
| Cloud Platform | Licence Conversion | BYOL Model | Cost Efficiency |
|---|---|---|---|
| Oracle Cloud (OCI) | 1 OCPU = 1 Processor licence | Most favourable: OCI designed for Oracle licensing efficiency | Best for Oracle workloads |
| AWS EC2 | 2 vCPUs = 1 Processor licence | BYOL supported; must follow Oracle's authorised cloud policy | Higher cost if not right-sized |
| Microsoft Azure | 2 vCPUs = 1 Processor licence | Similar to AWS BYOL approach | Comparable to AWS |
Active Oracle support is required for all BYOL deployments. During migration, ensure sufficient licences cover both on-premises and cloud simultaneously. Right-size cloud instances carefully: over-provisioning vCPUs increases licence requirement without corresponding performance benefit. OCI's advantage must be weighed against multi-cloud management burden if running everything else on AWS or Azure. Evaluate total cost of ownership across all dimensions, not just Oracle licence arithmetic.
| Pitfall | Detail |
|---|---|
| VMware full-cluster licensing | Single most expensive trap. Deploying Oracle on any VM in a shared VMware cluster with vMotion requires licensing every host. Organisations underestimate requirement by 4-10x calculating based on VM resources rather than physical host cores |
| Accidentally enabled options | Diagnostics Pack (AWR/ADDM), Tuning Pack, and Advanced Security (TDE) frequently enabled by default or activated during troubleshooting. Oracle audits check DBA_FEATURE_USAGE_STATISTICS for evidence. Even brief, unintentional access counts |
| Non-production environments assumed free | Development, QA, staging, and DR systems all require licensing unless contract explicitly provides exemption. Cloning production database to unlicensed test server creates immediate non-compliance |
| User count growth exceeding NUP licences | New employees, contractors, service accounts, API connections added without corresponding licence purchases. Each untracked user is a compliance gap |
| Forgotten database installations | Legacy databases on repurposed servers or Oracle bundled with third-party applications remain running without licence tracking. Audits discover these and calculate gaps at full list price |
| Restricted-use licence scope violations | Database licences bundled with Oracle applications (EBS, PeopleSoft, Siebel) restricted to that application only. Using the database for reporting, integration, or other purposes violates the restriction |
| Strategy | Detail | Savings Potential |
|---|---|---|
| Right-size editions | Audit every deployment: does it require Enterprise Edition, or would SE2 suffice? SE2 costs $17,500/socket vs $47,500+/Processor for EE | 50-75% per server for workloads not using EE features |
| Disable unused options and packs | Run DBA_FEATURE_USAGE_STATISTICS to identify installed but unused options. Disable Diagnostics Pack, Tuning Pack, Partitioning, and others not actively leveraged | $5,000-$23,000 per Processor per option plus 22% annually in support |
| Isolate Oracle on dedicated hosts | If using VMware, dedicate specific hosts to Oracle with live migration restricted to those hosts. Contains licensable footprint and prevents full-cluster licensing trap | 60-90% reduction versus full-cluster licensing |
| Leverage Core Factor in hardware procurement | Select processors with favourable Core Factors. Intel x86 at 0.5 halves core count. SPARC T-series at 0.25 quarters it. Hardware decision that reduces factor from 1.0 to 0.5 cuts requirement in half | 50% licence reduction per factor halving across entire estate |
| Optimise cloud instance sizing | On AWS/Azure, do not over-provision vCPUs. Each additional pair adds one Processor licence requirement. Right-size to actual workload demands | Performance tuning cheaper than licensing excess cloud capacity |
Choose Standard Edition 2 if your workload fits within its limits (2 sockets, 16 threads, no extra-cost options). Choose Enterprise Edition only when you genuinely need RAC, Partitioning, Advanced Security, or scaling beyond 2 sockets. SE2 costs roughly 60-75% less per server. Express Edition is free but too resource-constrained for production. The majority of audit findings stem from running Enterprise Edition on workloads that would function identically on SE2.
Use Processor when your user population is large (100+), unpredictable, or includes external/internet-facing users. Use Named User Plus when you have a small, defined group of internal users (typically under 100 per server). Break-even is usually 100-200 users per server. NUP requires careful tracking of every user and device, creating compliance risk in growing environments.
Core Factor is a multiplier Oracle assigns to each CPU type. Required licences = physical cores x Core Factor. Intel x86 uses 0.5 (halving core count), SPARC T-series uses 0.25, IBM POWER uses 1.0. Published by Oracle and updated for new processor families. Always verify the current factor for your specific hardware before calculating.
Oracle classifies VMware as "soft partitioning" and does not recognise it for licence limiting. You must licence all physical cores on the host server, or all cores in the VMware cluster if vMotion or DRS is enabled. A single Oracle VM on a large shared cluster requires licensing the entire cluster, multiplying costs 4-10x. Only ways to contain costs: isolate Oracle on dedicated hosts or use Oracle-approved hard partitioning.
Yes. Every extra-cost option (Partitioning, Advanced Security, Diagnostics Pack, Tuning Pack, RAC, Active Data Guard) requires a separate licence at additional cost. Each uses the same metric as your base database licence. Options are the most common audit finding because they are frequently enabled by default or activated accidentally by DBAs during routine troubleshooting.
On Oracle Cloud Infrastructure (OCI), 1 OCPU = 1 Processor licence under BYOL. On AWS and Azure, 2 vCPUs = 1 Processor licence. Both require active Oracle support for BYOL eligibility. OCI is generally more cost-efficient due to favourable conversion ratio and native optimisation. Evaluate against your broader cloud strategy before committing Oracle workloads to a single platform.
Redress Compliance provides independent advisory on Oracle Database licensing: edition right-sizing, options cleanup, virtualisation strategies, cloud migration planning, and audit defence. 100% vendor-independent. Fixed-fee engagement.
Oracle Licence ManagementIndependent Oracle advisory. Edition right-sizing. Options cleanup. Virtualisation strategy. Cloud migration. Audit defence. 100% vendor-independent, fixed-fee engagement.