Oracle Licensing Agreements Explained: OMA

Oracle wraps every license sale in one of six contract structures. The Oracle Master Agreement (OMA), the Oracle License and Services Agreement (OLSA), the Unlimited License Agreement (ULA), the Perpetual ULA (PULA), the Cloud Services Agreement (CSA), and the Oracle PartnerNetwork program agreement.

Each structure carries different rights, different exit doors, different audit exposure, and different commercial mechanics. The choice depends on the deployment footprint, the growth profile, and the renewal horizon.

Read this alongside the Oracle knowledge hub, the ULA decision framework, the Oracle services, and the Vendor Shield subscription.

Key Takeaways

What every Oracle customer needs to know about licensing agreements

Six structures. OMA, OLSA, ULA, PULA, CSA, OPN. Each carries different rights, scope, and audit exposure.
OMA is the master frame. Every Oracle order references the OMA. Negotiate the OMA terms once, every later order inherits them.
OLSA was retired. Pre 2010 deals still operate under OLSA. New deals run under the OMA frame. The two are not equivalent.
ULA is a two year window. Unlimited deployment for two to four years, then certification fixes the perpetual count. Get certification wrong and the exposure runs to eight or nine figures.
Cloud subscription is term limited. Cloud Services Agreement runs the duration of the subscription. No perpetual right.
Audit clause is universal. Every Oracle contract carries the same audit right. The procurement lever is the audit notice period and the data scope, not the right itself.
Renewal lever. Trade a multi year cloud commitment for OMA term improvements (audit notice period, partition language, M&A carve out, support cap).

Six contract structures, side by side

The six Oracle contract structures cover every Oracle commercial relationship. Knowing which one applies to a given product is the first step in any Oracle position assessment.

OMA, OLSA, ULA, PULA, CSA, OPN at a glance

Structure	Scope	Term	Audit exposure
OMA (Master Agreement)	Frame for all later orders	Perpetual frame	Audit right inherited by every order
OLSA (License and Services)	Pre 2010 master frame	Perpetual frame	Older audit language, narrower partition rights
ULA (Unlimited License)	Defined product list, unlimited deploy	2 to 4 years, then certify	Certification exposure, in scope product audit
PULA (Perpetual ULA)	Defined product list, unlimited perpetual	Perpetual unlimited	Scope drift, M&A boundary, cloud exclusion
CSA (Cloud Services)	OCI and SaaS subscriptions	Subscription term	Usage above commit, data export rights
OPN (PartnerNetwork)	Partner use rights	Annual	Embedded license boundary, partner audit

How the structures stack

OMA on top. Every later order references the OMA as the controlling frame.
OLSA legacy. Pre 2010 customers may still have OLSA in place. New product orders typically migrate to the OMA frame.
ULA inside OMA. A ULA is an Ordering Document under the OMA frame. The ULA replaces the per processor count for the in scope products during the ULA term.
CSA separate. Cloud services run under a separate Cloud Services Agreement, with cloud specific terms (service levels, data export, regional residency).

OMA scope and the terms that matter

The Oracle Master Agreement is the umbrella contract that frames every later license, support, and cloud order. Negotiating the OMA terms once protects every product line that follows.

Eight OMA terms that move on negotiation

Audit notice period. Default is 45 days. Target 90 days for enterprise customers.
Audit data scope. Default is broad usage data. Narrow to in scope products only.
Partition language. The VMware, Hyper V, and KVM partition stance is set here. Negotiate the right to operate hard partitions where physical CPU isolation is in place.
Support cap. Annual support uplift cap. Drive to 4 to 6 percent on a multi year cloud commit.
Repricing clause. The reprice to original list on partial drop default. Negotiate proportional pricing on partial drop.
Assignment. M&A carve in rights. Default blocks assignment to acquirers above a revenue threshold.
Definition of program. What counts as the in scope program. Tight definitions reduce audit exposure.
Definition of processor. Core factor table reference. Lock the version of the core factor table.

When to renegotiate the OMA

Before a ULA. The OMA terms control the ULA exit. Negotiate them before the ULA, not after.
Before a cloud commitment. Cloud subscription size lifts buyer side leverage. Use it.
Before an M&A event. Assignment rights matter on the divestiture or acquisition.
At a contract milestone. The 7 to 10 year renegotiation cycle is normal.

OLSA and the perpetual model

The Oracle License and Services Agreement was the master frame from the late 1990s through 2010. OLSA customers still operate perpetual licenses under OLSA, but new orders typically migrate to the OMA.

OLSA versus OMA differences

Term	OLSA default	OMA default
Audit notice	45 days	45 days
Partition language	Less explicit, more buyer flex	More explicit, broader Oracle interpretation
Cloud terms	None, predates cloud	Cloud reference in scope
Definition of program	Narrower	Broader (includes options and management packs by default)
Repricing on partial drop	Less aggressive	Aggressive list reprice default

The OLSA preservation play

Do not let Oracle force a migration to OMA without a commercial offset.
The OLSA partition language may be more favorable. Validate with legal review before agreeing to a migration.
Migrate selectively. Cloud subscriptions go under CSA. Perpetual licenses may stay under OLSA.
Document the controlling agreement on every order. Ambiguity favors Oracle in audit.

ULA mechanics and the certification trap

The Unlimited License Agreement gives unlimited deployment of a defined product list for a two to four year window, then a certification fixes the perpetual count. The certification math determines the exit value.

In scope and out of scope products

In scope. The defined product list (typically Database EE, RAC option, Partitioning, Diagnostics Pack, Tuning Pack, Advanced Compression).
Out of scope. Anything not on the list. Common pitfalls: WebLogic Suite, Identity Management, Coherence, GoldenGate.
Cloud exclusion. ULA deployments to authorized cloud (AWS, Azure) follow the cloud licensing policy (2 vCPU equals 1 Oracle processor on EE editions, 4 vCPU on SE editions). Deployments to OCI may receive different treatment, document in the ULA.
M&A boundary. Acquired entities can deploy only after a defined integration period (typically 90 days to 12 months).

The certification math

Deploy through the term. Maximize legitimate, in scope deployment by the certification date.
Document the count. Server inventory, partition disclosure, cloud deployment evidence.
Submit certification. Within 30 days of ULA term end.
The certified count becomes perpetual. Locked in at the closing position, supported indefinitely.

Cloud Services Agreement (CSA)

Oracle Cloud subscriptions, including OCI infrastructure, Oracle Cloud applications (Fusion ERP, HCM, SCM), and Autonomous Database, run under a separate Cloud Services Agreement. The CSA carries different mechanics from the OMA.

Cloud Services Agreement key terms

Subscription term. Typically 1, 3, or 5 years. No perpetual right.
Universal Credits. Pooled spend across OCI services. Annual draw down model.
BYOL. Bring Your Own License path lets perpetual customers deploy to OCI at a reduced rate.
Service levels. 99.95 percent default uptime. Negotiate higher for critical workloads.
Data export. Right to export data on termination. Validate the format and the timeline.
Regional residency. Customer choice of data center region. Document for GDPR, HIPAA, and other compliance.

CSA versus OMA perpetual

Dimension	OMA perpetual	CSA cloud
License grant	Perpetual	Subscription, term limited
Support	22 percent annual, perpetual	Bundled in subscription
Audit	Yes, broad	Yes, narrower scope
Termination	Customer can stop paying support	Customer must complete the term
Renewal	Optional	Required to retain access

Worked example: a 150M USD Oracle estate

A global manufacturer runs Oracle across 6,200 processors of Database EE, a partial ULA on RAC and Partitioning, and a 12M USD per year OCI subscription on Universal Credits. The contracts span a 2008 OLSA, a 2018 OMA, a 2022 ULA, and a 2024 CSA.

Current position

Contract	Scope	Annual cost	Renewal year
OLSA 2008	Legacy Database EE perpetual	4.4M USD support	Continuing
OMA 2018	Frame for later orders	--	--
ULA 2022	RAC, Partitioning, Diag, Tuning	14M USD per year	2025 cert
CSA 2024	OCI Universal Credits	12M USD per year	2027 renewal
Total	--	30.4M USD per year	--

The 18 month plan

Q1. Validate the OLSA controlling agreement on legacy Database EE. Preserve the partition language.
Q2. Build the ULA exit model. Validate in scope deployment, document the certified count, prepare submission package.
Q3. Submit ULA certification. Lock 220 processor count across the four products.
Q4. Renegotiate the OMA terms before the next major order. Audit notice to 90 days, partition language clarified, M&A carve in.
Year 2. Right size the CSA at the 2027 renewal. Trade a 5 year recommit for 35 percent unit price reduction and a 4 percent uplift cap.

Seven contract levers procurement carries

The seven Oracle contract levers

OMA renegotiation. Audit notice, partition language, M&A carve in, support cap, repricing clause.
OLSA preservation. Keep favorable legacy language on perpetual licenses where the OLSA wins.
ULA scope. Restrict the in scope product list to what will actually deploy unlimited.
ULA certification. Maximize legitimate, in scope deployment by the certification date.
Cloud commitment. Trade a 3 to 5 year cloud commit for OMA term improvements.
Support repricing. Negotiate proportional pricing on partial drop, not list reprice.
Renewal trade. Every renewal opens the OMA for renegotiation. Use it.

What to do next

The seven step checklist takes an Oracle contract position from current state to a negotiated renewal.

Map the controlling agreement on every Oracle product. OLSA, OMA, ULA, PULA, or CSA. The frame determines the rights.
Read the OMA boilerplate. Audit notice, partition language, definition of program, definition of processor, repricing clause.
Inventory the ULA scope. In scope products, current deployment, growth forecast through the certification date.
Build the cloud baseline. Universal Credits spend, BYOL deployment, OCI consumption forecast.
Identify the renegotiation event. Cloud commit, ULA exit, support renewal, M&A event.
Open the negotiation. Match the lever to the event. Demand OMA improvements as part of any cloud commit or ULA exit.
Document the renegotiated terms. In writing, in the order, on the master agreement amendment.

Frequently asked questions

What is the difference between an OMA and an OLSA?

The OMA (Oracle Master Agreement) replaced the OLSA (Oracle License and Services Agreement) in 2010 as the new master frame for Oracle commercial relationships. Pre 2010 customers may still hold OLSA perpetual licenses, with new orders migrating to the OMA frame.

The two agreements differ on definitions (program, processor), audit scope, partition language, and repricing on partial drop. Customers holding OLSA should validate which terms are more favorable before letting Oracle force a migration to OMA.

What happens if our ULA certification is wrong?

If the certification undercount, the customer leaves perpetual rights on the table. The unused deployment headroom evaporates at the certification date. If the certification overstates, the certified count locks in the inflated number, but the in scope product list controls. Out of scope products deployed during the ULA term remain a compliance exposure.

The audit pattern is to find post ULA deployments of products that were not on the in scope list. Those create compliance exposure at list price plus back support. Validate the certified count and the in scope products both before submitting.

Does the Cloud Services Agreement carry the same audit right?

The CSA carries an audit right, but the scope is narrower than the OMA audit. The CSA audit focuses on usage above the committed Universal Credits, the BYOL deployment evidence, and the regional residency compliance. Perpetual license audits run under the OMA, not the CSA, even where the perpetual licenses are deployed to OCI under BYOL.

The buyer side discipline is to keep the CSA scope narrow and the OMA scope clearly defined for any BYOL deployment.

Can we renegotiate the OMA mid term?

The OMA does not have a term in the traditional sense. It is a perpetual frame that controls every later order. Renegotiation typically happens at a contract milestone: a major new order, a cloud commitment, a ULA exit, an M&A event, or a support renewal.

The lever for renegotiation is the commercial value at the milestone. A 30M USD cloud commit, a 100M USD ULA, or a 50M USD support renewal each create the leverage to open the OMA boilerplate. The improvements (audit notice, partition language, M&A carve in) then control every future order under the master frame.

What is a PULA and when does it make sense?

A PULA (Perpetual ULA) gives unlimited deployment of a defined product list, on a perpetual basis, with no certification event. The customer pays a higher upfront fee and a higher annual support amount in exchange for the perpetual unlimited grant.

The PULA makes sense for customers with stable, predictable Oracle deployment, where the operational simplicity (no certification, no annual true up, no audit pressure on in scope products) outweighs the premium. It rarely makes sense for customers with declining Oracle footprint or active cloud migration.

How does Redress engage on Oracle contract advisory?

Redress runs Oracle contract advisory inside the Vendor Shield subscription, the Oracle services practice, and on engagement basis where an Oracle contract event is open. The output is a contract structure map, an OMA term assessment, a ULA scope and certification analysis, a cloud strategy memo, and a renegotiation playbook.

The engagement is led by Oracle commercial professionals on the buyer side. We have run Oracle contract advisory across pharma, banking, manufacturing, telecom, retail, and public sector customers running Oracle estates from 5M to 200M USD per year.

How Redress engages on Oracle contract advisory

Redress runs Oracle contract advisory inside the Vendor Shield subscription, the Oracle services practice, the Software Spend Assessment, and the Renewal Program.

Read the related ULA decision framework, the Java licensing, the database licensing guide, the contract renewal strategy, the contract negotiation service, the database ULA negotiation, the database pricing 2026, the Fusion cloud applications, the benchmarking page, the about us page, and the contact page.

Vendor Advisory

Cloud & Emerging

Programs

Assessments

Research

Knowledge Hubs

Assessment Tools

Oracle Licensing Agreements Explained. OMA, ULA, OLSA, and the choices behind them.