Oracle Processor Licensing vs Named User Plus: Which Metric Is Right for Your Deployment?

Oracle's licensing model is deliberately complex. That complexity is a feature, not a bug — it creates confusion that benefits Oracle during audits and renewals. The Processor vs Named User Plus decision is one of the most consequential choices an enterprise makes, yet most organisations have no idea which metric is costing them more or why.

The stakes are substantial. A company with 200 users and a 4-socket server running Oracle Database Enterprise Edition could owe anywhere from $800,000 to $2.4 million depending purely on which metric applies and how it's been calculated. Oracle's sales team will always recommend whatever generates the highest invoice — and it's rarely in your favour.

Our Oracle contract negotiation service has analysed hundreds of Oracle deployments. This guide distills what we've learned about choosing the right metric, calculating your true licence position, and negotiating the final number down.

The Processor metric licenses Oracle software based on the number of processor cores running the software, adjusted by a core factor. The core factor table — published by Oracle and updated periodically — assigns a multiplier to each processor architecture. Intel/AMD x86 cores carry a 0.5 factor, meaning a server with 32 Intel cores requires 16 Processor licenses. IBM POWER processors carry a 1.0 factor.

The critical word in Oracle's Processor metric definition is "running." Oracle defines this as any processor in a physical server partition or virtual machine where the Oracle software is installed and/or running, regardless of whether that software is actually in use at the time of measurement.

Core Factor Table: What You Need to Know

The core factor table has changed over Oracle's history. Factor changes are applied going forward, not retroactively — but many enterprises still use outdated spreadsheets for licence calculations. Key current factors:

The Virtualisation Problem

The Processor metric becomes dramatically more expensive in virtualised environments. Oracle's policy states that if you run Oracle software on a VMware cluster, you must licence all physical cores in the entire cluster — not just the cores assigned to the Oracle VM. Oracle does not recognise VMware's vSphere as a "hard partition" and will not accept VM-level licencing for Database Enterprise Edition.

This policy has caught hundreds of enterprises off guard during audits. A company running Oracle on one 8-core VM within a 10-host VMware cluster (each host with 32 cores) owes licences for all 320 cores — not 8. That's a potential difference of $10 million in licence exposure from a single miscalculation.

The Named User Plus (NUP) metric licenses Oracle software per named individual authorised to use it, regardless of whether they're concurrently using the software. A named user is defined as an individual authorised to use the programs which are installed on a single server or multiple servers, regardless of whether the individual is actively using the programs at any given time.

NUP also covers devices — any device (computer, terminal, workstation, telephone, pager, or electronic data interchange machine) that allows a named user to access and/or use Oracle software also requires a separate Named User Plus licence, unless that device is used exclusively by one named user.

What "Named User" Actually Includes

Oracle's definition of "named user" is broader than most procurement teams expect. It includes:

• All human users with database access — including read-only users who never write data
• Application accounts — if a middleware layer connects to Oracle using a single service account, Oracle may argue that all end-users of that application are named users
• Batch processes and automated jobs — depending on how they connect, these may require named user licences
• External users accessing Oracle via the internet — these can be licensed as a bundle under certain Oracle options, but the base requirement remains per named user

The "Plus" in Named User Plus refers to the requirement to also purchase support (annual maintenance) on top of the perpetual licence fee — typically 22% of the licence value per year.

The fundamental question is: at what user count does NUP licensing cost more than Processor licensing? Oracle publishes minimum NUP requirements (see below), but the break-even point depends on your specific processor count, core factor, and Oracle product.

For Oracle Database Enterprise Edition (list price $47,500 per Processor, $950 per Named User Plus):

When user count is below the NUP break-even point, NUP is cheaper. When you exceed it, Processor licensing wins. The practical reality: most enterprises with a large number of read-only or occasional users are over-licensed on Processor — and Oracle knows it.

Oracle imposes minimum NUP requirements on most products. These minimums mean you cannot use NUP to license a tiny number of users on a large server — you must meet the minimum regardless of actual user count. This is where Oracle's sales team frequently catches enterprises.

For Oracle Database Enterprise Edition, the minimum is 25 Named User Plus licences per Processor licence. This means:

• A 4-Processor server requires a minimum of 100 NUP licences ($95,000 list price)
• A 16-Processor server requires a minimum of 400 NUP licences ($380,000 list price)
• If your actual user count is below the minimum, you still pay for the minimum

For Oracle Database Standard Edition 2, the minimum is 10 NUP per Processor licence, and SE2 is limited to 2 sockets maximum. This makes NUP frequently more attractive for SE2 environments with small teams.

Minimums by Product Line

Moving Oracle workloads to cloud introduces significant complexity. Oracle's BYOL (Bring Your Own Licence) policy on AWS, Azure, and Google Cloud has specific rules about which instance types are "authorised" — and using the wrong instance type can void your BYOL rights entirely.

Oracle on AWS

Oracle on AWS EC2 with BYOL: licencing is based on the number of vCPUs in the instance, with a 0.5 core factor for Intel-based instances (2 vCPUs = 1 Processor licence). However, Oracle does not recognise AWS Dedicated Hosts as a partition mechanism — you must licence all vCPUs on the host, not just the VM.

AWS has published Dedicated Host configurations that Oracle recognises, but they're limited to specific instance families. Running Oracle on unsupported instance types while claiming BYOL is one of the most common audit exposure areas we see.

Oracle on Azure

Azure has a specific agreement with Oracle that authorises certain VM configurations. If you're on an Azure configuration that appears in Oracle's authorised deployment matrix, your licencing is based on the VM's vCPU count. Outside that matrix, Oracle defaults to full physical host licencing — a potentially catastrophic difference.

Oracle on OCI

Oracle Cloud Infrastructure handles licencing differently from AWS and Azure. On OCI, BYOL licences reduce your compute costs by 50-60% depending on product. The per-OCPU model on OCI is generally more favourable than on third-party clouds — which is by design, since Oracle wants to pull workloads to its own cloud.

Regardless of which metric applies, Oracle's list prices are always the starting point — never the finishing point. The question is how far you can move them.

Negotiating Processor Licences

Oracle's standard discounting on Processor licences typically starts at 10-20% for deals under $500K. For deals above $1M, you should target 35-50% off list depending on competitive alternatives, Oracle's end-of-quarter timing, and your negotiating leverage. Key tactics:

• ULA as an alternative anchor: A well-structured Unlimited Licence Agreement (ULA) can dramatically reduce per-Processor costs for high-growth environments
• Competitive displacement: Demonstrating a credible plan to migrate workloads to PostgreSQL, SQL Server, or open-source alternatives shifts the negotiation leverage
• Oracle fiscal year timing: Oracle's fiscal year ends May 31. Deals that close in Q4 (March–May) consistently receive larger discounts as Oracle sales teams chase quota
• Consolidation commitment: Agreeing to consolidate Oracle workloads onto fewer, larger servers reduces Oracle's licence count but can generate significant per-licence discounts

Negotiating Named User Plus Licences

NUP licences are often easier to discount because Oracle views them as volume deals. Tactics:

• User count documentation: Provide precise user counts with a clear methodology. Vague user estimates invite Oracle to estimate high
• Application user bundles: For applications with many read-only end users accessing Oracle through a middleware layer, negotiate an Application-Specific Full Use (ASFU) licence or Internet Application User (IAU) bundle — both are significantly cheaper than standard NUP
• Audit-ready compliance position: Demonstrating that you've done a rigorous internal licence review reduces Oracle's audit leverage and strengthens your negotiating position

Oracle's LMS team has specialised audit programmes for each metric type. Knowing what they look for helps you prepare.

Processor Metric Audit Traps

• Uncounted standby nodes: Oracle requires licences for Data Guard standby databases if they're on separate hardware. Many enterprises count only the primary
• Virtualisation non-compliance: Any VMware, Hyper-V, or KVM cluster without hard partitioning configured to Oracle's standards exposes every core in the cluster
• Options deployed but not licensed: Oracle Partitioning, Advanced Security, and Real Application Clusters (RAC) are separate products with separate licence fees — and Oracle's LMS scripts will detect them if they're installed
• Test/Dev environments: A common misconception is that non-production environments don't require licences. Oracle's policy requires licences for all environments where software is installed

Named User Plus Audit Traps

• Indirect access via applications: If your ERP system, CRM, or any middleware connects to Oracle, every user of that middleware system is potentially a named user under Oracle's interpretation
• Below-minimum licencing: Oracle will check whether your NUP count meets the minimum requirement based on the server's Processor count
• Shared accounts: Multiple people sharing a single Oracle account are all named users and require individual licences
• Former employee accounts: Named user licences follow named individuals, not active employment status. Terminated accounts that still exist in the Oracle database count

Before your next Oracle renewal or audit, work through these steps to understand your true licence position:

1. Run an Oracle Inventory (OI) script across all servers in your environment — the same script Oracle LMS uses. Know what Oracle will find before they find it
2. Map every server running Oracle software to its physical core count, core factor, and applicable metric (Processor or NUP)
3. Audit your virtualisation environment specifically for Oracle compliance. Identify any VMware, Hyper-V, or other hypervisor clusters where Oracle is deployed and compare against Oracle's partitioning policy
4. Count named users precisely — including application accounts, service accounts, and any middleware that connects to Oracle
5. Calculate your licence position against what you actually own. Identify gaps before Oracle does
6. Model the metric comparison — are you better off on Processor or NUP given your current user count and server configuration?
7. Engage independent expertise before Oracle's renewal team makes contact. Oracle's sales team will structure the deal to benefit Oracle

The enterprises that consistently pay the least for Oracle are those that negotiate from a position of complete information. Oracle's complexity is their advantage. Your job is to eliminate that advantage — or hire someone who already has.

Read our Oracle EA Negotiation Playbook for a comprehensive 40-page guide to the entire Oracle renewal process, or explore our Oracle License Review 2026 guide for current-year context. If you're facing an audit specifically, our Software Audit Defence service has resolved over $200M in Oracle compliance exposure.