Oracle Licensing Playbook 2026.

Oracle licensing in 2026: what this playbook covers

Oracle remains the most complex and the most audited software relationship most enterprises carry. Three things drive nearly every Oracle cost problem: the metric you are licensed on, how virtualisation is counted, and the gap between what you deployed and what you believe you own. This playbook works through each, with the contract language that decides the outcome.

Processor licensing through the Core Factor Table, Named User Plus minimums, and the rules Oracle applies to VMware and other soft partitioning are where exposure builds quietly. Oracle's published partitioning policy is not a contract document, yet it shapes how audits are argued, so the position you take on hard versus soft partitioning matters long before any audit letter arrives.

Java SE and the per-employee subscription

The 2023 shift to the Java SE Universal Subscription priced per total employee changed Java from a minor line item into a major one for many buyers. Knowing exactly where Java is installed, and whether a supported free alternative such as an OpenJDK build fits each use, is now central to controlling the bill.

ULA scope and exit

Unlimited Licence Agreements can be the right vehicle or an expensive trap. The value is decided at certification, where the count you declare becomes your perpetual entitlement. A ULA entered without an exit plan, or certified without a measured deployment, leaves money on the table or locks in products you no longer need.

Audit defence

Oracle audits run through License Management Services and follow a predictable pattern. Controlling the data Oracle sees, validating its measurement scripts, and reconciling your own position first are what reduce a claimed shortfall to a defensible number. The buyers who fare best treat the audit as a process to manage, not a verdict to accept.