The Two Fundamental Metrics
Oracle Database licensing is built around two primary metrics: Processor and Named User Plus (NUP). Every Oracle Database licence — whether for Standard Edition 2, Enterprise Edition, or any of the enterprise options — is sold under one of these two metrics. Understanding the difference is not optional for anyone responsible for Oracle cost management; it is foundational to every Oracle negotiation.
The metric you choose — or the metric Oracle's sales team steers you towards — can produce dramatically different cost outcomes for the same database deployment. We have seen enterprises paying three times more than necessary because their initial deployment choice was made without proper licensing analysis. We have also seen enterprises overcounting their NUP obligations and overpaying for years without realising the error.
The difference between Processor and NUP licensing for a 200-person internal application can be $180,000 per year versus $45,000 — for exactly the same Oracle Database deployment. The metric selection matters enormously.
Processor Licensing: How It Works
The Processor metric licences Oracle Database based on the number of processor cores running the software, multiplied by a core factor that depends on the processor architecture. Oracle's logic is that each processor (core) represents a unit of computing capacity making the software available to users or systems — regardless of how many people actually access the database.
Core Factor Calculation
Oracle publishes a Core Factor Table that assigns a multiplier to each processor type. The most common factors in enterprise environments are:
Oracle Database Enterprise Edition list price in 2026 is $47,500 per processor licence (perpetual), with an annual support fee of 22% of the licence cost ($10,450 per processor per year). On a standard 2-socket server with Intel Xeon processors and 32 cores per socket, a full-server deployment requires: 64 cores × 0.5 core factor = 32 processor licences. At list price, that is $1,520,000 in perpetual licences plus $334,400 per year in support. Negotiated pricing typically brings this down by 50–65% for enterprise buyers.
When Processor Licensing Makes Sense
Processor licensing is the right metric when: the database has many users or an unknown, variable user population; users include external customers, partners, or automated systems; or the user count multiplied by NUP pricing would exceed the Processor cost threshold. For databases serving internet applications, B2C platforms, or internal applications used across the entire workforce, Processor licensing is almost always more cost-effective than NUP.
Named User Plus: How It Works
Named User Plus licensing charges per authorised user — defined as any individual authorised to access the Oracle software, regardless of whether they actually connect on a given day. The "Plus" in the name distinguishes it from Oracle's older "Named User" metric and is relevant primarily for licensing Oracle tools; for most Database licensing discussions, NUP is the term used interchangeably.
The NUP Minimum Rule
Oracle imposes a critical minimum on NUP licensing: you must licence a minimum of 25 Named User Plus licences per Processor licence's worth of hardware. This means that if your server qualifies for 4 Processor licences under the Core Factor calculation, you must purchase at least 100 NUP licences — regardless of how few people actually use the database.
Oracle Database Enterprise Edition NUP list price: $950 per user per year (perpetual licence equivalent with support). For 100 users at list price, that is $95,000 per year in support costs. Compare this to 4 Processor licences at $10,450 support each = $41,800 per year. In this scenario, Processor licensing is actually cheaper than NUP even with only 4 users — because the NUP minimum forces a 100-user count.
Where NUP Delivers Value
NUP licensing genuinely saves money in specific circumstances: small internal databases with well-defined, limited user populations (typically fewer than 10–15 users per processor licence worth of hardware); development and test environments with tightly controlled access; or dedicated departmental applications where the authorised user count can be kept definitively below the Processor break-even threshold.
Which Metric Is Right for You?
The decision between Processor and NUP is straightforward once you have two inputs: the number of Processor licences required for your hardware (cores × core factor), and the number of authorised users. Apply the NUP minimum (25 users per Processor licence) and compare costs.
Virtualisation: The Licensing Minefield
Oracle's virtualisation licensing policy is the most contentious aspect of Oracle Database licensing and the primary source of audit findings for enterprises running Oracle on VMware, Hyper-V, or other non-Oracle hypervisors.
Oracle's Hard vs. Soft Partitioning Policy
Oracle distinguishes between hard partitioning (which limits Oracle's licensing scope to assigned partitions) and soft partitioning (which does not). Only hard partitioning technologies — specifically Oracle VM Server for x86, Oracle VM Server for SPARC (formerly Logical Domains), Solaris Zones under specific configurations, and IBM LPAR — are accepted by Oracle as limiting the licensing requirement to the assigned cores or partitions.
VMware ESXi, Microsoft Hyper-V, KVM, and all other common hypervisors are classified as soft partitioning. Oracle's policy states that when Oracle software is deployed on soft partitioning technology, all physical processor cores in the host server must be licensed. This means that a single Oracle Database instance running in a 4-vCPU VM on a 64-core VMware host requires licensing all 64 cores (× core factor) — not just the 4 vCPUs assigned to the VM.
A Fortune 500 manufacturing company came to us having run Oracle Database on VMware for six years. Their self-reported licence position covered 12 processor licences. Oracle's audit team calculated 340 processor licences based on the physical host infrastructure. The gap: $15.6 million in unlicensed software at list price.
Cloud Deployments: IaaS and SaaS
Oracle's licensing rules for public cloud environments are distinct from on-premises rules. On Oracle Cloud Infrastructure (OCI), Oracle applies a 0.5 core factor for all processor-based licensing, similar to its x86 treatment. On AWS, Azure, and Google Cloud, Oracle authorised in 2022 a specific counting methodology: each vCPU counts as 0.5 processor licences (i.e., 2 vCPUs = 1 processor licence) — but only under specific conditions and only for Bring Your Own Licence (BYOL) deployments. This is more favourable than the old full-host rule for these specific cloud environments, but the nuances matter significantly.
Database Editions and Cost Tiers
Oracle Database is sold in several editions, each with different feature sets, licensing restrictions, and price points. Understanding which edition you genuinely need — versus what Oracle's sales team sells — is an important cost lever.
Oracle Database Enterprise Edition (EE) is Oracle's flagship product, providing full feature access including partitioning, RAC, Data Guard, and all performance options. List price: $47,500 per processor (perpetual), $47,500 per year (annual). Enterprise Edition is appropriate for production databases requiring high availability, partitioning, or advanced performance features — but many organisations pay for EE when Standard Edition would fully meet their requirements.
Oracle Database Standard Edition 2 (SE2) limits deployment to a maximum of 2 sockets and caps NUP at 10 users on a 2-socket server. SE2 does not support RAC (Real Application Clusters) and excludes many enterprise features. However, for applications that do not require these features, SE2 list pricing is $17,500 per socket — roughly 37% of EE per-processor pricing — representing substantial savings for eligible workloads.
Database Options and Packs are add-ons to Enterprise Edition that carry significant additional licence costs. Oracle Advanced Compression: $11,500 per processor. Oracle Partitioning: $11,500 per processor. Oracle Real Application Clusters: $23,000 per processor. Oracle Diagnostics Pack and Tuning Pack: $5,800 and $11,500 per processor respectively. Enterprises frequently inadvertently activate these options through Oracle Enterprise Manager or default database configurations — creating compliance exposure without realising any option was enabled.
Negotiating Oracle Database Licences
Oracle Database licensing is among the most heavily discounted product categories in Oracle's portfolio, precisely because list prices are so high relative to actual transaction prices. Discounts of 50–70% off Oracle published list prices are the norm for enterprise-scale Oracle Database negotiations — but they do not materialise without deliberate negotiation strategy.
Leverage Alternative Databases
The most powerful lever in Oracle Database negotiations is a credible alternative. PostgreSQL (and its enterprise variants from EDB, Crunchy Data, and others), AWS Aurora, Google Cloud Spanner, Microsoft SQL Server, and MySQL Enterprise Edition all provide genuine migration paths for many Oracle Database workloads. Oracle's commercial team knows which workloads are practically migratable and which are not. Presenting a database migration assessment — even a preliminary one showing that 40% of your Oracle workloads could migrate within 18 months — changes Oracle's posture from "how much can we extract?" to "what do we need to offer to retain this account?"
Consolidate Oracle Spend
Oracle applies the most significant discounts to large, consolidated deals. Separate purchases of Database, middleware, and application licences attract lower individual discounts than a consolidated Oracle deal covering the full technology stack. If your organisation has Oracle Database and Oracle applications (EBS, PeopleSoft, JD Edwards), consolidating into a single negotiation gives you a larger deal value and access to Oracle's deeper discount tiers.
Avoid Licence Audits Through Proactive Compliance
Oracle LMS (Licence Management Services) audits are triggered by commercial disagreements, unresolved contract renewals, and Oracle intelligence about unlicensed deployments. Enterprises with strong internal Oracle licence management — conducting their own regular compliance reviews before Oracle does — have a fundamentally different negotiating position. They know their exposure, can quantify it, and can negotiate a true-up as part of a broader commercial agreement rather than responding defensively to an audit demand.
Related Resources
Back to cluster pillar: The Complete Guide to Oracle Licensing & Contract Negotiation.
Also in this cluster: Oracle ULA Negotiation Guide, Oracle Support Cost Reduction, Oracle Audit Defence Guide.
White paper: Oracle Negotiation Playbook — our complete guide to structuring Oracle Database negotiations.
Service: Software Licensing Negotiation — we represent buyers in Oracle Database licence negotiations. Case study: Oracle ULA Restructuring — 41% cost reduction for a global manufacturer.