Oracle Database Licensing Guide: Editions, Metrics, Options and Compliance

Why Oracle Database Licensing Demands Expert Attention

Oracle Database powers mission-critical workloads at thousands of organisations worldwide, but its licensing model is deliberately complex. Oracle has a commercial incentive to see customers unknowingly use features that require separate licences — and it employs a dedicated License Management Services (LMS) team to audit precisely that. A single unintentional usage of the Diagnostic Pack, RAC on a non-licensed node, or a forgotten In-Memory option can generate claims worth millions.

This guide is written from the perspective of ex-Oracle LMS auditors who have spent more than 20 years on both sides of Oracle licensing negotiations. The goal is to give procurement leaders, CIOs, and SAM managers a full picture of how Oracle Database licensing actually works — so you can negotiate from strength and stay audit-ready.

Oracle Database Editions: SE2 vs Enterprise Edition

Oracle offers two primary database editions for general enterprise use: Standard Edition 2 (SE2) and Enterprise Edition (EE). The choice between them shapes everything — your licensing metric, the features you can legally use, and your long-term cost trajectory.

Standard Edition 2 (SE2)

SE2 is Oracle's entry-level relational database edition, designed for workloads that do not require the advanced scalability and features of Enterprise Edition. Its key characteristics include socket-based licensing — you pay per occupied processor socket regardless of how many cores are on the chip — and a hard ceiling of two populated sockets per server. SE2 does not support Real Application Clusters (RAC), Oracle Partitioning, In-Memory, Advanced Security, or any of the paid Enterprise Edition options.

SE2 list price is approximately $17,500 per socket (2026 list). With the two-socket limit, a single SE2 server costs $35,000 to licence. Annual support is typically 22% of the licence fee — and that support fee increases by 8% per year, compounding the cost significantly over a typical five-to-seven year lifecycle.

A critical trap with SE2 is the presence of Enterprise Edition feature code in the binaries. Even on SE2, the database tracks feature usage in DBA_FEATURE_USAGE_STATISTICS. If developers or DBAs accidentally invoke EE-only features — often through Oracle Enterprise Manager or third-party tooling — Oracle will find that usage in an audit and claim SE2 should have been EE all along, with full retroactive true-up costs.

Enterprise Edition (EE)

Enterprise Edition is Oracle's full-featured database product, with no socket ceiling and the ability to purchase additional options and management packs. EE uses the processor licensing metric combined with the Core Factor Table, or optionally Named User Plus (NUP) where user counts are low enough to make that metric cost-effective.

EE list price is $47,500 per processor licence (2026 list). On a modern server with 32 cores at a 0.5 Intel core factor, that equates to 16 processor licences — a base cost of $760,000 before any options, support, or discounts. Annual support at 22% adds $167,200 in year one, rising by 8% per year thereafter.

Enterprise Edition unlocks access to Oracle's extensive options ecosystem — Real Application Clusters, Partitioning, In-Memory, Advanced Security, Label Security, Active Data Guard, and more — but each option must be licensed separately and carries its own per-processor list price.

Licensing Metrics: Processor vs Named User Plus

Oracle Database Enterprise Edition can be licensed under two primary metrics. Choosing the right metric — and ensuring you apply it correctly — is one of the highest-value decisions in Oracle licensing.

Processor Licensing

The processor metric licenses every physical core on every server where Oracle is installed (or, in virtualised environments, every core on the physical host unless approved hard partitioning is in place). The number of licences required per core is determined by the Oracle Core Factor Table.

The Core Factor Table assigns a multiplier to each processor type. Intel Xeon processors generally carry a 0.5 factor, meaning you require 0.5 licences per physical core. AMD EPYC processors (3rd and 4th generation) also carry a 0.5 factor. SPARC-based processors may carry different factors. On 1 April 2025, Oracle updated the Core Factor Table to include Intel Xeon 69xxP, 67xxE, 67xxP, 65xxP and E-24xx series at 0.5, and in May 2025 added AMD EPYC 9xx5 and related 5th-generation AMD series at 0.5.

For a 64-core Intel Xeon server: 64 cores × 0.5 factor = 32 processor licences required. At $47,500 per licence, that is $1,520,000 for Oracle Database EE alone, before options. This is why processor licensing on large bare-metal or poorly partitioned servers is so commercially dangerous.

Named User Plus (NUP)

Named User Plus licenses a defined set of named individuals or devices authorised to access the database, regardless of how many processor cores run beneath it. Oracle requires a minimum of 25 NUP licences per processor on Enterprise Edition. At approximately $950 per NUP licence (list), 25 NUP licences cost $23,750 — comparable to half a processor licence in purchasing power.

NUP licensing is commercially attractive when user counts are low relative to server size. A 32-core server with only 40 named users, for example, would require a minimum of 32 × 25 = 800 NUP licences at processor minimum rules — not 40. Always apply the processor-based minimum floor before assuming NUP saves money.

NUP becomes truly cost-effective only when the actual user count is below the processor minimum floor AND users can be clearly enumerated and controlled. Batch processes, middleware connectors, and application servers that access the database must also be counted as named users if they are not covered by a separate application-specific agreement.

Oracle Database Options: The Hidden Cost Layer

Enterprise Edition is the foundation, but Oracle's options ecosystem is where the real cost complexity lies. Options are separately priced add-ons that extend EE functionality. You must licence every option on every processor where that feature is installed, active, or accessible — not just where it is actively used. If the feature is enabled in the database and a user could theoretically invoke it, Oracle considers it in scope for licensing.

Real Application Clusters (RAC)

Oracle RAC allows multiple database instances to share a single database on a clustered set of servers, providing high availability and horizontal scalability. RAC list price is $23,000 per processor. On the same 32-processor-licence server from our earlier example, adding RAC costs an additional $736,000 — nearly as much as the base EE licences themselves. In a clustered HA environment with two or more nodes, RAC must be licensed on all nodes in the cluster.

Oracle Partitioning

Partitioning is among Oracle's most commonly used — and most commonly unlicensed — options. It allows large tables and indexes to be divided into smaller, manageable pieces for performance and storage management. List price is $11,500 per processor. Partitioning shows up in DBA_FEATURE_USAGE_STATISTICS whenever a partitioned table is queried, which makes it a frequent and straightforward audit finding. Many organisations have inherited partitioned schemas from vendors or previous DBAs without realising this triggers a licensing requirement.

Oracle In-Memory

In-Memory allows data to be stored in a columnar in-memory format for analytics acceleration. It is enabled by a non-zero value for the INMEMORY_SIZE initialisation parameter. List price is $23,000 per processor. If Oracle Enterprise Manager sets this parameter automatically during tuning recommendations, a licensing obligation may be created without any deliberate action by the DBA.

Advanced Security (TDE and Network Encryption)

Oracle Advanced Security provides Transparent Data Encryption (TDE) and network encryption capabilities. List price is $15,000 per processor. TDE is increasingly required for regulatory compliance (PCI DSS, HIPAA, GDPR), yet many organisations implement it without realising it requires a separately purchased option licence. In Oracle Database 12.2 and later, TDE is technically available without Advanced Security for tablespace encryption, but column-level and full-disk TDE still require the option.

Active Data Guard

Data Guard itself is included with Enterprise Edition and provides physical standby databases for disaster recovery at no additional cost. However, Active Data Guard — which allows the standby database to be opened read-only for reporting, offloading backups, and other active operations — requires a separate licence at $11,500 per processor on the primary database server (you licence the primary, not the standby). Many organisations accidentally activate Active Data Guard by querying the standby or opening it read-only without purchasing the option.

Oracle Management Packs: Diagnostic and Tuning

Beyond options, Oracle offers management packs that provide monitoring, diagnostic, and optimisation capabilities through Oracle Enterprise Manager. The two most commercially significant are the Diagnostic Pack and the Tuning Pack.

Diagnostic Pack

The Diagnostic Pack provides the Automatic Workload Repository (AWR), Active Session History (ASH), and Automatic Database Diagnostic Monitor (ADDM). These tools are among the most widely used in Oracle DBA toolkits for performance troubleshooting. However, accessing AWR reports, ASH views, or ADDM recommendations requires a Diagnostic Pack licence at $7,500 per processor per year (or $150,000 perpetual per processor).

Critically, on Oracle Database Enterprise Edition, the CONTROL_MANAGEMENT_PACK_ACCESS parameter defaults to DIAGNOSTIC+TUNING — meaning both packs are enabled from the moment the database is installed. AWR snapshots are automatically collected every 60 minutes. Every snapshot, every ASH sample, every ADDM report is logged in DBA_FEATURE_USAGE_STATISTICS and will be cited in any Oracle audit. Setting CONTROL_MANAGEMENT_PACK_ACCESS = NONE immediately if you have not licensed these packs stops future accumulation but does not erase historical evidence.

Tuning Pack

The Tuning Pack provides the SQL Tuning Advisor, SQL Access Advisor, and automatic SQL tuning. It requires the Diagnostic Pack as a prerequisite — you cannot licence the Tuning Pack without also licensing the Diagnostic Pack. List price is $5,000 per processor per year (or $100,000 perpetual per processor). The Tuning Pack is frequently triggered inadvertently through Oracle Enterprise Manager's automatic tuning jobs, which run on a default schedule and invoke SQL Tuning Advisor without any DBA intervention.

Virtualization and Cloud: The Licence Multiplication Problem

Virtualisation is the most commercially dangerous area of Oracle Database licensing for most enterprise customers. Oracle's policy does not recognise VMware, Microsoft Hyper-V, Nutanix AHV, or most third-party hypervisors as "approved hard partitioning" technologies — meaning Oracle requires you to licence all physical cores on the entire VMware cluster, not just the cores allocated to the virtual machine running Oracle.

VMware and Soft Partitioning

If Oracle Database is deployed on a VMware vSphere cluster with 10 hosts, each with 64 Intel Xeon cores (0.5 factor = 32 processor licences per host), Oracle requires 320 processor licences regardless of how many vCPUs are allocated to the Oracle VM. At $47,500 per processor licence, that is $15.2 million in base EE licences for a cluster that may have originally been estimated at 4–8 processor licences based on vCPU allocation alone.

This is the central commercial risk of running Oracle Database in VMware environments. Oracle has consistently enforced this position in audits, and its documentation explicitly excludes VMware from the approved hard partitioning list. The only recognised hard partitioning technologies are Oracle VM, Oracle Solaris Zones (when correctly configured), IBM LPAR with static processor assignment, and a small set of others.

Approved Hard Partitioning

To reduce licence scope in virtualised environments, customers must deploy Oracle on an approved hard partitioning technology and correctly configure it so that Oracle cannot move between processors or nodes without administrative intervention. Oracle VM Server for x86 and SPARC, Solaris Containers/Zones with physical binding, and dedicated Exadata infrastructure are among the approaches that qualify. If hard partitioning is implemented correctly and documented, you licence only the physical cores assigned to the partition — not the entire host.

Oracle Cloud Infrastructure (OCI)

OCI is Oracle's preferred cloud platform and offers the most commercially favourable licensing rules for Oracle Database. On OCI, Oracle uses a simplified vCPU-to-processor-licence ratio: 2 vCPUs equal 1 processor licence (with hyper-threading enabled). The Core Factor Table does not apply. This means that on OCI, licensing costs are predictable and proportional to allocated compute, unlike on-premises VMware environments.

BYOL on OCI allows customers to apply existing on-premises licence entitlements to cloud deployments. An OCI BYOL instance can be stopped without continuing to consume licence credits — you only use licences when the instance is running. This makes OCI a compelling platform for variable or burst workloads.

AWS, Azure, and Google Cloud

On Authorised Cloud Environments (ACE) — which include AWS, Azure, and Google Cloud — Oracle also uses the 2 vCPUs = 1 processor licence rule, and the Core Factor Table does not apply. However, licence obligations on these platforms may begin as soon as Oracle binaries are present and the instance is powered on, even if it is idle. Customers should never assume that a stopped or idle cloud instance has no licensing obligation without consulting Oracle's Authorised Cloud Environment policy in detail.

Oracle ULA and PULA for Database Deployments

For organisations with large, growing, or uncertain Oracle Database footprints, a Unlimited Licence Agreement (ULA) or Perpetual ULA (PULA) may offer a more predictable commercial framework. Under a ULA, Oracle grants unlimited deployment rights for a defined set of products for a fixed period — typically three years — in exchange for a flat annual fee.

At the end of a ULA term, the customer certifies their deployment count to Oracle and retains perpetual licences for the quantity deployed. This certification process is commercially critical: every additional deployment before certification is effectively free, because you already have unlimited rights. Customers must maximise their Oracle Database footprint — and the footprint of all covered options and packs — before the ULA certification date to extract full value from the agreement.

Support fees under a ULA are typically fixed for the duration of the term, regardless of how much you deploy. This is a significant advantage over individual licence transactions, where support fees increase by 8% per year on the perpetual licence base price. If you plan to expand your Oracle Database estate, executing a ULA before that growth occurs is almost always commercially superior to licensing incrementally.

A PULA provides the same unlimited deployment rights but converts to a perpetual agreement at the outset rather than after a defined term. PULAs are less common and typically reserved for customers with very large, stable, long-term Oracle commitments. Oracle also uses its Cloud Service Initiative (OCS) for customers moving workloads to OCI, and the Cloud Support Identifier (CSI) model for organisations managing support across complex multi-entity structures.

Oracle Database Support: The 8% Annual Escalator

Oracle's standard support model — Oracle Software Update Licence and Support (SULS) — is priced at approximately 22% of the perpetual licence fee annually. More importantly for long-term cost planning, Oracle contractually increases support fees by 8% per year. This is not a rumour or an estimate — it is a contractual term that Oracle enforces consistently.

On a $1 million perpetual EE licence purchase, Year 1 support is $220,000. In Year 5, that figure has grown to approximately $299,000 per year. Over 10 years, the cumulative support cost on a static $1 million licence base exceeds $3.17 million — more than three times the original software purchase. Many organisations discover this escalator only when they receive their annual renewal invoice and find a sharp increase they had not budgeted for.

Strategies for managing Oracle support costs include negotiating support caps at deal-signing, exploring third-party support alternatives (which provide risk-adjusted savings of 50–60% against Oracle's fees but with limitations on cloud and newer feature access), and using ULA terms to lock support fees during periods of growth.

Audit Risk: DBA_FEATURE_USAGE_STATISTICS and LMS Scripts

Oracle audits are initiated by Oracle's License Management Services team and typically begin with a request to run Oracle's Collection Scripts against your database estate. These scripts query DBA_FEATURE_USAGE_STATISTICS, a view that records every feature, option, and pack that has ever been used on a given database instance. Usage is timestamped and cannot be deleted — historical usage persists indefinitely.

The view captures data on more than 200 individual features. Oracle LMS cross-references this data against your Order Management System (OMS) entitlements to identify gaps. Common findings include Diagnostic and Tuning Pack usage on databases where only EE was licensed, Partitioning on databases with non-partitioned licence agreements, RAC node usage outside the licensed cluster scope, and In-Memory usage on databases where only standard EE was purchased.

Pre-Audit Remediation

The most effective defence against Oracle audit findings is proactive remediation. Before an audit begins, organisations should conduct an internal DBA_FEATURE_USAGE_STATISTICS review, set CONTROL_MANAGEMENT_PACK_ACCESS = NONE on any unlicensed databases, remove partitioned schemas that are not required, disable unused options through proper parameter management, and document all licence entitlements against each database instance. If historical usage has already accumulated, legal counsel and experienced Oracle licensing advisors should be engaged before any Oracle audit process begins, as how you respond to initial requests can significantly affect the final outcome.

Cost Reduction Strategies for Oracle Database Licensing

Reducing Oracle Database licensing costs requires a systematic approach across three dimensions: right-sizing your current footprint, controlling future growth, and negotiating commercially effective agreements.

Right-Sizing Your Current Footprint

Start with an accurate inventory of every Oracle Database instance in your environment — on-premises, cloud, and in development and test environments. Many organisations are paying support on licences that cover databases that have been decommissioned, migrated, or consolidated. Run DBA_FEATURE_USAGE_STATISTICS across all instances to identify which options and packs are actually in use versus merely enabled. Disable unused features, set CONTROL_MANAGEMENT_PACK_ACCESS appropriately, and explore whether EE-only workloads could be migrated to SE2 if they remain within SE2's two-socket ceiling and functional constraints.

Leveraging Approved Hard Partitioning

If you are running Oracle in a large VMware or Hyper-V environment and using only a fraction of the cluster capacity for Oracle workloads, migrating those workloads to Oracle VM or an approved hard-partitioned environment can dramatically reduce your processor licence count. The implementation cost of migration is almost always less than the perpetual licence exposure you are carrying by remaining on soft-partitioned infrastructure.

Negotiating Discounts and Agreement Structures

Oracle routinely discounts EE licences by 40–60% from list price in competitive, well-prepared negotiations. The key levers are credible competitive alternatives (PostgreSQL, SQL Server, or cloud-native database services), fiscal year-end timing (Oracle's fiscal year ends 31 May, with Q4 running March to May delivering the deepest discounts), volume commitments, and multi-year agreement structures. Never purchase Oracle Database licences at list price — a significant discount is always available for prepared buyers.

For growing organisations, a well-structured ULA negotiated at the right price point will almost always be cheaper than incremental processor licensing. Even if you are uncertain about deployment volume, the certainty of a fixed support fee during the ULA term is itself commercially valuable given Oracle's 8% annual support escalator.

Third-Party Support

Third-party support providers such as Rimini Street and Spinnaker Support offer Oracle Database support at 50–60% below Oracle's annual fees, without the 8% annual escalator. Third-party support is commercially attractive for stable, on-premises Oracle environments where access to the latest patches, cloud integration features, and Oracle's new database versions is not a priority. However, third-party support creates risks if Oracle pursues an audit, as it can be perceived as a signal that an organisation is reducing its Oracle spend and may trigger closer commercial attention.

Oracle Database FAQ

Does SE2 require a Core Factor Table calculation?

No. SE2 uses socket-based licensing — you count the number of populated processor sockets, not the number of cores. Each occupied socket requires one SE2 licence, regardless of core count. The Core Factor Table only applies to Enterprise Edition processor licensing.

Can I run Oracle Database on AWS without any Oracle licences?

Yes, if you use Oracle Database licence-included cloud services such as Amazon RDS for Oracle. In this model, AWS bundles the Oracle licence into the hourly service cost and manages the Oracle relationship on your behalf. If you run Oracle on an EC2 instance using BYOL, you must apply your own Oracle licences and comply with Oracle's Authorised Cloud Environment policy — including the 2 vCPU = 1 processor licence rule.

What is the safest way to use Enterprise Manager without triggering a Diagnostic Pack obligation?

Set CONTROL_MANAGEMENT_PACK_ACCESS = DIAGNOSTIC (if you have the Diagnostic Pack but not the Tuning Pack) or NONE (if you have neither). Disable automatic AWR collection if unlicensed. Avoid using the Performance Hub, ADDM, and SQL Tuning Advisor features in EM unless those packs are licensed. Note that simply accessing EM's database home page does not trigger a pack obligation — it is the specific feature invocations that create usage evidence.

Working with Redress Compliance on Oracle Database Licensing

Redress Compliance is an independent Oracle licensing advisory firm founded by ex-Oracle LMS auditors with more than 20 years of enterprise software licensing experience. We help organisations quantify their Oracle Database licence exposure, prepare for and respond to Oracle audits, negotiate ULA and PULA structures, and design compliant deployment architectures that minimise ongoing licence obligations. Our advisory is independent of Oracle — we work exclusively for customers. To discuss your Oracle Database licensing position, visit our Oracle services page or explore the Oracle Knowledge Hub.