Oracle Database licensing is one of the most complex and expensive areas of enterprise software. The interaction between editions, metrics, core factors, virtualisation policies, cloud rules, and separately licensed options creates a landscape where a single misconfiguration can trigger millions in unplanned spend. This guide covers every licensing model so you can licence correctly, avoid audit exposure, and optimise costs.
This is the master Oracle database licensing guide. See also: 6 Oracle Database Licensing Models & Costs | Licence Metrics & Definitions | SE2 Licensing Guide | Core Factor Calculator | NUP vs Processor Guide
Oracle offers several editions of its database, each with distinct licensing rules, technical limits, and cost profiles. Choosing the right edition is the foundational decision that shapes your entire licensing strategy and long-term costs.
| Edition | Licensing Model | Key Limits | List Price (per licence) | Typical Use Case |
|---|---|---|---|---|
| Enterprise Edition (EE) | Processor or NUP | No functional limits. Supports all options and packs. | $47,500 per processor | Large-scale, mission-critical workloads requiring maximum performance and features |
| Standard Edition 2 (SE2) | Socket-based (or NUP) | Max 2 sockets per server. 16 CPU thread cap. No extra-cost options. | $17,500 per socket | Small-to-medium systems where Enterprise features are not needed |
| Express Edition (XE) | Free (no licence cost) | Severely resource-restricted (limited CPU, memory, storage) | $0 | Learning, prototyping, or ultra-small non-production applications |
The edition determines which add-on features you can use. Enterprise Edition supports all options and management packs, each requiring a separate licence. Standard Edition 2 includes a more limited feature set with no additional options available. This means SE2 is inherently simpler to manage from a compliance perspective, but it comes with hard performance and scalability limits. For a complete SE2 deep-dive, see our SE2 Licensing Guide.
Enterprise Edition is the dominant edition in large enterprises because it removes technical ceilings and enables advanced capabilities like RAC, Partitioning, and Advanced Security. However, its significantly higher list price means every core added to your infrastructure carries substantial cost implications.
Oracle Database uses two primary licensing metrics: Processor and Named User Plus (NUP). This choice determines whether you pay based on hardware capacity or based on the number of people and devices accessing the database.
Processor licensing counts the computing power of the server: CPU cores multiplied by Oracle's core factor. This allows an unlimited number of users to access the database. Ideal for high, unpredictable, or external-facing user counts.
Named User Plus (NUP) licensing counts distinct users or devices accessing the database. Cheaper per unit but introduces compliance complexity: every user must be individually counted, and Oracle enforces minimum user counts per processor.
| Factor | Processor Metric | Named User Plus (NUP) |
|---|---|---|
| What is counted | CPU cores x core factor | Distinct users or devices with access |
| Unlimited users? | Yes | No. Each user/device must be licensed. |
| Hardware upgrades affect cost? | Yes. More cores = more licences. | Yes. More cores can raise NUP minimums. |
| EE minimum requirement | N/A | 25 NUP per processor |
| SE2 minimum requirement | N/A | 10 NUP per server |
| EE list price | $47,500 per processor | $950 per Named User Plus |
| Best suited for | High or unpredictable user counts. Web-facing applications. | Small, known user bases. Internal departmental systems. |
The NUP minimum is a common compliance trap. Even with only 5 actual users, Oracle requires at least 25 NUP per processor for Enterprise Edition. On a 4-processor server, that means a minimum of 100 NUP regardless of actual usage. For breakeven analysis, see our NUP vs Processor guide and NUP minimum requirements guide.
When you licence by Processor, Oracle does not count CPU cores at face value. It applies a weighting called the Core Factor, a multiplier that adjusts the licence count based on the processor type. The formula: Required licences = Physical cores x Core factor.
| Processor | Physical Cores | Core Factor | Required Licences |
|---|---|---|---|
| Intel Xeon (8 cores) | 8 | 0.5 | 4 processor licences |
| AMD EPYC (16 cores) | 16 | 0.5 | 8 processor licences |
| Oracle SPARC (32 cores) | 32 | 1.0 | 32 processor licences |
| IBM POWER8 (8 cores) | 8 | 1.0 | 8 processor licences |
The core factor table is published by Oracle but is not part of your licence contract. It is a policy document that Oracle can update unilaterally. Always check the latest version before making hardware procurement decisions. A seemingly minor change in core factor can significantly alter your licence requirements. The core factor does not apply in cloud environments. On AWS, Azure, and GCP, Oracle uses vCPU-based conversion rules. On OCI, the OCPU model applies. Use our Core Factor Table Calculator for quick estimates.
Oracle SE2 uses a simpler socket-based licensing model. Instead of counting individual cores, you count occupied CPU sockets on the server. Each occupied socket requires one SE2 licence regardless of core count. However, SE2 comes with strict hardware and feature limits.
| Restriction | SE2 Rule | Implication |
|---|---|---|
| Maximum server size | 2 sockets per server | Cannot deploy on 3+ socket servers. Requires EE. |
| CPU thread limit | 16 threads per database instance | Performance capped. Adding cores beyond ~8 provides no benefit. |
| RAC support | Removed in Oracle Database 19c+ | No clustering or scale-out. Single-server deployment only. |
| Options and packs | None available | Cannot purchase Partitioning, Advanced Security, Diagnostics Pack, etc. |
| NUP minimum | 10 NUP per server | Lower minimum than EE (25 NUP per processor). |
SE2 is the most cost-effective Oracle Database edition. At $17,500 per socket versus $47,500 per processor for EE, it can reduce database licensing costs by 60 to 96%. We routinely recommend SE2 migration as a primary cost-optimisation strategy for over-licensed EE deployments. For a comprehensive SE2 deep-dive, see our SE2 Licensing Guide.
Many of Oracle Database's most powerful features are not included in the base licence. They are sold as separately licensed options and management packs. Each add-on must be purchased independently and uses the same metric (Processor or NUP) as your base database licence. This means every option multiplies your total licensing cost.
| Option / Pack | List Price (Processor) | Key Risk |
|---|---|---|
| Partitioning | $11,500 | Often enabled by default in some Oracle tools |
| Diagnostics Pack | $7,500 | AWR/ASH reports trigger licensing. Accidental use is extremely common. |
| Tuning Pack | $5,000 | Requires Diagnostics Pack as prerequisite. Both must be licensed together. |
| Advanced Security | $15,000 | TDE encryption or data redaction triggers full licence requirement |
| Active Data Guard | $11,500 | Any read-only queries on standby require licensing beyond basic standby |
| Real Application Clusters (RAC) | $23,000 | EE only. Licensed per processor on every node in the cluster. |
| Multitenant | $17,500 | Required for BYOL to Oracle Autonomous Database |
| Data Masking & Subsetting | $11,500 | Source-only licensing rule. Only the server running masking operations requires it. |
| Partitioning (detail) | $11,500 | Every server with partitioned objects requires licensing |
Running an AWR report, viewing ASH data, or using Oracle Enterprise Manager's performance pages all trigger a Diagnostics Pack licence at $7,500 per processor. Many DBAs run these routinely without realising. Oracle's audit tools detect this usage automatically through DBA_FEATURE_USAGE_STATISTICS. On a 4-processor server, adding Diagnostics Pack ($30,000), Tuning Pack ($20,000), and Partitioning ($46,000) costs an additional $96,000 in licence fees plus $21,120/year in support, on top of the $190,000 base EE licence. Set control_management_pack_access = NONE to prevent accidental usage.
Virtualisation is where Oracle Database licensing becomes most dangerous and most expensive. Oracle's policies are highly restrictive for software-based virtualisation. Misunderstanding these rules is the single largest source of audit exposure in enterprise environments. The critical distinction is between hard partitioning and soft partitioning.
Hard partitioning (Oracle-approved). Uses Oracle-approved technologies to physically restrict the database to specific CPU cores. Only those cores require licensing. Approved technologies include Oracle VM (OVM) with CPU pinning, Oracle Linux KVM with CPU binding, IBM LPAR, and Solaris Zones.
Soft partitioning (not recognised by Oracle). Includes VMware vSphere, Microsoft Hyper-V, Nutanix AHV, KVM (without Oracle-approved pinning), and Docker/Kubernetes containers. Oracle requires licensing all physical cores on every host where the Oracle VM could potentially run.
| Environment | Oracle Licensing Requirement | Cost Risk |
|---|---|---|
| VMware vSphere cluster | All physical cores on every host in the cluster | Extreme. A single Oracle VM can force licensing hundreds of cores. |
| Microsoft Hyper-V | All physical cores on every host where Oracle could run | Very High. Same as VMware. |
| Oracle VM (hard partitioned) | Only the pinned CPU cores assigned to the Oracle VM | Low. Contained and predictable. |
| Bare metal (physical server) | All cores on the server x core factor | Predictable. Straightforward calculation. |
Oracle's Partitioning Policy is not a contractual document. It is a guideline Oracle publishes separately from your licence agreement. During audits, Oracle's LMS team will cite this policy as the definitive licensing rule, but legally it does not form part of your signed contract unless explicitly incorporated by reference. This distinction is critical for audit defence. See also our guides on licensing in virtualised environments, Oracle on Nutanix, and Oracle VM licensing.
Running Oracle Database in the cloud introduces different licensing rules depending on the platform. Oracle's own cloud (OCI) offers the most favourable terms, while third-party clouds (AWS, Azure, GCP) follow Oracle's Authorised Cloud Environment policy with less advantageous conversion rates.
| Factor | Oracle Cloud (OCI) | AWS / Azure / GCP |
|---|---|---|
| Licence conversion | 1 Processor licence = 2 OCPUs (4 vCPUs) | 1 Processor licence = 2 vCPUs |
| Core factor applied? | Favourable OCPU mapping (effectively 0.5) | No core factor. Every vCPU counted. |
| BYOL supported? | Yes. Lower subscription rate. | Yes. But EE on AWS RDS is BYOL only. |
| Licence Included available? | Yes (BYOL and LI options) | AWS RDS: SE2 only. EE requires BYOL. |
| Support Rewards | 25 to 33% of OCI spend offsets support bills | Not available |
| NUP minimum (EE) | As few as 2 NUP per OCPU in some services | Standard 25 NUP per processor applies |
A workload requiring 4 processor licences on OCI would need approximately 8 for the same vCPU capacity on AWS, effectively doubling the licence cost. For detailed cloud licensing guidance, see our guides on OCI vs AWS vs Azure vs GCP, Oracle on AWS, and Oracle BYOL.
When you combine add-on options with virtualisation, licensing costs escalate exponentially. Every option must be licensed on the same cores as the base database. In a soft-partitioned environment, that means licensing every option across every host in the cluster.
| Component | Licences Required | List Price per Licence | Total Cost |
|---|---|---|---|
| Database Enterprise Edition | 40 | $47,500 | $1,900,000 |
| Diagnostics Pack | 40 | $7,500 | $300,000 |
| Partitioning | 40 | $11,500 | $460,000 |
| Total Licence Cost | $2,660,000 | ||
| Annual Support (22%) | $585,200/year |
This scenario: Oracle Database EE with Diagnostics Pack and Partitioning on a VMware cluster with 5 hosts, each containing 16 cores (80 cores total, 40 processor licences after the 0.5 core factor). The organisation may have intended to licence a small VM, but Oracle's virtualisation policy multiplied the cost across the entire cluster. The options alone added $760,000. This is the "multiplying effect" that makes VMware + Oracle + options the most expensive licensing combination in enterprise IT.
| Pitfall | What Happens | Typical Cost Impact | Prevention |
|---|---|---|---|
| Misunderstanding virtualisation rules | Assuming VM vCPU allocation limits licensing. Oracle counts entire host or cluster. | $1M to $5M+ (cluster-wide licensing) | Isolate Oracle on dedicated hosts. Use hard partitioning. |
| Enabling options accidentally | Running AWR report, using TDE, or querying ASH without realising each triggers separate licence. | $100K to $500K+ per option per server | Set control_management_pack_access = NONE. Train DBAs. |
| Forgetting non-production environments | Cloning production to unlicensed dev/test server. Installing Oracle on developer workstations. | $100K to $500K+ per environment | Licence all installations. Use SE2 for dev/test. |
| Ignoring NUP minimums | Fewer actual users than Oracle's minimum (25 NUP per processor EE, 10 NUP per server SE2). | $50K to $200K+ per server | Verify minimums at deployment. Track NUP requirements. |
| User count growth | Starting with NUP for small team. Adding users over time without purchasing additional licences. | $50K to $300K+ cumulative | Annual user count audit. Switch to Processor when breakeven crossed. |
| Miscounting cores on new hardware | Upgrading from 8-core to 16-core processors. Doubling licence requirement without adjustment. | $190K to $380K+ per server | Pre-migration hardware audit. Budget licences before procurement. |
| Cloud vCPU miscounting | Assuming cloud vCPU ratios without verifying Oracle's specific rules per platform. | $100K to $500K+ per deployment | Verify OCI vs AWS vs Azure rules. See cloud comparison guide. |
For a comprehensive list, see our guide on top 25 Oracle Database non-compliance reasons. For audit preparedness, see our Oracle Audit Response Playbook.
1. Isolate Oracle workloads with hard partitioning. Constrain Oracle to dedicated hosts or use Oracle-approved hard partitioning to limit the number of cores requiring licensing. In VMware environments, create a dedicated Oracle cluster separate from the rest of your virtual infrastructure.
2. Migrate to Standard Edition 2 where possible. SE2 delivers the full Oracle Database engine at a fraction of the cost. For workloads within SE2's 2-socket/16-thread limits, the savings are transformative. Typically 30 to 50% of EE databases qualify for migration. See our SE2 Licensing Guide.
3. Eliminate unused options and packs. Audit your databases for enabled options you are not actively using. Disable Diagnostics Pack, Tuning Pack, and any other features not required. Set database parameters to prevent accidental usage.
4. Right-size cloud deployments. Do not over-allocate vCPUs on AWS, Azure, or OCI. Every additional vCPU pair increases your licence requirement. Use the smallest instance type meeting performance needs. Consider OCI where conversion rates are more favourable.
5. Leverage BYOL to Oracle Cloud. If you already own Oracle licences, bringing them to OCI via BYOL can reduce cloud subscription costs by 40 to 70%.
6. Conduct regular internal licence reviews. Perform quarterly reviews of Oracle deployments: installations, editions, enabled features, core counts, and user counts. Identify and remediate compliance gaps before Oracle does. For review guidance, see our Oracle Licence Management Services.
7. Negotiate strategically. Include all options in ULA/ELA negotiations where possible. Align renewal timing with Oracle's fiscal year-end (May 31). Present credible competitive alternatives. See our Oracle Contract Negotiation service and Cost Optimisation Playbook.
Processor licensing counts CPU cores (multiplied by Oracle's core factor) and allows unlimited users. Named User Plus (NUP) counts individual users or devices and is cheaper per unit but introduces compliance complexity. Oracle enforces minimum NUP counts: 25 per processor for Enterprise Edition, 10 per server for Standard Edition 2. The right choice depends on your user count and growth trajectory.
The core factor is a multiplier applied to physical CPU cores to determine Processor licences required. For Intel Xeon and AMD EPYC, the factor is 0.5 (2 cores = 1 licence). For Oracle SPARC and IBM POWER, the factor is typically 1.0 (each core = 1 licence). The core factor applies only to on-premises deployments. Cloud environments use vCPU or OCPU conversion rules instead.
Standard Edition 2 is limited to servers with 2 CPU sockets maximum, a cap of 16 CPU threads per database instance, and no support for Enterprise Edition options or packs. RAC support was removed in Oracle Database 19c. SE2 uses socket-based licensing at $17,500 per socket, making it 63% cheaper per unit than Enterprise Edition.
Under Oracle's Partitioning Policy, yes. Oracle classifies VMware as soft partitioning and requires licensing all physical cores on every host in the cluster where the Oracle VM could potentially run (via vMotion or DRS). The safest mitigation is isolating Oracle workloads on a dedicated VMware cluster with minimum hosts.
On AWS, Oracle counts every 2 vCPUs as 1 Processor licence (with hyperthreading enabled). Enterprise Edition on AWS RDS is BYOL only. AWS RDS offers Licence Included pricing only for Standard Edition 2, limited to 8 vCPUs per instance. For the same vCPU capacity, AWS requires approximately twice as many licences as OCI.
Running an AWR (Automatic Workload Repository) report, viewing ASH (Active Session History) data, or using Oracle Enterprise Manager's performance diagnostics pages all trigger a Diagnostics Pack licence at $7,500 per processor. This is the most common accidental compliance violation. Set the control_management_pack_access parameter to NONE to prevent accidental usage.
Enterprise Edition lists at $47,500 per Processor licence or $950 per Named User Plus. Standard Edition 2 lists at $17,500 per socket or $350 per NUP. Annual support is 22% of the licence price. Enterprise discounts of 40 to 70% off list are common for large deals. Each add-on option carries its own per-processor cost on top of the base licence.
On OCI, 1 Processor licence covers 2 OCPUs (4 vCPUs). On AWS, the same licence covers only 2 vCPUs. You need approximately twice as many licences for the same workload on AWS compared to OCI. Additionally, OCI offers Support Rewards (25 to 33% of spend as credits against support bills), lower NUP minimums, and Licence Included options for Enterprise Edition.
Yes. SE2 can be deployed on OCI, AWS, Azure, and GCP. On AWS, SE2 is limited to instances with 8 or fewer vCPUs. On OCI, SE2 is limited to 8 OCPUs (16 vCPUs). SE2's socket-based pricing typically translates to more favourable cloud economics for smaller workloads.
For organisations with significant Oracle Database estates, independent advisory is strongly recommended. The interaction between editions, metrics, virtualisation policies, cloud rules, and options creates substantial complexity. An independent adviser can identify savings opportunities, prevent compliance gaps, and provide audit defence with no ties to Oracle or any cloud vendor.
Our Oracle advisory team has managed 200+ licensing engagements for Fortune 500 companies. Vendor-independent. Fixed-fee engagements. No ties to Oracle.
Oracle Advisory ServicesIndependent Oracle licensing advisory. Edition selection, virtualisation architecture, options audit, cloud migration strategy, audit defence. Fixed-fee. Vendor-independent.