The Oracle Master Agreement or older OLSA sets the general terms and the ordering document records what you bought, so together they form the signed contract that governs your licensing, and the signed agreement beats any separate policy paper.
What are the OMA, OLSA and ordering documents?
The OMA, OLSA and ordering documents are the layers of your Oracle contract. The Oracle Master Agreement, or the Oracle License and Services Agreement that preceded it, contains the general legal terms that apply across everything you buy. The ordering document sits beneath it and records each specific purchase: the products, the metrics, the quantities and the price. Read together, top to bottom, they are the agreement. Anything that is not in that stack, including Oracle's published policy papers, sits outside the contract and carries different weight.
What does the master agreement do?
The master agreement sets the rules of the relationship. It defines the licensing metrics, the grant of rights, the support terms, the audit clause, and the definitions that every order inherits. When a dispute turns on what a term means, the master agreement is usually where the meaning is fixed. Older estates may still sit under an OLSA rather than an OMA, and the two are not identical, so the first step in reading any Oracle position is knowing which master terms actually apply to you.
What does the ordering document do?
The ordering document records the deal. It names the products you licensed, the metric for each, the quantity, and any special terms negotiated for that purchase. Where the ordering document grants something the standard terms do not, or limits something they would otherwise allow, the ordering document usually prevails for that order. This is why two companies under the same master agreement can have very different positions: the ordering documents differ, and the ordering document is where the specifics of your entitlement live.
| Layer | What it governs |
|---|---|
| Master agreement (OMA or OLSA) | General terms, metrics, audit clause, definitions |
| Ordering document | Products, metrics, quantities, special terms |
| Policy papers | Oracle position, not generally in the contract |
Does Oracle policy override the agreement?
Oracle policy does not override the agreement. Documents such as the partitioning policy describe how Oracle would like certain situations licensed, but they are not generally incorporated into the master agreement or the ordering document. Where the signed agreement is silent, weaker policy language cannot fill the gap in Oracle's favour, and where the agreement is stronger, it prevails. This is the core of the buyer side position on virtualization and many other findings: contract language beats policy, and the policy paper is not the contract you signed.
Which document controls in an audit?
The signed agreement controls in an audit. A finding is only as strong as the contract language behind it, so the first test of any claim is which document it rests on. A claim grounded in the ordering document and master terms is a contract claim and must be met on its merits. A claim grounded in a policy paper is a policy position, and where the contract does not support it the claim is weaker than it looks. Sorting a finding into contract grounded and policy grounded parts is often the most valuable early move in a defense.
How to read the contract stack
You read the stack from the top down and let the specific govern the general. Start with the master agreement to fix the definitions and the metrics. Move to each ordering document to see exactly what was bought and on what terms. Note where an ordering document varies the master terms, because that variation usually wins for that order. Finally, set any Oracle policy paper to one side until you have established what the contract itself says, because the contract, not the policy, is the measure. This ordered reading is what turns a pile of documents into a clear entitlement position.
A worked example
Consider an anonymized insurer facing a virtualization finding that licensed an entire cluster. The finding cited Oracle's partitioning policy as its basis. A reading of the contract stack showed the master agreement did not incorporate the policy and the ordering document granted licenses on a basis the cluster wide claim ignored. The defense answered the policy claim with the signed terms, and the contract grounded position held. The defensible exposure was a fraction of the opening figure, and it turned entirely on which document controlled. No client names, sector level example only.
The buyer moves
The buyer moves are to identify whether you sit under an OMA or an OLSA, gather every ordering document, read the stack from general to specific, and separate any finding into the part grounded in the contract and the part grounded in policy. Each move anchors your position in the signed agreement rather than Oracle's preferred reading, which is why a contract literate buyer rarely accepts a policy grounded finding at face value.
Where to go next
This piece links up to the Oracle License Compliance Guide. Keep reading across the cluster:
To read your contract stack against an Oracle finding, read the Oracle License Compliance Guide or book a strategy call.