Oracle License Review: What It Covers, When to Run One and What It Finds

An Oracle licence review answers one question before Oracle asks it: are we licensed for what we run? Done well, it also answers a second one that matters as much: are we paying for what we do not need? Most Oracle estates have both problems at once, a compliance gap in one place and unused licences in another, and a review is the only way to see both before they cost money.

This article explains what an Oracle licence review covers, when to run one, what it usually finds, and why it should be independent of Oracle.

In short

• What it is: A comparison of your Oracle entitlements (every contract and order) with your deployments (every installation, option and pack in use), counted by Oracle’s rules, including virtualisation and cloud.
• When to run one: A year before a ULA ends or a major renewal, before a hardware refresh or cloud migration, after a merger, and as soon as Oracle asks for deployment data.
• What it finds: Unlicensed options and packs, VMware clusters counted in full, uncounted standby servers, Java installations, and licences you own but do not use.
• Who should do it: Someone independent of Oracle. Oracle’s own “licence reviews” are run by its audit team and feed its sales team.

What an Oracle licence review covers

A complete review has three parts.

• Entitlements. Every Oracle Master Agreement, licence agreement, ordering document and amendment, including those of acquired companies, with the products, metrics, quantities, restrictions and support status of each. Oracle’s own records are often incomplete, especially for licences bought through resellers or inherited in a merger.
• Deployments. Every server, virtual machine and cloud instance where Oracle software is installed or running: database editions, options and management packs in use, middleware, applications and Java, with the processors and users behind each.
• The rules. Oracle’s processor definition and core factor table, the minimums for Named User Plus, its policies on partitioning, disaster recovery and the cloud, and the terms of your own contracts, which take precedence over policy.

The result is an effective licence position for each product: licensed, under-licensed or over-licensed, with the reason and the figure.

When to run an Oracle licence review

• A year before a ULA ends, so you can decide between certifying and renewing on your own numbers.
• Before a major renewal or purchase, so you negotiate from your position rather than Oracle’s.
• Before a hardware refresh, virtualisation change or cloud migration. More cores per socket, a new VMware cluster or a move to AWS can change the count overnight.
• After a merger or acquisition, when two estates and two sets of contracts meet.
• As soon as Oracle asks for deployment data, whatever the request is called. That is the start of an audit.

What a review usually finds

• Options and packs in use without a licence, often the Diagnostics and Tuning Packs, which are enabled by default in Enterprise Edition.
• VMware clusters that Oracle’s partitioning policy would count in full, even where Oracle runs on a few hosts.
• Standby and test servers with the database installed and running, which need licences like production.
• Cloud instances counted the on-premises way, when AWS, Azure and Google Cloud need twice the licences for the same cores.
• Oracle Java installations, now priced per employee for the whole organisation.
• Licences you own and do not use, still paying 22% of their net price in support every year.

Why it should be independent

Oracle offers its own licence reviews, often presented as help. They are run by Global Licensing and Advisory Services, the same team that runs audits, and their findings go to Oracle’s sales team. An independent review keeps the findings yours: you decide what to fix, what to remove and what, if anything, to buy, before anyone at Oracle sees the data.

Our reviews are run by people who spent years on Oracle’s side of the table, and we take no fees, commissions or partnerships from Oracle or any other vendor. Our SAVE Review Program covers Oracle alongside your other major publishers, and our article on the baseline Oracle licence review describes the first engagement in detail. If you want to count yourself first, our guide to running an Oracle licence self-audit sets out the steps.

Questions we are asked about Oracle licence reviews

What is an Oracle licence review?

A comparison of the Oracle licences you are entitled to with the Oracle software you have deployed and use, counted by Oracle’s rules and your contracts. It shows where you are under-licensed and where you hold licences you do not need.

How long does an Oracle licence review take?

From a few weeks for a small estate to two or three months for a large or multinational one. Most of the time goes into gathering contracts and deployment data.

Is an Oracle licence review the same as an Oracle audit?

No. An audit is run by Oracle under your contract’s audit clause and ends with a purchase proposal. An independent review is run for you, and its findings stay with you.

Should I accept Oracle’s offer of a free licence review?

Treat it as the start of an audit. It is run by Oracle’s audit team, and the data you share will be used to assess compliance. Run your own review first.

If a renewal, a ULA end date or an Oracle request is coming up, book an hour with our Advisor on Call or talk to us about a review.