The measurement disputes that decide Oracle audits are core factor counts, options usage, cluster wide virtualization and Named User Plus, and winning them against the contract is why independent review typically cuts claims 60 to 80 percent.
Why do measurements decide the audit?
Measurements decide the audit because the finding is only as large as the counts behind it. Oracle audits run through GLAS, formerly LMS, and the preliminary finding arrives inflated at list price. Behind every inflated line is a measurement choice: how many processors, which options are used, whether a whole cluster counts, how many users. Win those measurement disputes and the number falls, regardless of the list rate applied on top.
How does the core factor table change the count?
The core factor table changes the count because processor licensing applies a factor to physical cores rather than counting cores at full value. A finding that ignores the correct factor, or applies the wrong one, overstates the processor requirement. Applying the right factor from the table to the right cores is often a straightforward correction with a large effect on the number.
| Dispute | Winning argument |
|---|---|
| Processor count | Apply the correct core factor to the right cores |
| Options usage | Show the option was never used and was disabled |
| Cluster wide virtualization | Test the claim against the contract, which beats policy |
| Named User Plus | Recount the real population against contract minimums |
How is the options usage dispute won?
The options usage dispute is won with usage evidence. Many options install by default, and a single Enterprise Manager click can flag Diagnostics or Tuning Pack as used. An accidental flag is not deployment. Gathering the evidence that a feature was never used in production, and was disabled on discovery, separates a genuine usage from a measurement artefact and removes the line.
How is the virtualization dispute won?
The virtualization dispute is won by reading the contract rather than the policy. Oracle's partitioning policy does not recognise VMware, Hyper V or KVM as hard partitioning and argues for licensing every host in a cluster. That argument rests on a policy paper, which is often weaker than the signed agreement. Where the contract does not grant the cluster wide basis, the claim falls, and on a large virtual estate that single dispute can decide the whole audit.
How is Named User Plus disputed?
Named User Plus is disputed by recounting the real population against the contract minimums. Findings inflate user counts by assuming every potential user is licensed or by applying minimums incorrectly. A careful recount, mapped to the actual people and devices that access each program, frequently lands well below the assumed figure.
A worked example
Consider an anonymized utilities firm whose finding overstated processors, flagged two packs and counted a full VMware cluster. The defense applied the correct core factor, proved the packs were never used, and defeated the cluster wide claim against the contract. Each measurement dispute removed a layer, and the defensible exposure landed near a quarter of the opening figure. No client names, sector level example only.
The buyer moves, in order
Winning the measurement disputes follows a clear order: apply the correct core factor, prove options usage with evidence, test virtualization claims against the contract, and recount Named User Plus against the real population. Done in sequence, these moves are why an independent line by line review typically cuts a preliminary claim 60 to 80 percent.
Where to go next
This piece links up to the Oracle Audit Defense Guide. Keep reading across the cluster:
To win the measurement disputes on your own estate, get a quote, or read the Oracle Audit Defense Guide.