Get Oracle Licensing Intelligence
Join enterprise IT leaders receiving our monthly advisory on Oracle audit tactics, licensing changes, and compliance risk management.
By Fredrik Filipsson · Category: Oracle Licence Management · Audience: SAM Manager / IT Director / Procurement / CIO / ITAM · Updated 2026
01 The Three Pillars of Oracle Licence Verification
Establishing an accurate Oracle licence position requires three parallel workstreams: entitlement verification (what you own), usage discovery (what you run), and gap analysis (where the two diverge). Most organisations attempt only one or two of these. A complete licence baseline requires all three pillars, executed systematically and reconciled against each other.
| Verification Pillar | What It Answers | Primary Sources | Common Gap |
|---|---|---|---|
| 1. Entitlement verification | What Oracle licences do we legally own? Which products, metrics, quantities, and editions? | Ordering documents, Master Agreements, support renewal notices, Oracle CSI records | Licences purchased through acquisitions, regional offices, or historical deals not captured in central inventory |
| 2. Usage discovery | What Oracle software is actually installed and running? Which features are enabled? On what hardware? | Database queries, server inventories, DBA_FEATURE_USAGE_STATISTICS, LMS scripts, CMDB | Oracle software installed on servers that SAM/ITAM teams do not know about (shadow IT, dev environments, test instances) |
| 3. Gap analysis | Where does usage exceed entitlements (compliance risk)? Where do entitlements exceed usage (cost waste)? | Comparison of entitlement inventory against usage inventory | Analysis performed on incomplete data from either pillar, producing false confidence |
02 Pillar 1: Gathering Entitlement Documentation
Entitlement documentation is the legal proof of what Oracle licences you own. Without complete, accurate entitlement records, you cannot defend your position in an audit, you cannot identify shelfware for cost reduction, and you cannot negotiate effectively.
| Document Type | What It Contains | Where to Find It | Common Problem |
|---|---|---|---|
| Oracle ordering documents | Product names, licence metrics (Processor/NUP), quantities, list price, discount, net price, support fees | Procurement archives, legal/contracts department, Oracle account team | Ordering documents from 10 to 20 years ago are missing or stored in retired filing systems |
| Master Agreement / OLSA | Overarching terms: territory, audit rights, definitions of metrics, permitted use, transfer rights | Legal department, contract management system | Multiple Master Agreements across subsidiaries with different terms; no central view |
| Support renewal notices | Annual renewal documents listing products under support, quantities, and annual support fees | Finance/AP department, Oracle account team | Renewal notices may not match ordering documents (Oracle's records vs your purchases) |
| ULA / ELA agreements | Unlimited or enterprise licence terms, product scope, duration, certification requirements | Legal/procurement; often managed by a single executive | ULA product scope misunderstood: organisations assume broader coverage than the agreement provides |
| Acquisition-related licences | Oracle licences purchased by acquired companies before the acquisition | M&A integration records, acquired company's procurement archives | Acquired company's Oracle licences never consolidated into the parent's inventory. Most common gap source. |
| Partner / reseller purchases | Oracle licences purchased through authorised resellers or distributors | Reseller records, procurement system purchase orders | Reseller purchases may not appear in Oracle's CSI records if CSI was not properly linked |
03 Pillar 1b: Using My Oracle Support (CSI) for Verification
My Oracle Support (MOS) is Oracle's customer portal where you can view products currently under active support, submit service requests, and access patches. Your organisation's Customer Support Identifiers (CSIs) are the keys to this information. While MOS is not a complete entitlement record, it is a valuable cross-reference tool.
| MOS Feature | What It Shows | How to Access | Limitation |
|---|---|---|---|
| Support Identifiers (CSI) | Products under active support, licensed quantities, support end dates, support level | Login → Settings → Support Identifiers → Select CSI | Only shows licences with active support. Perpetual licences without support are invisible. |
| Product listing | Oracle product names and editions covered under each CSI | CSI details page → Products tab | Product names may not match ordering document terminology exactly (renamed products, bundled suites) |
| Licence quantities | Number of licences per product under the CSI | CSI details page → Quantities column | Quantities may not reflect your actual entitlement if Oracle's records are incomplete |
| Support renewal history | Historical renewal dates and amounts | CSI details page → Renewal tab | Does not show original licence purchase price or discount terms |
| Multi-CSI environments | Organisations with multiple CSIs have fragmented views | Each CSI must be checked individually | No single consolidated view across all CSIs. Must manually aggregate to see full picture. |
04 Pillar 1c: Engaging Oracle for Verification
| Engagement Method | What You Receive | Risk Level | Recommended Approach |
|---|---|---|---|
| Request entitlement summary from account manager | Official list of all licences Oracle has on record for your organisation | Low: routine administrative request | Request in writing; specify all legal entities and subsidiaries; cross-check against your internal records |
| Request ordering document copies | Oracle can retrieve copies of historical ordering documents from their archives | Low: document retrieval is standard | Useful when internal records are incomplete; verify that Oracle's copies match your records |
| Engage Oracle LMS for "compliance review" | Full audit-style assessment of your Oracle deployment | High: this is effectively an Oracle audit | Do NOT engage Oracle LMS for compliance verification. Conduct internal assessments first. |
| Request CSI consolidation | Oracle can consolidate multiple CSIs into a unified structure | Medium: may trigger review of licence attribution | Consolidate CSIs when you have a clear picture of all entitlements |
Vendor Shield: Oracle Licence Management
Redress Compliance builds complete entitlement baselines for Fortune 500 organisations. We identify $1M to $10M+ in unrecognised entitlements and shelfware, and establish ongoing governance that maintains audit readiness.
05 Pillar 2: Usage Discovery
Knowing what you own is only half the equation. You must also know exactly what Oracle software is installed, running, and being used across your entire estate.
| Discovery Method | What It Reveals | Scope | Key Consideration |
|---|---|---|---|
| DBA_FEATURE_USAGE_STATISTICS | Which Oracle Database features and options have been used (Partitioning, TDE, Diagnostics Pack, ADG, etc.) | Per database instance | Records feature usage permanently. Even one-time accidental activation creates an audit trail. |
| V$LICENSE and V$INSTANCE | Database edition (EE/SE2), current sessions, CPU count, database name | Per database instance | Confirms which edition is installed and basic capacity metrics |
| Server hardware inventory (CMDB) | Physical servers, socket counts, core counts, processor types (for core factor calculation) | All servers running Oracle | Must include virtualisation hosts, not just VMs. Oracle licences physical infrastructure. |
| Virtualisation platform inventory | VMware clusters, host assignments, affinity rules, VM mobility settings | All virtualisation environments with Oracle | Oracle counts all hosts in a cluster unless isolation is documented. VMware cluster mapping is essential. |
| Cloud instance inventory | AWS/Azure/GCP/OCI instances running Oracle, vCPU counts, instance types | All cloud accounts and subscriptions | Cloud instances may be provisioned by developers without ITAM awareness; audit all cloud accounts |
| Java installation discovery | Oracle Java SE installations across servers, desktops, containers | Enterprise-wide | Java SE licensing changed to subscription model in 2023 (employee-based); all installations must be assessed |
| Middleware and application inventory | WebLogic, SOA Suite, Oracle Forms, OAS, EBS, PeopleSoft, JDE, Siebel installations | All application and middleware servers | Middleware installations often overlooked; restricted-use provisions must be verified |
06 Pillar 3: Gap Analysis
| Gap Type | What It Means | Typical Cause | Required Action |
|---|---|---|---|
| Under-licensing (compliance risk) | Usage exceeds entitlements. You are running more Oracle software than you have licences for. | Unlicensed database options, VMware cluster-wide counting, NUP under-counts, shadow installations | Remediate before Oracle discovers: reduce usage, acquire additional licences, or restructure deployment |
| Over-licensing (cost waste) | Entitlements exceed usage. You own licences that are not deployed or needed. | Historical purchases never decommissioned, acquired company licences sitting unused, EE licences where SE2 would suffice | Terminate support on unused licences to eliminate annual support cost; redeploy to cover gaps elsewhere |
| Metric mismatch | Licence metric (NUP vs Processor) does not match deployment reality | NUP-licensed database exposed to large user population; processor-licensed database running on different hardware | Evaluate whether switching metrics would be more cost-effective; negotiate conversion with Oracle if needed |
| Edition mismatch | Software edition installed does not match licence edition (e.g., EE features used on SE2 licence) | DBA installed EE binary on SE2-licensed server; EE features enabled without awareness | Disable EE features immediately; document corrective action; assess whether EE licence is required |
07 Common Licence Verification Pitfalls
| Pitfall | How It Occurs | Cost Impact | Prevention Strategy |
|---|---|---|---|
| Relying solely on MOS/CSI | ITAM team uses My Oracle Support as the only entitlement record; misses perpetual licences without support, acquired company licences, and reseller purchases | $200K to $2M+ in unrecognised entitlements | Maintain internal master inventory based on ordering documents; use MOS as cross-reference only |
| Paying support on shelfware | Annual support continues on licences that are no longer deployed or needed | $100K to $1M+/year in wasted support fees (22% of licence value annually) | Annual shelfware review: compare deployed products against support renewal list |
| Misinterpreting licence metrics | Processor licences counted by socket instead of cores x core factor; NUP minimums not calculated correctly | $200K to $1M+ in under-licensing or over-purchasing | Always use Oracle's Core Factor Table; calculate NUP minimums based on processor count |
| Ignoring virtualisation impact | Oracle deployed on VMware cluster without assessing cluster-wide licensing implications | $500K to $5M+ (entire cluster licensed instead of single host) | Map all Oracle instances to their physical infrastructure; document isolation |
| Incomplete acquisition integration | Acquired company's Oracle licences never consolidated; duplicate support payments or unrecognised entitlements | $200K to $2M+ in untracked entitlements or duplicate costs | Include Oracle licence inventory in every M&A due diligence and integration checklist |
| Allowing Oracle LMS to "help" | Oracle LMS conducts a "compliance review" that reveals gaps; findings used to pressure commercial outcomes | $500K to $10M+ in audit findings used as leverage | Never allow Oracle LMS to run scripts on your infrastructure; use independent advisors |
08 Building a Licence Baseline: Step-by-Step
Consolidate Entitlement Documentation
Gather all ordering documents, Master Agreements, support renewals, ULA/ELA agreements, acquisition records, and reseller purchases into a central repository. Output: Master Entitlement Inventory (product, metric, quantity, date, entity). Timeline: 2 to 4 weeks.
Cross-Reference with MOS/CSI
Log into every CSI across all entities. Extract product lists and quantities. Compare against internal master inventory. Flag discrepancies. Output: CSI Reconciliation Report. Timeline: 1 to 2 weeks.
Discover All Oracle Installations
Scan all servers, VMs, cloud instances for Oracle Database, Middleware, Applications, and Java installations. Record editions, versions, and features. Output: Complete Oracle Installation Inventory. Timeline: 2 to 4 weeks.
Map Hardware and Virtualisation
For every Oracle installation, document the physical server (sockets, cores, processor type), virtualisation platform (VMware cluster hosts, affinity rules), and cloud instance (vCPUs). Output: Infrastructure-to-Licence Mapping. Timeline: 1 to 2 weeks.
Run Feature Usage Analysis
Query DBA_FEATURE_USAGE_STATISTICS on every Oracle database. Identify enabled options and packs. Check for EE features on SE2 instances. Output: Feature Usage Report (with compliance flags). Timeline: 1 week.
Perform Gap Analysis
Compare entitlement inventory against usage inventory. Identify under-licensing (compliance gaps), over-licensing (shelfware), metric mismatches, and edition mismatches. Output: Gap Analysis Report with remediation priorities and cost impact. Timeline: 1 to 2 weeks.
Remediate and Document
Address compliance gaps (reduce usage, acquire licences, restructure). Eliminate shelfware (terminate support). Document all changes. Output: Remediated Licence Position with supporting documentation. Timeline: 2 to 8 weeks (depending on gap severity).
09 Ongoing Governance Checklist
Annual Entitlement Reconciliation
Before each Oracle support renewal, reconcile the renewal notice against your master entitlement inventory. Verify that all products, quantities, and metrics match. Flag discrepancies with Oracle. Identify shelfware candidates for support termination.
Quarterly Usage Discovery Scan
Run DBA_FEATURE_USAGE_STATISTICS on all Oracle databases. Scan infrastructure for new Oracle installations. Check cloud accounts for Oracle instances provisioned since last scan. Update the Oracle Installation Inventory.
Infrastructure Change Control
Require ITAM sign-off before any hardware change, server migration, virtualisation reconfiguration, or cloud instance resize that affects Oracle-licensed servers. Recalculate licence requirements after every change.
M&A Licence Integration
Include Oracle licence inventory in every acquisition due diligence checklist. Within 90 days of closing, consolidate acquired company's Oracle entitlements into the master inventory. Assess whether acquired licences can cover existing gaps.
CSI and Contract Management
Maintain a register of all Oracle CSIs across all entities. Verify annually that CSI records match internal entitlement inventory. Consolidate CSIs where practical to simplify governance.
Audit Readiness Documentation
Maintain a current "audit file" containing: master entitlement inventory, ordering documents, CSI reconciliation report, Oracle installation inventory, feature usage reports, infrastructure mapping, and gap analysis. This file should be ready to present within 48 hours of an Oracle audit notification.
Frequently Asked Questions
Start with two parallel actions: (1) Log into My Oracle Support and review all your CSI records, which shows products currently under active support with quantities and metrics. (2) Locate your most recent Oracle support renewal notice, which lists all products you are paying support on and their annual cost. Together, these give you a quick snapshot. However, this is not a complete picture. MOS only shows licences with active support, and may not include historical purchases, acquired company licences, or perpetual licences where support was terminated.
Contact your Oracle account manager and request copies of all ordering documents associated with your organisation's legal entities. Oracle maintains archives of historical purchases and can retrieve copies. Additionally, check internal procurement systems, legal department archives, finance department records (for payment history), and acquired company records. For very old purchases (10+ years), Oracle's archives may be incomplete. In these cases, support renewal notices that list the products and quantities serve as secondary evidence of entitlement.
Requesting an entitlement summary from your Oracle account manager is a routine administrative request and does not trigger an audit. However, engaging Oracle LMS (License Management Services) or GLAS (Global Licence Advisory Services) for a "compliance review" is functionally equivalent to an audit. Any findings will be shared with Oracle's sales organisation and used commercially. Always distinguish between asking your account manager for documentation (safe) and inviting Oracle LMS to assess your environment (risky). Conduct internal compliance assessments before any engagement with Oracle's licensing teams.
Oracle provides built-in discovery capabilities at no additional cost. Run DBA_FEATURE_USAGE_STATISTICS on every Oracle database to identify which features and options are in use. Query V$LICENSE and V$INSTANCE for edition and capacity information. Use your CMDB or server inventory tools to map Oracle installations to physical hardware. For virtualisation, extract VMware cluster host lists and affinity rules from vCenter. For cloud, use AWS/Azure/GCP billing and inventory APIs to identify Oracle instances. Combine these data sources into a spreadsheet-based licence position. No commercial SAM tool required for a baseline assessment.
At minimum annually (before support renewal) and immediately after any major event: acquisitions, divestitures, new Oracle deployments, infrastructure migrations, cloud migrations, virtualisation changes, or workforce changes affecting NUP counts. Organisations with large Oracle estates (100+ databases or $5M+ annual support) should conduct quarterly usage scans to catch drift early. The cost of proactive compliance monitoring is a fraction of the cost of an Oracle audit finding.
My Oracle Support shows only licences with active Oracle support. It does not show: perpetual licences where support has been terminated (you still own these licences), licences purchased through resellers that were not properly linked to your CSI, licences from acquired companies that have not been consolidated, or licences under separate CSIs that your MOS account cannot access. Your ordering documents are the definitive legal proof of entitlement. MOS is a useful cross-reference tool but should never be treated as the complete entitlement picture.
📚 Oracle Licence Management Series
Oracle Licensing Knowledge Hub (Pillar) → Oracle LMS Collection Tool & Scripts → Oracle Licence Metrics & Definitions → Oracle Support Policies & Maintenance → Oracle Licensing on AWS → Oracle Licensing on Nutanix → Oracle Database SE2 Licensing →Oracle Licence Management
Service
Oracle Audit Defence
Service
Oracle Contract Negotiation
Service
Third-Party Support Advisory
Service
Licensing Assessment Case Studies
Case Studies
Active Data Guard Licensing
Advisory
Java SE Subscription Pricing
Advisory
Oracle Knowledge Hub
Knowledge Hub
Build Your Complete Oracle Licence Baseline
Contact us for a confidential introductory call to discuss your software landscape, upcoming renewals, and how Redress can deliver measurable savings. Fixed-fee proposal typically provided within 48 hours.