The Oracle Licence Management Services audit runs in three phases: data collection, technical review, and findings. The Admodum read on each phase, the buyer-side response posture, and the audit-quality inventory that the buyer should hold before the first letter arrives.
Oracle Licence Management Services (LMS) is the publisher’s in-house licence-compliance arm. The team is staffed by Oracle employees and contractors and operates as a discrete function within Oracle. The output of an LMS audit is a non-compliance position, which Oracle then converts into a commercial settlement (typically a perpetual licence purchase plus back-support, or a cloud-subscription substitution).
The LMS audit is initiated by an audit notice letter, issued under the audit clause of the buyer’s Oracle Master Agreement (OMA), Oracle Licence and Services Agreement (OLSA) or earlier contractual form. The clause typically grants Oracle the right to audit on forty-five days’ notice and at reasonable intervals; the buyer’s response runs against the contracted clause rather than against any informal request.
The wider editorial sits in the Oracle pillar. The white-paper sits at Oracle LMS Audit Defence. The companion-article LMS scope-control sits at LMS scope control.
Phase one is the data collection phase. LMS requests deployment data from the buyer through a series of named instruments: typically the LMS scripts (a suite of database queries that read deployed cores, deployed options and feature-usage history), the user-list query (reading active and inactive Named-User-Plus accounts), and the environment manifest (production / development / test / standby).
The buyer-side response posture at phase one is the scope contestation. The audit clause typically grants LMS access to the contracted estate within the contracted scope. The buyer should read the audit notice against the contract clause and contest any scope expansion beyond the contracted entity, geography, product line or contractual right. The contestation is not adversarial; it is the buyer-side reading of the audit clause as written.
The deeper read on LMS scripts sits at LMS scripts in plain language. The deeper read on scope contestation sits at LMS scope control. Settlement framing sits at LMS settlement position.
Phase two is the technical review. LMS receives the buyer’s data and runs the analysis: deployed cores read against the core-factor table, virtualised hosts read against the partitioning policy memorandum, database options read against the entitled-option list, and Named-User-Plus counts read against the per-processor minima.
The technical review is the most contestable phase. The buyer-side discipline runs the same analysis in parallel against the same data and produces a counter-position. The two positions then meet at the technical review meeting (typically a series of remote sessions across two to four weeks). The buyer-side counter is not a refusal to engage; it is a documented, defensible alternative reading of the same evidence.
Phase three is the findings phase. LMS produces a draft findings letter, naming the alleged non-compliance position (typically expressed as additional processor licences required, plus back-support of two to three years). The findings letter is then converted into a commercial settlement proposal: a perpetual licence purchase, a cloud subscription substitution, or a hybrid.
The findings phase is therefore not a technical conclusion. It is the start of a commercial negotiation. The settlement options are open: list-price purchase is the publisher’s opening position; the buyer-side counter typically reads against the LMS-claimed scope, against the LMS-asserted partitioning treatment, against the back-support multiplier and against the proposed pricing.
The white-paper read on the settlement framing sits at Oracle LMS Audit Defence. The companion article sits at LMS settlement position.
The buyer-side response is materially stronger where it runs from a pre-existing audit-quality inventory. The inventory carries the deployed core count by host, by environment, by product; the partitioning treatment with the supporting affinity-rule evidence; the entitlement set drawn from contracts and ordering documents; the Named-User-Plus accounts with the active-versus-inactive read; and the licence-versus-deployment reconciliation by product.
The audit-quality inventory should be a continuous artefact, not a one-time response. The Admodum methodology runs the inventory build at engagement start and refreshes it quarterly across the engagement; the inventory then is available at the moment any audit letter arrives.
The engagement entry sits at the Oracle practice and the audit-defence programme at audit defence. The case-study read sits at case studies.
The buyer holds two structural positions at the close of an LMS audit. The first is the negotiated settlement (typically expressed as a discounted perpetual purchase, a multi-year cloud subscription, or a hybrid), against which the buyer carries forward the certified entitlement set. The second is the renegotiated audit clause inside the closing settlement, which the buyer can use to narrow scope, to extend notice periods or to require a more proportionate technical procedure on any future audit.
The settlement is also the moment to clean the wider contractual position. The Admodum methodology runs a parallel renewal review at the close of the audit, applying the negotiation leverage to a wider Schedule A repackaging, an OCI commitment design or a ULA renewal where the timing aligns. The wider read sits at Schedule A repackaging and the OCI commitment construct.
The wider editorial context sits in the Oracle licensing pillar. The aggregated reading list sits in the Oracle knowledge hub.
A senior Admodum Oracle advisor will read your audit position against the deployed estate on a private call. Active audits route to the Audit Defence programme; pre-audit inventory builds sit inside the Oracle practice.