Oracle Contracts and Licensing Agreements: OMA, ULA, PULA, OCS and CSI Explained

The Oracle Contract Architecture

Oracle's licensing framework is built on a hierarchy of documents. At the top sits the Oracle Master Agreement (OMA) — the overarching terms and conditions that govern the entire Oracle relationship. Below the OMA, individual Oracle License and Services Agreements (OLSAs), ordering documents, and statement of work documents define the specific products, quantities, support terms, and service commitments for each purchase.

A critical point that is frequently misunderstood: Oracle does not offer Enterprise Agreements in the way that Microsoft does for software. Oracle has no single agreement that covers unlimited use of all Oracle products for a flat annual fee. Every Oracle product requires specific licence entitlement, and the various agreement types available — ULA, PULA, OCS subscriptions — all cover only the specific products listed in the ordering document.

Organisations with long Oracle relationships typically have multiple layers of ordering documents accumulated over years of purchases, with different support renewal dates, different contractual terms (reflecting different Oracle standard agreement versions over time), and potentially different audit provisions. Consolidating this complexity into a coherent, current-terms agreement structure is itself a significant governance exercise — and a negotiating opportunity.

The Oracle Master Agreement

The Oracle Master Agreement (OMA) is the framework contract that governs all Oracle software licences, hardware orders, and service engagements for a customer. It defines the general terms for licence grants, support, warranties, indemnification, limitations of liability, and Oracle's right to conduct licence audits.

Key OMA Provisions to Understand

The OMA's audit provisions give Oracle the right to audit your Oracle software deployment once per year with reasonable notice. However, the specific terms of the audit right — what notice Oracle must provide, what scope they can audit, and what methodology they can use — vary by OMA version and can be negotiated. Organisations with older OMA versions may have broader or narrower audit rights than the current Oracle standard.

The OMA's support renewal provisions establish Oracle's right to increase annual support fees. Oracle's standard policy allows for annual support fee increases, and the current practice is to increase support fees by 8 percent per year. OMA versions negotiated with a support fee increase cap — limiting Oracle's ability to increase annual support fees beyond a specified maximum — provide significant long-term cost protection. Organisations that accepted Oracle's standard OMA without a support cap routinely face compounding support cost growth.

The OMA's licence grant provisions define what constitutes authorised use. Specifically, the definition of "authorised user," the permitted deployment environments, and the virtualisation permissions all flow from the OMA and are essential for understanding compliance exposure. Post-2015 Oracle OMAs often contain more restrictive virtualisation language than earlier versions.

Perpetual Licence Agreements

The most common Oracle licence type is the perpetual licence — a one-time purchase that grants the right to use a specific Oracle software product indefinitely, in the quantity and metric specified in the ordering document. Perpetual licences are the foundation of most enterprise Oracle estates.

What Perpetual Licences Include and Exclude

A perpetual Oracle licence grants the right to use the product as described in the Technical Support Policies applicable at the time of purchase. The licence does not include the right to use newer versions of the software — product upgrades require active Oracle support. It does not include the right to deploy the product on additional servers beyond those covered by the purchased licence count. It does not include the right to use Oracle software options or packs that are separately licensed, even if those options are technically present in the installed software.

Oracle's software options policy is one of the most common sources of compliance gaps in perpetual licence environments. Oracle Database Enterprise Edition comes with the technical capability to use dozens of separately licensed options — Advanced Security, Partitioning, Real Application Clusters, Multitenant, Label Security, Database Vault, and many more. Using any of these features without the corresponding option licence is non-compliant, even accidentally. Oracle's LMS audit scripts detect feature usage and generate compliance findings for any option used without a corresponding licence.

Annual support fees for perpetual licences are charged at 22 percent of the net licence fee annually, with the 8 percent annual increase applied at each renewal. For a perpetual licence purchased at $1 million net (after discount), initial annual support is $220,000, growing to approximately $427,000 per year after 10 years under standard Oracle support escalation.

Unlimited License Agreements (ULA)

An Oracle Unlimited License Agreement grants the customer the right to deploy unlimited quantities of specified Oracle software products during a defined term — typically three years. During the ULA term, the customer pays a fixed annual support fee regardless of how much of the covered software they deploy. At the end of the ULA term, the customer certifies (declares) the quantities of each covered product deployed, and those quantities become the customer's perpetual licence entitlements.

ULA Product Scope

A ULA covers only the specific products listed in the ordering document. Oracle does not have a ULA that covers "all Oracle products" — each ULA is scoped to a defined list of technology products (Database Enterprise Edition, specific middleware products, specific options). Products not in the ULA scope require separate perpetual licences.

The product selection in a ULA is one of the most important commercial decisions in any ULA negotiation. Including products that are expected to grow significantly in deployment volume captures the most ULA value. Including products where deployment is stable or declining dilutes the ULA economics by adding to the support fee without generating deployment-based savings.

ULA Certification — The Critical Exit Decision

At ULA expiry, the customer certifies deployed licence quantities which become their perpetual entitlements. ULA support fees are fixed regardless of deployment volume, so every additional deployment before certification captures perpetual licence value at zero marginal cost. This is the most important ULA principle: maximise deployment before the certification date. Organisations that certify early — before completing planned infrastructure deployments — permanently lose the ability to capture those deployments as perpetual licences.

Common ULA certification errors that reduce perpetual licence value include failing to count disaster recovery environments, test and development environments, and cloud deployments of ULA-covered products; using incorrect virtualisation methodologies that undercount virtual deployments; and certifying before scheduled infrastructure rollouts are complete.

Perpetual Unlimited License Agreements (PULA)

A Perpetual Unlimited License Agreement (PULA) is a ULA without a defined end date — it grants unlimited perpetual deployment rights for specified Oracle products with no certification requirement. PULAs are rare and expensive because Oracle prices them to reflect the theoretical maximum deployment risk. They are appropriate only for organisations that expect continuous, unlimited growth in Oracle software deployment over the long term and want to avoid the administrative burden of periodic ULA certifications.

Under a PULA, annual support fees are negotiated as a fixed amount and continue indefinitely. There is no certification event and no expiration. However, support fees under a PULA still increase annually — at the 8 percent per year standard Oracle rate unless a support cap is negotiated as part of the PULA terms. A PULA negotiated without a support fee cap will see its annual support obligation compound significantly over a multi-decade relationship.

Oracle Cloud Services (OCS) Agreements

Oracle Cloud Services agreements govern subscriptions to Oracle's cloud-hosted software offerings — Oracle Fusion ERP Cloud, Oracle HCM Cloud, Oracle CX Cloud, Oracle Autonomous Database, and Oracle Cloud Infrastructure (OCI). OCS agreements are subscription-based, meaning the customer pays recurring fees for access to the service but does not acquire perpetual rights to the software.

Key OCS Contract Provisions

OCS agreements specify the subscription term (typically one to five years), the committed service volumes (user counts, storage, compute capacity), the service level agreements (uptime commitments, response times, support tiers), and the data ownership and portability provisions. Unlike perpetual licences, OCS subscriptions grant no right to retain or use the software after the subscription expires.

OCS contracts for Oracle SaaS products (Fusion Applications) include provisions for price escalation at renewal. Oracle's standard OCS renewal terms allow for price increases at each renewal cycle. Without a contracted price escalation cap, SaaS renewal costs can increase by 8 percent or more per year — the same compounding dynamic as on-premise support fees. Organisations renewing Oracle SaaS contracts without independent advisory frequently accept renewal prices significantly above benchmarked market rates.

OCI (Oracle Cloud Infrastructure) OCS agreements are structured differently from SaaS OCS agreements. OCI is consumption-based infrastructure — the customer commits to a minimum monthly spend level and pays for actual usage above the minimum. OCI commitment agreements typically run 12 to 36 months, with discounts increasing for higher committed volumes and longer terms.

Customer Support Identifiers (CSI)

A Customer Support Identifier (CSI) is an Oracle-generated identifier that links a specific set of licensed Oracle products to a customer's Oracle support contract. Every Oracle perpetual licence purchase generates one or more CSIs — the CSIs are used to access Oracle support portals, log service requests, download patch sets, and receive security updates.

CSI Management in Practice

Large Oracle estates may have dozens or hundreds of CSIs accumulated across multiple purchases over many years, potentially with different support renewal dates. Each CSI represents a separate support contract line item with its own annual fee. Consolidating CSIs into a single support renewal event creates negotiating leverage — Oracle is more willing to negotiate support pricing on a large consolidated renewal than on individual small renewals.

Under a ULA, all individual CSIs for ULA-covered products are consolidated into a single CSI for the ULA term. This means the customer loses the ability to selectively terminate support on individual products (since they are now under a single ULA CSI), and the ULA CSI cannot be split back into individual CSIs during the ULA term without agreement from Oracle.

Post-ULA certification, the certified licence quantities generate new CSIs at the current Oracle support rate (22 percent of certified licence value). The timing of ULA certification determines the support fee basis — certifying later in the ULA term, with a larger deployed inventory, results in higher certified licence value and therefore higher post-ULA annual support fees. This is a deliberate tension in Oracle's ULA model: maximum deployment maximises perpetual licence value but also maximises ongoing support obligations.