What is the structure of an Oracle Master Agreement?
An Oracle Master Agreement, or OMA, is a framework contract that sets the general terms, while the specific programs, quantities, and metrics you bought live in the ordering documents that attach to it. The framework and the orders work together: the OMA, which replaced the older Oracle License and Services Agreement, supplies the definitions, the audit rights, the support terms, and the general conditions, and each ordering document grants named programs under named metrics in named territories. To know your position you read both layers, because neither alone tells the whole story. The OMA without the orders is rules with no inventory. The orders without the OMA are inventory with no rules.
This structure is why a finding cannot be judged from a spreadsheet of deployments alone. The deployment has to be read against the grant in the orders and the definitions in the OMA. When the two layers and the finding are laid side by side, the lines that do not follow from the contract become visible, and those are the lines that come out on review. This topic links up to the Oracle license compliance guide for the standing compliance picture.
How do you read the grant and the metrics?
You read the grant and the metrics by listing exactly which programs each ordering document licenses, under which metric, and in what quantity, then checking how each metric is defined in the OMA. The grant tells you what you are entitled to deploy. The metric tells you how that entitlement is measured, and this is where most findings are won or lost, because a finding often applies a stricter count than your defined term requires. Two metrics dominate. Processor counts cores against the core factor table, so the hardware and the factor decide the number. Named User Plus counts authorised users and devices, subject to per processor minimums that can lift the count above your actual user base.
Read the definitions of these terms in your specific agreement, not from memory, because the wording varies between agreements and over time, and a favourable older definition is a real asset. Check the minimums, the territory, and any program specific notes in the order. For the metric comparison, read processor versus Named User Plus. Where a definition is ambiguous or you cannot locate the governing wording, treat the answer as contract dependent and resolve it before conceding anything that depends on it.
The grant is what you may deploy. The metric is how it is counted. A finding lives or dies on the metric definition in your agreement, so read that definition before you accept any count Oracle applies.
What does the audit clause actually say?
The audit clause gives Oracle the right to verify your use against your entitlements, typically on notice, and it is the source of the 30 to 45 day response window that frames an audit. Read it closely, because it defines the boundaries of what Oracle can do, not an open licence to demand anything. It usually specifies notice, a frequency limit, an obligation to cooperate reasonably, and a process. What it generally does not do is require you to run Oracle's collection scripts on demand or accept Oracle's interpretation of every policy as binding. Running the scripts is a decision, and the script output is reviewed before it leaves your network because it can overcount across virtualization layers.
The response window inside the clause is more flexible than it first appears. The timeline and the scope can be negotiated before you agree to anything, and confirming the scope in writing prevents an audit from expanding beyond what the clause supports. The clause is the buyer's friend here, because it bounds the exercise. For the window in detail, read the audit clause in your Oracle contract.
What is incorporated by reference, and why does it matter?
Incorporation by reference is the mechanism by which an external Oracle document, such as the partitioning policy, can become part of your contract, and it matters because that is the only way a policy paper binds you. Look for language that names an external document and states that it forms part of the agreement. If the partitioning policy is incorporated, the cluster wide virtualization argument has a contractual footing. If it is not, the policy is Oracle's opinion, and a finding built on it can be narrowed to what the agreement actually supports. The same logic applies to other Oracle documents that a finding might lean on.
| Read | What it tells you |
|---|---|
| Ordering documents | Programs, metrics, quantities, territory |
| OMA definitions | How each metric is measured |
| Audit clause | Verification rights and the response window |
| Incorporation by reference | Whether external policies bind you |
This is the heart of why contract language beats policy. A finding may assume every Oracle policy applies, but only the documents your agreement adopts actually do. For the principle in full, read the agreement review before any audit.
Our Oracle compliance workbook gives you a structured way to read your agreement, map your entitlements, and test a finding against the contract. We reduce your Oracle exposure or we reimburse our service fee, on a Fixed Fee or Gainshare basis with no risk to you.
What is the buyer move?
The buyer move is to read your agreement before an audit arrives, mapping the grant, the metrics, the audit clause, and what is incorporated by reference, so a finding meets a prepared reader rather than a surprised one. Build a clean record of which programs you own under which metrics, note the favourable definitions, and know what your contract does and does not adopt. When a finding lands, test each line against that record, and flag anything that depends only on a policy your agreement never incorporated. Where the governing wording is unclear, treat it as contract dependent and confirm it. To have your agreement read and your exposure assessed before any audit, book a strategy call, and work up to the Oracle license compliance guide.
FAQ
What should you read first? The grant in the ordering documents and the metric definitions in the OMA, then the audit clause and anything incorporated by reference. Most findings turn on a defined term.
Does the OMA include the partitioning policy? Not unless incorporated by reference. The policy is a separate document, which is why contract language beats policy and cluster wide claims can be narrowed.
Why does reading the agreement cut exposure? A finding must rest on what you signed. Tested line by line against the contract, findings are typically cut 60 to 80 percent.