The Oracle Database Licensing Guide

Oracle Database licensing is governed by two metrics, Processor and Named User Plus, multiplied through the core factor table and layered with options and management packs. Most overpayment comes from counting cores incorrectly, licensing options never used, and accepting Oracle measurement scripts at face value. This guide explains the ruleset and the buyer side defence.

Executive summary

Oracle Database is the highest exposure product line in most enterprise estates, and the one where the gap between what is owned and what is licensed is widest. The licensing model rests on two contractual metrics. The Processor metric counts physical cores, adjusted by the Oracle core factor table, and is the default for internet facing or uncountable user populations. The Named User Plus metric counts human and device users plus a per processor minimum, and suits bounded internal populations. The decision between the two is the single largest lever on cost, and it is frequently set wrong at the point of purchase and never revisited.

Layered on top of the base licence are the options and management packs, Partitioning, Advanced Compression, Advanced Security, Real Application Clusters, Diagnostics Pack, Tuning Pack, and others, each licensed separately and each a frequent audit finding. Oracle measurement scripts capture every feature ever touched, including options enabled by a database administrator during a one time test and never used in production. The buyer side defence rests on documentary evidence of who enabled what, when, and under whose authority.

This white paper sets out the complete Oracle Database licensing ruleset as an independent buyer side advisor applies it. It covers core factor mechanics, the Processor versus Named User Plus decision, soft and hard partitioning policy, the options and packs that drive audit findings, and the contractual definitions that decide disputes. It then presents the buyer side measurement and negotiation framework that has reduced Database audit claims by an average of seventy percent across the practice. The objective is not to win an argument with Oracle. It is to enter every conversation already knowing the answer, with cleaner data and a defensible position, before Oracle does. Read it alongside our Oracle Database licensing advisory service and the deeper Database licensing pillar.

What is inside

1. The core factor table explained, with worked examples across Intel, AMD, and SPARC processors and the most common counting errors.
2. The Processor versus Named User Plus decision framework, including the per processor minimum and when each metric wins.
3. Soft partitioning versus hard partitioning under Oracle policy, and what VMware, Solaris Zones, and OCI mean for your core count.
4. The options and management packs that drive the majority of audit findings, and how to prove non use.
5. A buyer side measurement and negotiation framework, with a five step audit response and prioritised recommendations.

Read by general counsel, IT procurement, and vendor management teams across thirty countries. Part of a fourteen paper buyer side library.

About the practice

Oracle Software Licensing is an independent buyer side advisory practice with offices in New York, London, and Stockholm. Across more than 750 Oracle engagements the practice has delivered an average audit reduction of seventy percent and over $300M in client savings, drawing on 20+ years of combined licensing experience. We do not resell or implement Oracle software. We measure estates, defend audits, and negotiate settlements on behalf of the buyer. Explore our audit defence service or request a consultation.