If you read nothing else
An Oracle SAM programme is a continuous, buyer-side practice that discovers every Oracle deployment, reconciles it against entitlements, and keeps an independent effective-licence position year-round — so an Oracle GLAS audit becomes verification, not discovery. Built well, it produces audit-ready evidence on demand, right-sizes support before renewal, and is the single most effective defence against a 3–5× back-licence claim.
Software asset management is the discipline of knowing exactly what Oracle software you have deployed, what you are entitled to, and where the gap is — measured on your terms, not Oracle's. Oracle's audit arm, now branded Global Licensing and Advisory Services (GLAS) rather than the old License Management Services (LMS), runs audits as a revenue exercise. The buyer's only durable counter is to hold a forensic, independently maintained licence position that is more accurate than Oracle's, available the day a 45-day notice lands. This playbook sets out how to build that programme, what to measure, who owns it, and how to right-size Oracle spend as a by-product of running it.
Key Takeaways
- An Oracle SAM programme is the discipline of continuously reconciling deployed Oracle software against entitlements to hold an independent effective-licence position — the best Oracle audit defence there is (Oracle Licensing Experts engagement data, 2026).
- Only around 10 tools globally are recognised by Oracle GLAS as producing audit-grade measurement data; using an unverified discovery tool can mean redoing the count under audit pressure (Oracle GLAS verified-tool guidance, 2026).
- Oracle support is billed at 22% of net licence value every year, so right-sizing the deployed estate through SAM directly cuts the largest recurring Oracle line item (Oracle Technical Support Policies, 2026).
- The most expensive SAM blind spots in 2026 are Java SE per-employee exposure, Oracle on VMware soft-partitioning, and unlicensed Enterprise Edition options and management packs (Oracle Licensing Experts engagement data, 2026).
- Across 600+ engagements, organisations running a continuous SAM programme settle audits for a fraction of the opening claim, while reactive shops face the full 3–5× exposure (Oracle Licensing Experts engagement data, 2026).
Recommendations by role
CIO / IT Director
- Fund a standing SAM function, not a one-off project — Oracle exposure compounds between audits.
- Mandate that no Oracle deployment goes live without a SAM entitlement check first.
- Require an independent effective-licence position reviewed quarterly, separate from Oracle's tooling.
SAM / ITAM Manager
- Stand up continuous discovery across physical, virtual and cloud, reconciled to your ordering documents.
- Maintain a forensic evidence pack — deployment data, partitioning design, contracts — audit-ready at all times.
- Treat Java, VMware and EE options as your three highest-risk measurement targets.
Procurement / Vendor Management
- Use the SAM position to right-size every Oracle renewal and challenge support on shelfware.
- Never accept Oracle's measurement output as the system of record — reconcile against your own.
- Sequence purchases so any compliance gap is closed inside a commercial deal, not an audit settlement.
CFO / Finance
- Treat the SAM programme as risk insurance against a 3–5× audit claim, and budget it accordingly.
- Model the 22% annual support annuity and target right-sizing as a recurring saving, not a one-time cut.
- Require a defensible licence position before approving any Oracle expansion or cloud migration.
What is an Oracle SAM programme and why does it matter?
An Oracle SAM programme is a continuous practice that discovers every Oracle deployment, maps it to your contractual entitlements, and maintains an independent effective-licence position. It matters because Oracle's GLAS audit team runs audits to find revenue, and the only durable buyer-side defence is to already hold a forensic, more-accurate count of your own estate before the notice arrives.
Software asset management is not licence inventory in a spreadsheet. It is an operating discipline: continuous discovery feeding a reconciliation engine that compares what is deployed against what you bought, surfaces the gap, and keeps the evidence audit-ready. The difference between a programme and a project is permanence — Oracle exposure drifts every time a VM is cloned, a management pack is switched on, or a new hire pushes Java headcount up. A reactive shop discovers all of this for the first time under a 45-day audit clock, with Oracle controlling the measurement. A SAM programme discovers it the day it happens, on the buyer's terms.
How do you build continuous Oracle discovery across the estate?
You build continuous discovery by deploying a recognised measurement tool that scans physical servers, every VMware and hypervisor host, and cloud instances on a recurring schedule, then feeds the output into a single reconciliation system. Coverage must follow where Oracle workloads can run, not just where they do — soft-partitioned VMware clusters are licensed by every host a VM could move to.
Discovery is the foundation, and its weakness is scope. Oracle Database deployed in a VMware vSphere cluster is treated as soft partitioning, which means Oracle expects every physical processor in every host the VM could vMotion to be licensed — the virtual machine's vCPU count is irrelevant for licensing. A discovery tool that only sees configured VMs misses the cluster boundary that defines your real exposure. Effective discovery captures the full hardware topology, the partitioning design, and the management-pack and option usage that Oracle's own scripts query (such as the DBA_FEATURE_USAGE_STATISTICS view). Run it continuously, not annually, so the position is always current.
How do you reconcile deployments against Oracle entitlements?
You reconcile by mapping every discovered deployment to a specific entitlement in your ordering documents — by metric (Processor, Named User Plus, Employee), by Core Factor, and by edition and option. The output is your effective licence position: the net surplus or shortfall per product. This is the number you defend in an audit, and it must be yours, built independently of Oracle's tooling.
Reconciliation is where SAM earns its keep. Deployed cores are converted to licence units using the Oracle Core Factor Table; Named User Plus counts are checked against per-processor minimums; Enterprise Edition options like Partitioning, Advanced Compression, Diagnostics Pack and Tuning Pack are matched to whether they were ever purchased. The result is an effective licence position you control. When GLAS arrives, you are not discovering your exposure with them — you are presenting a forensic position you have already verified, and negotiating from evidence rather than fear.
Why is Java SE the SAM blind spot that costs the most in 2026?
Java SE is the most expensive SAM blind spot because the Java SE Universal Subscription is priced per employee, not per install — every full-time, part-time, contractor and temporary worker counts, regardless of how many actually use Java. At a 2026 list ceiling of $15.00 per employee per month, a 10,000-person firm faces roughly $1.8M a year for Java alone if it is caught unmanaged.
The Java SE Universal Subscription is the trap most SAM programmes miss because Java installs quietly, bundled inside dozens of third-party applications. Oracle's 2026 list runs from $15.00 per employee per month in the 1–999 band down to $5.25 in the 40,000-plus band, and some order documents carry a minimum annual floor of $50,000 to $100,000 regardless of headcount. Because the metric is total employees, a single unlicensed Oracle JDK install can justify a subscription covering your entire workforce. A SAM programme must track every Java runtime, distinguish Oracle JDK from OpenJDK builds such as Eclipse Temurin, and right-size by migrating non-essential workloads off Oracle's distribution.
How does a SAM programme contain Oracle-on-VMware exposure?
A SAM programme contains VMware exposure by documenting and enforcing the cluster boundary: dedicated Oracle clusters with restricted vMotion scope, separated storage and networking, and a maintained topology record proving where Oracle VMs can and cannot run. Because Oracle treats VMware as soft partitioning, undocumented clusters expose every host in the estate to licensing.
Oracle's partitioning policy did not change when Broadcom acquired VMware — only the platform economics did. Oracle still classifies VMware as soft partitioning, so its audit position is that any host a VM could migrate to must be fully licensed. The SAM defence is architectural and evidentiary: design isolated Oracle clusters, restrict migration boundaries technically, and keep a written, time-stamped record of the topology and historical VM placement. Held in your SAM tool, that record is what defeats Oracle's "you could have moved it anywhere" claim. Broadcom's repricing has pushed many estates to shrink VMware footprints, which incidentally tightens the Oracle containment story — capture that in your position.
Should you join Oracle's GLAS VSAM programme?
Oracle's Verified Software Asset Management (VSAM) programme is a voluntary GLAS offering that gives a one-year audit reprieve in exchange for using Oracle-recognised tooling and data sharing. It can reduce audit frequency, but it routes your measurement data to Oracle's advisory arm. Treat it as a supplement to an independent SAM programme, never a replacement — keep your own forensic position regardless.
The GLAS VSAM programme offers a tempting carrot: opt in, use a verified tool, and Oracle grants a defined audit reprieve. The catch is that the data and the framing flow through Oracle's own licensing-advisory team, whose commercial interest is unchanged. Joining can be sensible for organisations that want fewer formal audits, but only if you maintain a parallel, independent effective-licence position that you control. The moment your only count is the one Oracle helped produce, you have surrendered the evidentiary advantage that makes a SAM programme worth running. Independence is the asset — protect it.
How do you turn the SAM position into right-sized Oracle spend?
You convert SAM data into savings by attacking the 22%-of-net-licence-value support annuity: identify shelfware and over-deployed editions, downgrade Enterprise Edition where Standard Edition 2 suffices, retire unused options and packs, and time terminations to a commercial deal so repricing rules do not erase your discount. SAM tells you precisely where the waste is.
Right-sizing is the financial payoff of a SAM programme. The effective-licence position surfaces surplus licences carrying support you no longer need, options enabled but never deployed, and Enterprise Edition databases running workloads that Standard Edition 2 would cover. Each one is a recurring cost, because Oracle bills support at 22% of net licence value every year. The discipline is to act on the data inside a negotiation: Oracle's matching-service-levels and pricing-following-reduction rules can reprice retained support to list if you terminate carelessly, so sequence reductions into a broader deal where you hold the upper hand. SAM makes the savings visible; negotiation captures them.
Decision matrix: where to focus your SAM effort first
Prioritise SAM coverage by two variables — how much exposure the product area carries, and how fast that exposure drifts between audits. The matrix shows where to point your scarce measurement effort first.
High exposure · fast drift
Java SE per-employee and VMware soft-partitioning. Headcount and VM topology change weekly — measure continuously and document boundaries.
High exposure · slow drift
Enterprise Edition options and management packs. Rarely change once set, but a single enabled pack creates large, durable exposure — audit feature usage regularly.
Lower exposure · fast drift
Named User Plus counts on smaller systems. Worth tracking against per-processor minimums, but not where the biggest claims originate.
Lower exposure · slow drift
Standard Edition 2 estates and clearly-entitled core products. Reconcile annually; spend your effort on the high-exposure quadrants.
The SAM programme building blocks
The table summarises each building block of an Oracle SAM programme, what it produces, and the exposure it controls.
| Building block | What it produces | Exposure it controls |
|---|---|---|
| Continuous discovery | Current deployment data across physical, virtual, cloud | Surprise deployments, VMware cluster scope |
| Entitlement baseline | Mapped record of every ordering document and metric | Mis-applied metrics, lapsed or mis-counted licences |
| Reconciliation engine | Independent effective-licence position per product | Back-licence claims, Core Factor errors |
| Java runtime tracking | Inventory of Oracle JDK vs OpenJDK by host | Per-employee Java SE Universal Subscription exposure |
| Topology evidence pack | Documented cluster boundaries and placement history | VMware soft-partitioning over-claims |
| Right-sizing cadence | Shelfware and edition-downgrade candidates | 22% support paid on unused entitlements |
Strengths & cautions of each SAM lever
| Lever | Strength | Caution |
|---|---|---|
| Recognised discovery tooling | Produces audit-grade data Oracle cannot easily reject. | Only ~10 tools qualify — verify recognition before you buy. |
| Independent licence position | Lets you negotiate from evidence, not fear. | Must be maintained continuously or it goes stale fast. |
| Java runtime governance | Stops a single JDK install triggering a workforce-wide bill. | Requires real OpenJDK migration capability to hold price. |
| VMware topology evidence | Defeats Oracle's "could move anywhere" soft-partitioning claim. | Worthless unless the cluster boundary is enforced technically. |
Acronyms & key terms
- SAM
- is Software Asset Management, the discipline of continuously reconciling deployed software against entitlements to hold a defensible licence position.
- ITAM
- is IT Asset Management, the broader practice covering hardware and software assets of which Oracle SAM is a specialist part.
- GLAS
- is Oracle Global Licensing and Advisory Services, the audit and licensing-advisory arm formerly branded License Management Services (LMS).
- VSAM
- is Oracle's Verified Software Asset Management programme, a voluntary scheme granting an audit reprieve in exchange for verified tooling and data sharing.
- Effective Licence Position
- is the net surplus or shortfall per Oracle product after reconciling deployments against entitlements.
- Core Factor
- is the multiplier in the Oracle Core Factor Table converting physical cores into the number of Processor licences required.
- Soft Partitioning
- is Oracle's classification of VMware and similar virtualisation, under which every host a VM could run on must be licensed.
- Named User Plus
- is the per-user Oracle metric, subject to per-processor minimum counts regardless of actual user numbers.
- Java SE Universal Subscription
- is Oracle's per-employee Java licence, billing every employee in the organisation rather than each Java install.
- Management Pack
- is a chargeable Enterprise Edition add-on such as Diagnostics or Tuning Pack, frequently enabled and used without a licence.
- Shelfware
- is licensed and supported Oracle software that is never deployed, carrying 22% annual support for no benefit.
- DBA_FEATURE_USAGE_STATISTICS
- is the Oracle database view Oracle's audit scripts query to detect option and pack usage.
Frequently asked questions
What is an Oracle SAM programme?
An Oracle SAM programme is a continuous software asset management practice that discovers every Oracle deployment across physical, virtual and cloud environments, reconciles it against your contractual entitlements, and maintains an independent effective-licence position. Its purpose is to ensure you always know your true Oracle compliance position before Oracle does — so a GLAS audit becomes a verification of evidence you already hold, not a discovery exercise Oracle controls. It also right-sizes spend by exposing shelfware and over-deployment.
How is a SAM programme different from running an Oracle audit tool once?
A one-off tool run is a snapshot; a SAM programme is permanent. Oracle exposure drifts constantly — VMs are cloned, management packs are enabled, employee headcount changes Java liability, and clusters are reconfigured. A single annual scan misses all of this and leaves you discovering your real position under a 45-day audit clock. A continuous programme captures changes as they happen, keeps the evidence audit-ready year-round, and turns the licence position into a tool for negotiating renewals rather than a fire drill.
Which tools does Oracle GLAS recognise for SAM?
Oracle GLAS recognises only a small set — roughly ten globally — of measurement tools as producing audit-grade data. Using an unrecognised discovery tool risks Oracle rejecting your numbers and rerunning its own scripts during an audit, exactly when you have least room to push back. Before investing, confirm a tool's current recognition status, and ensure it captures full hardware topology and option-usage data (including the DBA_FEATURE_USAGE_STATISTICS view), not just a list of configured virtual machines.
Why is Java the biggest SAM risk in 2026?
Because the Java SE Universal Subscription is priced per employee, not per install. Oracle's 2026 list runs from $15.00 per employee per month in the 1–999 band down to $5.25 in the largest bands, and counts every full-time, part-time, contractor and temporary worker — so one unlicensed Oracle JDK install can justify a subscription covering your entire workforce. A 10,000-person firm faces roughly $1.8M a year at the list ceiling. A SAM programme must track every Java runtime and distinguish Oracle JDK from OpenJDK builds.
Does a SAM programme actually save money or just reduce risk?
Both. The risk reduction is large — it is the difference between settling an audit for a fraction of the opening claim and paying a 3–5× back-licence demand. But SAM also saves recurring money by surfacing shelfware, unused options, and Enterprise Edition databases that Standard Edition 2 could run, all of which carry support at 22% of net licence value every year. Right-sized inside a negotiation, those reductions typically protect a meaningful share of the annual Oracle support bill.
Should we join Oracle's VSAM programme?
Oracle's Verified Software Asset Management (VSAM) programme offers a one-year audit reprieve in exchange for verified tooling and data sharing, and can reduce formal audit frequency. The caution is that it routes your measurement data through Oracle's own advisory arm, whose commercial interest is unchanged. It can complement an independent SAM programme, but it must never replace one — always keep a parallel effective-licence position you control, so you are never negotiating against a count only Oracle can produce.
Who should own the Oracle SAM programme internally?
Ownership usually sits with a SAM or ITAM manager, but it needs executive sponsorship from the CIO and a working relationship with procurement and finance. The SAM function maintains discovery and the licence position; procurement uses that position to right-size renewals and challenge support; finance treats the programme as insurance against a multi-million-dollar audit claim. The failure mode is leaving Oracle licensing as a part-time responsibility — exposure compounds in the gaps, and Oracle audits the gaps.
Methodology & sources
Benchmarks in this playbook draw on Oracle Licensing Experts engagement data across 600+ Oracle licensing, audit-defence and SAM engagements in 2024–2025. Java pricing reflects Oracle's published 2026 Java SE Universal Subscription tiers; support mechanics reflect the Oracle Technical Support Policies and the Oracle Master Agreement; virtualisation treatment reflects Oracle's partitioning policy. Figures are representative benchmark scenarios for guidance, not a quote. Primary and authoritative sources:
About the author
This playbook was prepared by the Oracle Licensing Experts Advisory Team — former Oracle insiders who now work exclusively buyer-side. The team has advised on $1.8B of Oracle spend across 600+ engagements, with an independent, evidence-based, forensic approach to Oracle audits, software asset management, license optimization and contract negotiation. Learn more about the team. Not affiliated with Oracle Corporation.
Download this SAM programme playbook as a PDF
Get the full Oracle SAM Programme Playbook to put in front of your IT, procurement and finance teams — and to brief whoever owns your next Oracle audit response.
Request the PDF & a free Oracle compliance review →Related white papers
Standing up an Oracle SAM programme?
We build the independent licence position Oracle cannot challenge — continuous discovery, forensic reconciliation, Java and VMware containment — and right-size your spend before the next renewal. One Fortune 500 manufacturer cut a $4.2M Oracle EE estate to $1.6M after we rebuilt its SAM position — see how in our enterprise audit-defence case study.
The buyer-side Oracle briefing
Forensic Oracle licensing intelligence — SAM tactics, audit defence, Java exposure and support repricing. No Oracle spin.