What is GLAS, and what happened to LMS?
GLAS is Oracle Global Licensing and Advisory Services, the team that conducts license audits, and it is the same function that used to be called License Management Services, or LMS. The name changed, the role did not. GLAS measures your deployment against your entitlements, turns the gap into a number, and presents that number as a finding. If you have received a letter referencing GLAS or LMS, you are at the start of a formal audit, and the most useful thing to understand on day one is that the process is contractual, not a routine inspection.
The authority for the audit sits in your Oracle Master Agreement. Almost every Oracle agreement contains an audit clause that lets Oracle verify your usage, usually on written notice, with a defined response window of around 30 to 45 days. That clause is the rulebook. It also sets limits, because it is a negotiated contract term, and the limits run both ways. Reading the clause you actually signed, rather than the policy language Oracle quotes, is where buyer side defense begins.
Why does Oracle audit its customers?
Audits are also a sales channel, not just a compliance check. Analysts estimate that 20 to 30 percent of Oracle on premises license revenue comes from audits, which tells you the audit is a revenue mechanism with a process wrapped around it. The finding is rarely the end goal. It is the lever. A large number creates urgency, and that urgency is then pointed at a commercial outcome: a Unlimited License Agreement renewal, a cloud commitment on Oracle Cloud Infrastructure, or a Java SE Universal Subscription priced per employee.
Seen that way, the inflated preliminary number is not a mistake. It is an opening position. Oracle opens high because the gap between the opening claim and the settlement is the room in which a deal gets done. Understanding this changes your posture. You are not a defendant who has been caught. You are a counterparty at the start of a negotiation, and the first job is to slow the clock down to a pace that lets you verify everything before you concede anything.
How does an Oracle audit actually start?
An Oracle audit starts with a formal notification letter that cites the audit clause and proposes a timeline. The letter typically names GLAS, references your agreement, and asks you to nominate a contact and agree to a kickoff. This is the moment people make their first avoidable error: they treat the proposed timeline and scope as fixed. They are not. The response window and the scope are both negotiable, and the kickoff call is where that negotiation either happens or gets skipped.
Audits rarely arrive at random. The common triggers are worth knowing, because if one of them describes your roadmap, the time to get your position in order is before the letter, not after.
| Trigger | Why it draws an audit |
|---|---|
| Virtualization | Oracle policy does not recognise VMware as hard partitioning, so a cluster looks under licensed |
| Java downloads | Downloads without a subscription are visible to Oracle |
| Merger or acquisition | Estates combine and entitlements blur |
| Declining support spend | A drop signals possible deployment Oracle is not capturing |
| Rejected sales proposals | A declined deal can be followed by a compliance review |
| Cloud migrations | Moving workloads changes the licensing picture |
Do I have to run Oracle's collection scripts?
Running Oracle's collection scripts at all is a decision, not an obligation. This is one of the least understood points in the whole process. GLAS will provide measurement scripts and ask you to run them and return the output. The scripts gather data on what is installed and what has been used, and that output becomes the raw material for the finding. The trouble is that the scripts can overcount, especially across virtualization layers, where they may report a feature as in use across an entire cluster rather than on the host where it genuinely ran.
Because the output drives the number, it should be reviewed before it is submitted, not after. A buyer side review checks what the scripts captured, separates meaningful usage from incidental activity, and corrects the overcounts that virtualization and default installations create. Submitting raw script output without that review hands Oracle the most aggressive reading of your estate as the starting point. The agreement governs what you must provide, and within that, you control the quality and accuracy of what you submit.
What does GLAS usually find?
The classic findings repeat from audit to audit because they come from the same handful of mechanisms. Processor core shortfalls appear when the core factor table is applied incorrectly or ignored, so the same server carries a different license count than it should. Options and management packs show up as enabled when they were never deliberately licensed, because a single click in Enterprise Manager can register usage of Diagnostics or Tuning Pack, and many options install by default. Cluster wide virtualization claims appear because Oracle policy treats common hypervisors as soft partitioning. Named User Plus undercounts surface against per processor minimums, and disaster recovery mistakes appear around the 10 day rule for failover environments.
Each of these is contestable, and most rest on a distinction that favours the buyer once it is named: the policy document is not the contract. Cluster wide claims in particular often rest on Oracle policy papers that are weaker than the signed agreement, and where the contract is silent or more favourable, contract language beats policy. That single principle decides a large share of audit value.
What is the buyer move?
The buyer move is to treat the audit as a negotiation with a clock, and to control the clock, the scope, and the data in that order. Slow the timeline to the window your agreement actually allows. Agree a scope that matches the clause rather than Oracle's preferred breadth. Review every script output before it leaves your building. Then validate the preliminary findings line by line, because that is where the 60 to 80 percent reduction comes from. None of this is adversarial toward the people running the audit. It is simply insisting that the number be accurate before it becomes a settlement.
If you want the full process from letter to close, the Oracle audit defense guide walks through each stage. To go deeper on the moments that follow the letter, read the audit kickoff call and how to run it and why the preliminary report is an opening position.
The Oracle Audit Defense Handbook covers the response window, GLAS, options detection and settlement in one buyer side playbook. Free behind a work email.
FAQ
What is GLAS at Oracle? GLAS is Oracle Global Licensing and Advisory Services, the team formerly known as LMS that conducts license audits under the audit clause in the Oracle Master Agreement, usually with a 30 to 45 day response window.
Why does Oracle audit customers? Audits are also a sales channel. Analysts estimate 20 to 30 percent of Oracle on premises license revenue comes from audits, and findings feed ULA renewals, OCI commitments and Java subscriptions.
Do I have to run Oracle's audit scripts? Running the collection scripts at all is a decision, not an obligation, and the scripts can overcount across virtualization layers, so the output should be reviewed before anything is submitted.