Contents
Key takeawaysThe four document classesThe ordering documentReferenced policiesThe audit clauseSpecial grantsAfter an acquisitionWhat our reviews showedWording to ask forWhat to do nextFAQAn Oracle licensing agreement is four classes of document, and the price sits on a different page from the risk. Knowing which class governs which question decides every later dispute, and the documents that decide the most money are usually ones you never signed.
- Four classes, four roles. The master sets the rules, the order records the purchase, the documentation describes the program, and referenced policies set how Oracle applies the rules.
- The order beats the master. Under Oracle's online master an ordering document prevails in a conflict, so negotiated concessions belong in the order.
- Five fields on every order. Program name, metric, quantity, contracting entity and territory decide what you own.
- Referenced policies can move. Wording such as "as may be updated from time to time" gives Oracle the pen on rules you never read.
- The audit clause is a boundary. It sets 45 days notice and reasonable assistance, and names no specific script, grants no credentials and fixes no deadline for findings.
- Acquisitions add a second master. Each order stays under the master it was placed under, and standard terms bar transfers between entities.
Which documents make up an Oracle licensing agreement?
An Oracle licensing agreement is four classes of document: the master agreement, the ordering documents, the program documentation, and the policies the contract refers to without attaching them. Amendments and addenda sit alongside the master. Each class answers a different question and changes in a different way after you sign.
Confusing the classes is how buyers end up arguing the right point against the wrong document. A typical case is citing a policy page against a metric definition that the ordering document itself fixes, and losing because the order controls.
| Document | Answers | Changeable after signature | What you should do |
|---|---|---|---|
| Master agreement | What are the rules of the relationship | Only by mutual amendment | Negotiate audit, assignment and liability terms |
| Ordering document | What exactly did we buy | No, it is a fixed record | Check five fields before signature |
| Program documentation | What is inside the program we bought | Evolves with releases | Keep the version current at the order date |
| Referenced policies | How Oracle applies the rules in practice | Often revisable by Oracle | Pin the version or exclude it |
| Amendments and addenda | What did we change for this deal | Only by further amendment | File them with the master, not the order |
Which document wins when two of them conflict?
The document the agreement names wins. In Oracle's current online master agreement, a schedule overrides the general terms, and an ordering document overrides the master where the two conflict. The second rule works in your favor, because a concession written into the order beats the standard wording it contradicts.
The same agreement says Oracle's terms replace anything in your purchase order or procurement portal, so your own paper offers no protection. Changes need a writing signed or accepted by both parties, which means a promise in a sales email carries no contractual weight.
- Order of precedence. States which document controls when terms conflict. Read it before you negotiate anything else.
- Entire agreement. Limits what counts as part of the deal, which cuts both ways when a sales commitment was made outside the paper.
- Incorporation by reference. Pulls external documents in, and its wording decides whether you are bound to today's version or to whatever it becomes.
- Amendment. Sets how changes are made, and therefore whether a policy update can change your obligations without your signature.
How to Negotiate the Oracle Java Employee Agreement: Honest Leverage in a Captive Deal
What should you check on an Oracle ordering document before you sign?
Check five fields: exact program name, metric, quantity, contracting entity, and territory and use restrictions. The ordering document is the only place your commercial deal lives. Oracle's master grants use subject to the definitions and rules set out in the order, so the order also settles most definitional questions.
- The exact program name. Options and packs are separate programs with separate names. A near miss on the name is a gap in your entitlement, and it is the field we most often find wrong. Metric definitions sit in the license types guide.
- The metric. The counting rule you are buying, which governs how deployment is measured for the life of the grant.
- The quantity. Include any minimum the metric implies, which can exceed what the business thinks it needs.
- The contracting entity. Licenses sit with the legal entity named, and group structures change more often than contracts do.
- Territory and use restrictions. Where the program may be used and by whom, including affiliate and outsourcer language.
The order also records the term, the price and the customer support identifier (CSI) linking the licenses to a support contract. None of these live anywhere else, so when a support renewal quote shows a different quantity, the order is the record to reconcile against.
How long should it take to produce your order file?
About two hours, if every ordering document sits in one place with its amendments attached. In most disputes we work, rebuilding that file takes the first two weeks instead, while Oracle already holds its own copy. Until your file exists, only Oracle can state your entitlement position.
| Source | What it shows | What to look for |
|---|---|---|
| Signed master agreements | The rules, and which entity signed | A second master that arrived with an acquisition |
| Ordering documents and amendments | Program, metric, quantity, entity, territory, price | Options bought separately, or never bought |
| Support renewal quotes | Licenses on support, grouped by CSI | Quantities that differ from the orders |
| CSI list in My Oracle Support | Active support identifiers and their administrators | CSIs held by acquired entities |
| DBA_FEATURE_USAGE_STATISTICS and similar deployment data | Options and features actually used | Usage that no order covers |
Oracle CIO Guide
The renewal calendar, support rules and contract terms that shape Oracle spend over five years.
Get the white paper →Why does "as may be updated from time to time" matter in an Oracle contract?
That phrase hands the right to change your obligations to whoever writes the referenced document, which is Oracle. It usually follows a reference to a policy that is neither attached nor circulated. The signatories have rarely read the rules that later decide their dispute, and in file after file, that is where the money was.
The technical support policies show how it works. They are incorporated into the programs schedule of Oracle's online master and are "subject to change at Oracle's discretion," limited only by a promise not to materially reduce support during a period you have already paid for.
Which referenced documents decide the most money?
Four operational documents carry most of the counting logic. None sits on the signature page, and Oracle revises all of them without your involvement.
| Document | What it decides | Contract status |
|---|---|---|
| Partitioning policy | Which partitioning technologies can limit the processors you count | Says on its face it is educational, may not be incorporated into any contract, and can change without notice, so whether it binds you depends on your incorporation wording |
| License definitions and rules, published with the price lists | Metric definitions and minimums, which do the work in most user based disputes | Applied through the definitions and rules set out in the order |
| Cloud computing policy | How licenses are counted in third party clouds | Published and revised by Oracle |
| Technical support policies | Renewal mechanics, matching service levels, and what happens when you reduce quantities | Incorporated, and changeable at Oracle's discretion |
How do the support policies price a reduction?
They decide what a partial reduction actually saves. Three rules in the current policies do the work:
- Matching service levels. Every license in a license set must sit on the same support level, so dropping support on part of a set means terminating those licenses.
- Repricing. Terminate some licenses on an order, and support on the rest is repriced at current list less the applicable standard discount. The new fee can rise as high as what you paid for the whole order, plus country annual adjustments, and never falls below what you paid for the licenses you keep.
- Reinstatement. Letting support lapse and returning later costs 150 percent of the last annual support fee, prorated back to the date support lapsed.
Say, hypothetically, one order holds 20 processor licenses at $100,000 a year in support, $5,000 each, and you drop 5. You expect to pay $75,000. If current list less the standard discount for 15 licenses comes to $95,000, that is the new fee, since it sits between the $75,000 floor and the $100,000 cap. The saving is $5,000, not $25,000.
The contract side of these rules is covered in how Oracle incorporates its support policies. For any referenced document, the ask is small and often granted: reference it by title and date, and attach a copy as an exhibit. If Oracle says no, save a dated copy of the version in force on the day you signed.
A version you can produce is worth more in a dispute than an argument you have to make.
Where do Oracle's audit rights come from, and where do they stop?
Oracle's audit rights come from a single clause in the master agreement. Policies, support documents and the notice letter add nothing, because the letter only exercises the clause. The clause is therefore also the limit of what Oracle can require of you.
Under the current online master, Oracle may audit on 45 days written notice. You give reasonable assistance and access to information, and the audit may not unreasonably interfere with operations. Nothing shifts Oracle's cost of conducting the audit to you, but your cooperation costs stay with you, and a confirmed shortfall must be remedied within 30 days of written notification.
The current online wording says your assistance includes running Oracle data measurement tools on your servers and handing over the output. Check whether your signed master carries that sentence. If it does not, you owe information and reasonable assistance, and the method of collection is open to agreement.
What does the audit clause usually leave out?
The clause covers the programs licensed under that agreement, a narrower universe than everything Oracle you run. It also omits four things audit letters often ask for:
- A named script. Even the current tool wording names no specific script or version, so which scripts run, on which servers, is open to agreement.
- System access. It grants no credentials and no direct access to your servers.
- Other entities. It reaches only the entities the definitions bring in.
- A deadline for findings. Dates in the letter are proposals unless your clause sets them.
Anything asked for beyond the clause is a request you can negotiate. The claim stage is covered in fighting an Oracle audit claim, the budget in what an Oracle audit really costs, and the first days in what to do when the letter arrives.
Which Oracle licenses carry their own contract rules?
Special grants carry terms that differ from a standard full use license, so catalog them separately in your order file.
- Application specific licenses. An ASFU license is restricted to a named application, and any other use falls outside the grant.
- Embedded and distribution grants. They carry their own reporting duties.
- Free developer terms. They are not an enterprise entitlement.
- Unlimited agreements. A ULA ends with a certification obligation.
Java is the clearest case of audit language that diverges by document. Java taken under click through download terms and Java ordered under a master agreement sit under different wording, set out in our Java audit clause comparison.
How does an acquisition change which Oracle agreement governs?
An acquisition usually brings a second master agreement into the group, and each order stays under the master it was placed under. Unless someone maps this, people assume the parent's master governs everything, although the two can differ on audit terms, definitions and affiliate rights.
The standard online master defines "You" as the entity that signed it and allows use for internal business operations, including by agents and outsourcers. Affiliates get no right of use, and the programs may not be assigned or transferred to another entity. Older paper may sit under an earlier agreement type such as an OLSA.
What should you compare between two Oracle masters?
| Question | Where to look | Why it matters |
|---|---|---|
| Which entity is "You"? | Definitions, and the entity on each order | Licenses stay with the entity that bought them |
| Can other group companies use the programs? | Affiliate wording in the master or an amendment | Without it, use by a sister company is a finding |
| Can licenses move between entities? | Assignment clause and any merger amendment | Standard wording bars transfer |
| Which master governs each order? | The master reference on each ordering document | Precedence and audit arguments start here |
Carve outs raise the same questions in reverse, as our notes on the assignment clause and splitting entitlements explain.
What did our Oracle contract reviews in 2024 and 2025 show?
Across roughly 30 to 40 Oracle contract and dispute reviews in 2024 and 2025, the same three structural problems appeared in file after file.
- An incomplete order file. The buyer could not produce a complete set of ordering documents, so the entitlement position could not be stated without asking Oracle.
- The wrong master. The master in force was not the one people believed was in force, usually because an acquisition had brought in a second one.
- Unread references. Referenced documents had never been read, so the rules that decided the dispute were rules the signatory had never seen, and some Oracle can revise after signature.
Why we disagree with leaving Oracle's standard paper alone
A common line of advice says Oracle's paper does not move, so negotiating effort belongs on price. We disagree. Definitions and precedence are negotiable at signature and effectively never afterwards, and the requests are modest: a title and date for each referenced document, an attached copy, affiliate wording and an entity list.
The disputes we reviewed turned on those terms. Spend one negotiating round on the terms before the final price round, while Oracle still wants the order and the quarter still matters to the account team.
What contract wording should you ask Oracle for?
Ask for terms that fix the rules at signature and state who may use the programs. Our audit clause redlines go further on the audit section.
| Term to request | Why it matters |
|---|---|
| Referenced documents named by title and date, attached as exhibits | Later revisions stop applying automatically |
| Affiliate definition covering named entities and later acquisitions | The standard master covers the signing entity only |
| Right to assign on merger, reorganization or divestiture | Standard wording bars transfer |
| Master reference on every ordering document | Settles which rules govern each order |
| Audit limits on tools, format, credentials and the timetable for findings, including the right to supply data from your own records | Turns the gaps in the clause into written limits, and narrows the measurement tool obligation in the current wording |
| A cap on support increases in the order | Otherwise renewal pricing follows policies Oracle can revise |
What will the account team say, and how should you reply?
- "Our paper is standard and legal will not change it." Leave the master alone and put the concession in the ordering document, which prevails under Oracle's own precedence clause.
- "The policies are public and apply to every customer." Agree, and ask only that today's version be named by title and date and attached. That changes nothing Oracle publishes.
- "Affiliate wording needs legal review and will miss the quarter." Offer a schedule of named entities in the order instead of a new definition in the master. It is shorter to review and still covers the companies that run the programs.
- "You can sort out the entity question after signature." Decline. Once the order is booked, Oracle has no reason to reopen it, and the entity named on the order is the one that owns the licenses.
What to do next
- Build the order file. Put every ordering document in one place with its amendments attached, and map which master agreement governs each one.
- Read four clauses first. Order of precedence, entire agreement, incorporation by reference and amendment, before negotiating anything commercial.
- Find every "as may be updated from time to time" reference. Pin each document by title and date as an exhibit, or keep a copy of the version in force at signature.
- Check five fields on every new order. Exact program name, metric, quantity including implied minimums, contracting entity, and territory.
- Read the audit clause as a boundary. List what it grants and what it leaves out before any notice arrives.
- Get help mapping the stack. Our Oracle practice maps the agreement stack with you, and the Oracle knowledge hub holds the wider library.
Frequently asked questions
What documents are in an Oracle agreement?
Four classes: the master agreement, the ordering documents, the program documentation and the policies Oracle publishes separately. The master defines program documentation narrowly, as the user and installation manuals, so the counting rules live in the orders and the policies.
Which Oracle document wins when two of them disagree?
Whichever one the agreement names. Where an older or heavily negotiated agreement has no clear order of precedence, conflicts get settled by argument, which is the slowest and most expensive way to find out.
What does the Oracle ordering document actually decide?
Everything commercial and most things definitional: program name, metric, quantity, contracting entity, territory, term, support identifier and price. If an internal spreadsheet disagrees with the order, correct the spreadsheet. The exact program name is the field most often wrong.
Why does "as may be updated from time to time" matter?
It allows the author of the referenced document, Oracle, to change the rules after you sign. A dated copy of the version in force at signature is what you will argue from later, so keep it with the order even when Oracle attaches nothing.
Where do Oracle's audit rights come from?
From one clause in the master agreement behind the audited orders. The audit letter only exercises it. A group with two masters can face two different sets of audit terms, so check which master each audited program sits under.
What does the Oracle audit clause usually not grant?
A named script, system credentials, reach into entities outside the definitions, or a binding deadline for findings. Current online wording does require you to run Oracle data measurement tools, so propose in writing which servers and scripts are in scope before anything runs.
Which Oracle policies decide the most money?
The partitioning policy, the license definitions and rules published with the price lists, the cloud computing policy for third party clouds, and the technical support policies. The support policies can erase much of the saving a partial support reduction was meant to deliver.
When can definitions and precedence be changed?
At signature, and effectively never afterwards. Any later change needs an amendment both sides sign, and Oracle gains nothing by agreeing to one. Settle which master governs each ordering document, and which entities it covers, before the order is booked.