When Oracle LMS or GLAS opens an audit, the first number is almost always a worst-case reading of your estate. We defend the customer side only: correcting the measurement scripts, applying the contractual core factor, and contesting soft-partitioning and disaster-recovery assumptions. Across our 340+ engagements that work cuts the initial Oracle compliance claim by 68% on average — and keeps the audit on the contract instead of Oracle's default interpretation.
Oracle audit defence is the independent, buyer-side management of an Oracle LMS or GLAS review from the engagement letter to the final settlement. We take over the technical and commercial response so Oracle cannot set the measurement, the timeline, or the price. We do not act for Oracle, resell its licences, or take vendor fees — we represent the customer alone, which is exactly what lets us contest a finding rather than rationalise it. The objective is simple: pay for genuine gaps, and nothing for Oracle's worst-case assumptions.
Most of the claim Oracle presents is interpretation, not entitlement. Their scripts count every installed option as used, treat passive disaster-recovery nodes as production, and ignore the core factor that should reduce your processor count. In our experience the difference between Oracle's opening position and the defensible number is consistently large — the 68% average reduction is not an outlier, it is what disciplined challenge of the measurement produces.
Do not run their scripts yet. We scope what is shared first. Talk to us before you respond.
The claim shrinks finding-by-finding, not through a single concession. This is the pattern we see most often across Oracle audits — Oracle's opening read on the left, the defensible position after review on the right.
| Finding area | Oracle's opening position | Defensible position | Driver of the reduction |
|---|---|---|---|
| Processor count | All physical cores, no core factor | Licensable cores × correct core factor | Contractual core-factor table applied |
| Database options | Every installed option counted as used | Only options actually deployed | Usage evidence vs. install evidence |
| VMware / soft partitioning | Entire cluster licensable | Scoped per contract and architecture | Partitioning and host-affinity facts |
| Disaster recovery | Standby treated as production | Failover / 10-day rule applied correctly | DR licensing policy correctly read |
| Java SE | Whole-organisation employee metric | Scoped or migrated to OpenJDK | Right-sizing and migration evidence |
The employee-metric exposure model, the OpenJDK migration path, and the LMS response checklist we use in live audits.
We run a controlled, buyer-side process from the moment the audit notice lands. Every step is designed to keep the measurement on the contract and the timeline on your terms.
We defend the claim and negotiate the deal as one motion — Oracle uses both as leverage, so we do too.
For the mechanics behind each finding above, read our Oracle audit defence guide, the Oracle Java audit defence breakdown, the Oracle LMS tactics teardown, and the Oracle licensing guide pillar. For the wider methodology, see our audit defence service and the cross-vendor vendor audit defence guide. Negotiating a renewal at the same time? Start with Oracle negotiation.
An Oracle audit is rarely just a compliance exercise — it is leverage for the next deal. Treating it as both, with independent buyer-side defence, is how the 68% average reduction turns into a settlement that protects the renewal as well as the claim.
From single-database reviews to enterprise-wide LMS engagements, we defend the buyer side only.
Weekly compliance intelligence for IT leaders.