Oracle Licensing Position — Sample Report
What a licensing position review should produce — entitlements against measured usage, the gap quantified, the features found in use that nobody authorised, and the actions ranked by exposure.
Markdown. No sign-up, no email.
This is an illustrative example. The organisation, figures and findings are composed to show what a licensing review should produce, not drawn from a named engagement. It is not legal or contractual advice — Oracle agreements vary, and the detail decides the outcome.
Prepared for: Head of Infrastructure Scope: All production and non-production Oracle databases Method: Feature usage extracted from each database; entitlements from contract records Date: _______
Summary#
Nine databases reviewed. Three findings create exposure, one of which has been accruing for an estimated two years. Estimated worst-case exposure: £180,000–£240,000, before any negotiation.
None of this arose from deliberate misuse. All three findings are features that were switched on by people doing their jobs, in tools that enable them by default.
| # | Finding | Severity | Est. exposure |
|---|---|---|---|
| 1 | Diagnostics and Tuning Pack in use on 4 unlicensed databases | High | £120k–£160k |
| 2 | Partitioning in use on 1 Standard Edition database | High | £45k–£60k |
| 3 | Non-production databases not covered by entitlement | Medium | £15k–£20k |
| 4 | Two databases past end of support | Medium | — (risk, not licensing) |
Finding 1 — management packs in use without entitlement#
What was found: Feature usage shows Diagnostics Pack and Tuning Pack access on four databases. Entitlements cover one.
How it happened: The monitoring platform installed in the previous year collects performance data using views that fall under these packs. Nobody chose to license a pack; the tool did what it was configured to do, and the usage counter incremented.
Since when: Earliest recorded access is roughly two years old, which is the accrual period a vendor audit would likely assess.
🔴 This is the single most common Oracle finding in practice, and it is almost always innocent. The cost arrives back-dated regardless of intent.
Actions:
- Disable the collection on the three unlicensed databases, and confirm usage stops
- Establish whether the historical accrual can be addressed commercially — take specialist advice before any contact with the vendor
- Add feature-usage extraction to the monthly operational review
Finding 2 — an Enterprise feature on a Standard Edition database#
What was found: Partitioning is in use on a database licensed as Standard Edition.
How it happened: A performance problem in a large table was solved by a DBA applying a standard technique. The edition constraint was not visible at the point of the decision.
Actions:
- Assess whether the partitioning can be removed and the performance requirement met another way
- If not, price the edition upgrade against the exposure
- Add an edition check to the change process for schema work
Finding 3 — non-production coverage#
What was found: Three development and test databases with no clear entitlement. Frequently assumed to be free; generally they are not.
Actions: Confirm the contractual position, and consolidate the three onto fewer instances where the workload allows.
Finding 4 — support status#
Two databases run a version past its support end date. This is not a licensing exposure but it is a security and operational one: no patches, limited vendor assistance, and an upgrade that grows harder each release.
Action: Schedule the upgrade as a project now rather than as an emergency later.
What was checked, and what was not#
Checked: feature usage per database, edition, version and support status, entitlement records, non-production inventory.
Not checked, and recommended next: how cores are counted in the virtualisation platform. This is frequently the largest single exposure in an Oracle estate, it depends on contract terms rather than on technical configuration, and it needs specialist review before any audit.
Recommended sequence#
- Stop the ongoing accrual — finding 1, this week
- Take specialist licensing advice on historical exposure before contacting the vendor
- Resolve finding 2 technically if possible
- Confirm non-production position
- Commission a virtualisation review
- Make feature-usage extraction a monthly routine
Why this report exists in this shape#
A licensing report that says "you may be exposed" changes nothing. This one names what is in use, on which databases, since when, and what to do first — because exposure that is quantified and sequenced can be managed, and exposure that is described in general terms simply waits for an audit.
See Oracle and the health and licensing checklist.