Oracle license audits, from notice to settlement. Where the final number is decided.

An Oracle license audit is a commercial process in compliance language. The largest savings come early: a written scope before any script runs, a classification pass on the collection output, and a settlement priced as five years of support.

Who runs an Oracle license audit, and what is it for?

Oracle license audits are run by Global Licensing Advisory Services (GLAS), the Oracle function formerly called License Management Services (LMS). GLAS reports inside Oracle and is measured on outcomes, so expect a commercial process conducted in the language of compliance.

Every step, from the letter to the closure proposal, leads toward one of four outcomes, and each lands in an Oracle revenue line:

• A license purchase for the shortfall, with annual support attached.
• A cloud commitment, offered as Oracle Cloud spend in place of the purchase.
• An Unlimited License Agreement (ULA) that folds the finding into a larger deal.
• A Java subscription, where the finding concerns Java SE.

That is why closure proposals arrive so quickly after findings. None of the responses in this guide are about evasion. They are about accuracy, holding Oracle to the contract you signed, and not paying for software you do not run.

When is an Oracle audit most likely to arrive?

Audits cluster at the moments when Oracle's revenue model has the most to gain. Buyers notice the pattern, but few plan for it:

• After a ULA certification. The certified counts become the baseline that later deployments are measured against.
• After a large support reduction. Dropping support on part of the license base prompts Oracle to check what is still deployed.
• After a public restructuring. A merger, divestiture or reorganization changes which entities use the programs.

If you hold one of these events on your calendar, a notice arriving afterward is expected and your team can respond calmly. The contract basics are in our Oracle audit guide and the trigger patterns in the audit triggers analysis. Java audits follow their own track, where Oracle's opening evidence is a download log; see the Java audit defense guide.

What rights does the Oracle audit clause give Oracle?

The clause gives Oracle fewer rights than most teams assume. Oracle's published Master Agreement allows an audit on 45 days written notice. You provide assistance and information reasonably requested, the audit must not unreasonably interfere with your normal operations, and you have 30 days to remedy any shortfall.

Four words in that clause do most of the work for you. Notice gives you a schedule to plan against, and unreasonably puts a limit on disruption. Reasonably is the test every data request has to pass.

Remedy sets a 30 day deadline, counted from Oracle's written notification, to resolve a confirmed shortfall, which in practice usually means buying licenses, so the finding has to be right before that clock starts.

Are Oracle's partitioning and cloud policies binding?

Not on their own. Oracle's partitioning policy and its cloud licensing policy both close with the same disclaimer: the document is for educational purposes only and may not be incorporated into any contract. That sentence is printed on the very documents auditors quote at you.

Your executed agreement and ordering documents govern. Any terms you negotiated that differ from the standard are where your case on virtualization and cloud counting starts. See our analysis of the partitioning policy and the cloud licensing policy for the counting rules Oracle will cite.

Which audit terms should you ask for when you next sign with Oracle?

The clause is open to negotiation at signature and renewal. Oracle will refuse some of these terms, but each one you win narrows the next audit:

• Named entities. Audit rights limited to the legal entities that signed or use the programs, which keeps unrelated affiliates out.
• Formal notice only. Only a written notice under the audit clause starts the 45 day clock, which separates an audit from an informal review request.
• Frequency. No more than one audit in any 12 month period, so a closed audit cannot be reopened next quarter.
• Data limits. Collection only through Oracle's measurement tools, only for programs in scope, with no administrative access for Oracle staff.
• Remedy trigger. The 30 day remedy period runs from a final report both parties have reviewed, never from a draft.
• Contract over policy. Published policies apply only where an ordering document expressly incorporates them.

Our audit clause redline guide sets out wording for each of these terms.

How does an Oracle audit run from letter to settlement?

An Oracle audit runs in five stages: the letter, the scope negotiation, the data collection, the position paper and the closure. You have a response at every stage, and the early stages change the final number the most.

How should you treat the audit letter?

Classify it before anyone replies. The audit clause binds only formal notices, so an email inviting you to a license review is a request you can decline or accept on your own terms. Route every Oracle contact through the single response owner.

Our guide to what to do when the audit letter arrives covers the first written reply.

What should the scope letter name?

Agree the scope letter in writing in the first three weeks, before any script runs, and make it name:

• The legal entities under audit, matching the entity that signed the agreement.
• The programs in scope, by product name and customer support identifier (CSI).
• The environments in scope and those excluded, such as decommissioned or disconnected systems.
• The data channel: who sends what, in which format, to whom.

The first meeting with Oracle should produce a process: timeline, contacts, scope and data channel. Bring no data to it. Teams that send an inventory to the opening call give Oracle a scope it had not yet asked for.

Why are Oracle's first draft audit findings so often too high?

Oracle's first draft prices the raw collection output, an inventory of what is installed, as though every line were a confirmed finding. In our line by line reviews, first drafts were inflated 25 to 60 percent. The installation data was rarely wrong. The errors sat in which systems counted and how they were priced.

Three kinds of error produced most of that inflation:

1. Environment classification. Development systems classified as production, and systems your ordering documents treat differently counted on full production terms.
2. Dormant installations. Software still on disk but no longer running, counted as a live deployment.
3. Options enabled but never used. Database options and management packs flagged as enabled and priced as deployments, although no one had used them.

How can you check your own position before Oracle does?

Run the checks Oracle will run, before any data leaves your hands. For Oracle Database, these sources decide most disputes:

• DBA_FEATURE_USAGE_STATISTICS. The database view that records detected use of features and options, with first and last usage dates.
• Oracle's options and packs usage script. Published on My Oracle Support, it reads the same view and reports usage by option and management pack.
• CONTROL_MANAGEMENT_PACK_ACCESS. The initialization parameter that decides whether Diagnostics and Tuning pack features can be reached. On Enterprise Edition it defaults to DIAGNOSTIC+TUNING, so pack features can be used without anyone choosing to buy them.
• Change and decommissioning records. CMDB entries and retirement tickets that prove a flagged installation is dormant.
• Virtualization host history. Records from vCenter or your hypervisor console showing which hosts a database could run on, which Oracle will use to count processors.

See our guides to running the feature usage report before the audit script and reading LMS database script output. Note that Partitioning usage stays recorded after the objects are removed, so the view on its own does not prove current use.

How do you respond to Oracle's position paper?

Challenge the methodology against your reconciled record, and do not negotiate the total as presented. For every line, state whether you accept it, dispute the classification or dispute the count, and attach the evidence.

A total you agree to discuss becomes the starting point for every later offer, while a line removed on evidence stays removed. Our guide to challenging Oracle audit findings covers the disputes that come up most.

Why is haggling over the finding the wrong place to start?

The common advice is to accept Oracle's number as the opening position and push for a large discount at the end. We think that gets the order wrong.

On our engagements, the single largest reduction almost never came from the negotiation. It came from the scope letter, with the classification pass removing most of what was left. A discount only trims a number that is already too high, so settle scope and count first.

What does an Oracle audit settlement cost over five years?

Over five years a settlement costs roughly twice its license line. It carries 22 percent annual support that escalates about 4 to 8 percent a year, so a $1 million license finding becomes a commitment of about $2.2 million over five years. The invoice is the smaller half.

At either rate, five years of support cost more than the license itself, so put support into every comparison of closure options.

How do the four closure options compare?

The proposal shows one number, but each option carries its own payments over several years. Build all four as five year cash flows before you compare them:

• License purchase. The fee plus support at 22 percent, rising each year for as long as you keep the licenses on support.
• Cloud commitment. The committed spend for the whole term. Test whether you would consume that much Oracle Cloud anyway, and what happens to credit left unused at term end.
• ULA. The fee plus support for the term, and the support you keep paying on the certified licenses after it ends.
• Java subscription. Every year of subscription you will need, including the renewals after the first term.

When does Oracle have the most room to settle?

Oracle has the most room to settle from March to May. Its fiscal year ends May 31, and settlement authority widens materially in those last months. A closure that was impossible in October can become signable in April.

Have your reconciled position ready before March. Do not stall to get there, because unexplained delay weakens your claim to be cooperating reasonably.

What have we seen in recent Oracle audit responses?

Across the 60 to 80 Oracle audit responses I led from 2023 to 2025, Oracle's opening claim was rarely wrong about what software was installed. It was wrong about nearly everything that set the price: which environments counted, which installations were still live, and which options had ever been used.

• Scope. The scope agreed in the first three weeks shrank the systems under audit by 20 to 45 percent before any collection script ran, and that reduction held through every later stage.
• First drafts. The inflation came from the three errors described above, and the classification pass against the client's own records was what removed it.
• Volunteers. Half of the expensive audits we inherited had been widened by a helpful engineer answering a question no one had asked, which pulled environments outside the named scope into the audit.

A total you agree to discuss becomes the starting point for every later offer. A line removed on evidence stays removed.

What will Oracle's audit team say, and how should you answer?

These lines come up in most Oracle audits, and each has a short reply that keeps the process inside the clause:

• "Send us your deployment inventory so we can get started." Reply that you will send data once the scope letter is signed, only for the entities, programs and environments it names.
• "This is a friendly license review, not an audit." Reply that a review is voluntary, and that if Oracle wants to exercise the audit clause it should send written notice under it.
• "The partitioning policy means every host in the cluster must be licensed." Ask where your ordering documents incorporate that policy, since its own footer disclaims any contractual force.
• "We need administrative access to run the collection." Reply that the clause covers reasonable assistance, and that your team will run Oracle's measurement tools and return the output.
• "This offer is only good until the end of the quarter." Reply that you will answer when your reconciliation is complete, and that you are comparing every option on five year cost.

Which mistakes make an Oracle audit more expensive?

Beyond volunteering, four errors account for most of the avoidable cost we see:

1. Bringing data to the first meeting. An inventory handed over early sets the scope before you have negotiated it.
2. Treating the draft as an invoice. Paying against a draft concedes every error in it.
3. Comparing invoices. The option with the lower headline number can cost more once five years of support are counted.
4. Letting several people talk to Oracle. Different answers from different teams give Oracle inconsistent statements to hold you to.

What to do next

1. This week. Classify the letter, name one response owner, and take engineers off every Oracle call.
2. Before the first meeting. Prepare a process proposal covering timeline, contacts, data channel and draft scope, and bring no data.
3. Within three weeks. Agree the scope letter in writing, with entities, programs and environments named.
4. Before any output goes to Oracle. Run your own classification pass: production against development, live against dormant, used against merely enabled.
5. When the position paper arrives. Answer line by line with evidence, and quote the policy disclaimers wherever Oracle relies on policy instead of your contract.
6. Before you sign. Model every closure option as a five year cash flow and aim the signature at March to May. The Oracle practice can run the response with you.

Frequently asked questions