Oracle Contract Terms Glossary60+ Terms Decoded: What Oracle Says, What It Actually Means, and What You Should Negotiate

NUP has minimum requirements per processor — typically 25 NUP per processor for Enterprise Edition, 10 per processor for Standard Edition 2. This means even if only 5 people use the database, you must licence a minimum of 25 NUP per processor. Oracle audits routinely flag the gap between "named users" and "minimum NUP per processor" as non-compliance. Always calculate the minimum before choosing NUP over Processor licensing.

Virtualisation creates enormous complexity. In VMware environments, Oracle's position (contested but enforced through audits) is that all physical cores in a cluster must be licensed unless you use Oracle-approved hard partitioning (Oracle VM, Solaris Zones, or physical capping). A 4-server VMware cluster with 80 cores × 0.5 = 40 Processor licences — even if Oracle runs on only one VM. This single interpretation drives more audit exposure than any other Oracle licensing rule. See Licensing in Virtual Environments.

The Employee metric is a headcount trap. If you licence PeopleSoft HCM on the Employee metric, every employee in your organisation counts — including those in business units that never touch PeopleSoft. Oracle counts headcount from public filings or HR system data. The Application User metric is narrower but requires careful tracking. See PeopleSoft Licensing Guide for the four distinct approaches.

The Core Factor Table applies only to on-premise Processor licensing. Oracle's position is that it does not apply in Oracle Cloud Infrastructure (OCI) — cloud pricing uses OCPUs (Oracle Compute Units) with their own counting rules. Also, Oracle can update the Core Factor Table at any time for new processor architectures. When ARM-based servers enter your data centre, verify the applicable factor before deploying Oracle software.

Oracle HCM Cloud uses Hosted Employee, meaning every active HR record counts toward your subscription — including contractors, contingent workers, and pre-hires. For Oracle ERP Cloud, Hosted Named User is more common, restricting cost to actual users. The metric you negotiate directly determines whether cloud costs scale with your workforce size or with your user count — a distinction that can mean a 2–5× difference in cost. See Hosted Named User vs Hosted Employee.

Most organisations signed their OLSA 10–20 years ago and have never renegotiated it. The OLSA is negotiable — particularly the audit clause (Section 10), the termination provisions, and the limitation of liability. Renegotiating the OLSA before a major renewal or cloud migration can yield structural improvements that benefit every future Oracle transaction. Your OLSA terms cascade into every Ordering Document. Learn more about independent Oracle advisory services.

Your Oracle estate is the sum of all Ordering Documents — often accumulated over 15–20 years across dozens of separate purchases. During an audit, Oracle's compliance team reviews every Ordering Document to determine your total entitlement. Organisations frequently discover they have Ordering Documents for products they no longer use (shelfware) or duplicate licences purchased by different business units. A comprehensive Ordering Document inventory is the foundation of any licensing optimisation exercise.

The ULA is Oracle's most powerful commercial instrument. It creates a dependency cycle: deploy freely during the term, then face enormous pressure to renew (because certifying at lower-than-expected quantities feels like "leaving value on the table"). Oracle's sales teams present renewal as the default path. Certification — exiting the ULA with locked perpetual entitlements — is almost always the better commercial outcome, but requires careful preparation. See ULA vs PULA: Understanding the Two Models.

The PULA eliminates certification risk but locks you into perpetual Oracle support payments on an agreed fee base — typically $2M–$10M+ annually. Oracle cannot audit your PULA product deployments (because they are unlimited), but they can and do audit non-PULA products. PULAs are commercially attractive for organisations with large, growing Oracle estates — but the support obligation is a permanent cost. See Oracle PULA: 10 Contract Traps.

Your CSI number is your lifeline to Oracle support — and Oracle's primary mechanism for tracking your licensing. When you log an SR, Oracle can see your entire licensed estate through the CSI. Organisations with multiple CSI numbers (from acquisitions, different business units, or separate purchasing entities) often have fragmented visibility into their total Oracle entitlement. Consolidating CSI numbers is a governance best practice — but do it carefully, as consolidation can expose previously invisible compliance gaps.

The 22% rate is non-negotiable — Oracle does not discount the support percentage. However, the base on which 22% is calculated (the Net Licence Fee) is determined by your original purchase discount. A 50% discount on a $1M list-price licence means support is 22% of $500K = $110K/year. A 30% discount means 22% of $700K = $154K/year. The negotiation leverage is in the licence discount, not the support rate. Annual support uplift (typically 3–4%) compounds this base every year. See Dropping Oracle Support and Reinstatement.

This is Oracle's most effective deterrent against support termination. If you drop support to save $200K/year and want to reinstate after 3 years, you owe $600K in back-support plus $900K in penalty (150% × $600K) = $1.5M. This makes the decision to drop support nearly irreversible — which is exactly Oracle's intent. The workaround: if you drop support, commit fully. Transition to third-party support for ongoing maintenance, and accept that returning to Oracle support means repurchasing licences rather than reinstating.

Sustaining Support is the trap: you pay the same 22% annually but receive only access to previously released patches and the My Oracle Support portal. No new security patches, no bug fixes, no regulatory updates. You are paying full price for a fraction of the service. When your product enters Sustaining Support, evaluate third-party alternatives immediately — providers like Rimini Street and Spinnaker offer full support (including new patches for tax and regulatory changes) at 50% of Oracle's price. See Oracle Third-Party Support Providers.

Unlike perpetual licences (which you own forever), SaaS subscriptions are rentals. When the contract ends, you lose all access — including your data, unless you have negotiated explicit export provisions. Oracle's standard SaaS terms provide a 60-day data export window post-termination, but the data format is Oracle-proprietary unless you negotiate otherwise. Insist on: defined data export formats (CSV/XML, not Oracle-only), 180-day export window, and continued read-only access during transition. See Negotiating Oracle SaaS Contracts. Learn more about Oracle contracts and licensing agreements.

Migration credits are not a programme — they are a negotiation. Oracle has no published formula, no minimum credit entitlement, and no obligation to offer them. Initial credit offers of 15–25% are starting positions; structured negotiation achieves 30–50%. The credits are applied as subscription discounts, not as transferable value. Never accept the first credit offer, and never tie credits to PeopleSoft/EBS support termination dates. See PeopleSoft to HCM Cloud Migration Guide.

Universal Credits expire at the end of the contract term — unused credits are forfeited. Oracle's sales teams size credit pools based on projected maximum usage, creating a systematic over-purchasing dynamic. Negotiate: annual true-up/true-down (ability to adjust the credit pool at each anniversary), credit rollover provisions (unused credits carry forward), and flexible service allocation (credits usable across any OCI service without restrictions).

BYOL is compelling but contractually complex. Your on-premise licences must be fully paid up on support to qualify. The licence-to-OCPU conversion ratios differ from on-premise core counting. And critically: licences used for BYOL in OCI cannot simultaneously be counted toward your on-premise deployment — if you BYOL to OCI and still run on-premise, you may create a compliance gap. Audit your entitlements carefully before committing to BYOL. See Oracle Applications on AWS: Licensing Guide for multi-cloud considerations.

On support, the standard uplift is 3–4% (applied to the support fee, not the licence fee). On cloud subscriptions, the uplift can be 3–8% depending on what you negotiated. A 4% uplift on $1M support adds $216K in cumulative cost over 5 years. Negotiate flat (0%) uplift where possible, or cap at CPI. On cloud, always negotiate uplift as a specific term — Oracle's default is "list price at renewal" which gives them uncapped pricing authority.

The NLF is the most important number in your Oracle relationship — it determines your permanent support obligation. A deeper discount on the initial licence purchase reduces support costs for the entire life of the licence. This is why Oracle sales teams resist deep licence discounts: every dollar of discount reduces Oracle's perpetual support revenue stream. Conversely, when Oracle offers a "great deal" on a new licence, verify it is a genuine NLF discount and not a one-time credit that leaves the NLF (and therefore support) at a higher level. See Oracle Pricing Benchmarks.

Co-termination benefits Oracle by creating a single, high-stakes renewal event where your entire Oracle estate is at risk simultaneously. This maximises Oracle's leverage — you cannot selectively walk away from one product without affecting the rest. The alternative: staggered renewals that allow you to negotiate each product area independently. If you must co-terminate, ensure you have contractual flexibility to reduce scope on individual products at each anniversary, not just at the co-termination date.

Organisations that expand globally or undergo M&A frequently discover their Oracle licences are restricted to specific legal entities or geographies. Deploying Oracle in a newly acquired subsidiary — even if that subsidiary is in the same country — may not be covered by existing licences. Review territory restrictions in every Ordering Document before organisational changes, and negotiate "worldwide" or "enterprise-wide" deployment rights where possible. See Oracle Licensing in M&A Due Diligence.

Oracle uses audits strategically — not randomly. Audits are triggered by: upcoming renewals (to create urgency), cloud migration discussions (to establish leverage), M&A activity (to capture new entities), and declining support revenue (to identify unlicensed usage that can be converted to new purchases). Your audit response strategy matters enormously. See How Oracle Selects Audit Targets.

GLAS is not a neutral auditor — it is an Oracle revenue function. GLAS findings are reviewed by Oracle's sales organisation and used as leverage in commercial negotiations. You are not obligated to run GLAS scripts on every server they request — review the scope carefully and limit data collection to what your OLSA contractually requires. Always conduct an internal self-assessment before allowing GLAS access. See Interpreting Oracle LMS Script Output. Learn more about Oracle audit defense and response.

Oracle's audit findings typically overstate the compliance gap because they interpret licensing rules in Oracle's favour (particularly around virtualisation, multiplexing, and territory restrictions). An independent review of audit findings commonly reduces the stated gap by 30–60% through legitimate counter-arguments: correcting virtualisation assumptions, identifying licences in different Ordering Documents that GLAS missed, demonstrating that non-production environments qualify for testing-use-only terms, and challenging Oracle's interpretation of deployment metrics. Never accept GLAS findings at face value. See Case Study: NOV Inc — $22M Saved.

Shelfware is the single largest source of immediate savings in most Oracle estates. We typically find 15–30% of licensed products are shelfware, representing $100K–$1M+ in avoidable annual support costs. Identifying and terminating shelfware support requires a complete inventory of Ordering Documents mapped against actual deployment. Oracle will not proactively tell you which licences are unused. See Case Study: Costco — $4.2M Saved by Terminating Unused Licences.

Without true-down rights, you are locked into your current licence count regardless of usage changes. Organisations that restructure, divest, or optimise their Oracle deployments save nothing unless they can reduce the support base. Negotiate annual true-down rights of 15–20% at each contract anniversary. Oracle will resist — support revenue reduction is the most painful concession they make — but it is achievable with competitive leverage and multi-year commitment.

Oracle's support business generates $8B+ annually at 90%+ margins. Every dollar of support you threaten to move to third-party providers is a dollar Oracle is acutely motivated to protect. Organisations that present a documented third-party support evaluation — with pricing, scope, and a transition plan — consistently achieve 15–30% better outcomes on renewal negotiations. The evaluation does not need to result in a switch. It needs to be credible enough that Oracle takes it seriously. See Case Study: Technip Energies — €12M Savings and Case Study: Adecco — €12M Savings.

Deals closed in Oracle's Q4 typically achieve 10–20% deeper discounts than identical deals closed in Q1 (June–August). The effect compounds: a $2M deal at 40% discount in Q4 versus 25% discount in Q1 saves $300K in licence cost — and $66K annually in perpetual support savings (22% of the $300K difference). For major Oracle transactions, timing is one of the highest-ROI negotiation levers available. See How to Negotiate Oracle ERP Cloud Pricing.

Certification is the most consequential commercial event in the ULA lifecycle — and the one Oracle's sales team works hardest to prevent. Oracle's preferred outcome is ULA renewal (perpetuating the support revenue stream). Your best outcome is usually certification (locking in perpetual entitlements and eliminating the ULA premium). Certification requires meticulous deployment counting: every Oracle Database, WebLogic, or Middleware instance must be inventoried, attributed to the correct metric, and documented. Under-counting during certification means you certify fewer licences than you actually need — creating immediate non-compliance. Over-counting means you certified more than deployed, which is wasteful but not harmful. See PULA Lifecycle Planning.