Oracle License Audit or Renewal? Your Options, From Negotiating to a Full Exit

The short answer

When an Oracle audit notice or a support renewal arrives, you have four options, and they combine: comply and negotiate with Oracle, move some or all databases to third-party Oracle support, migrate part of the estate to shrink what you license, or plan a full exit to another database. Whatever you choose, the first weeks look the same: read the audit and support terms in your own agreement, build your own record of what you are entitled to and what is deployed before Oracle's numbers arrive, agree the scope and the data-collection method in writing, and involve your legal and procurement teams early.

This article is general information, not legal advice. Your contract and your counsel decide what applies to you.

What Oracle says License Management Services does

Oracle describes License Management Services (LMS) as the sole Oracle licensing authority that can verify your licensing requirements for Oracle programs, and lists two services: an Assurance Service, for confirming requirements in advance or after a merger, acquisition or divestiture, and an Audit Service. Its page sets out a four-phase approach:

1. Agree objectives, timelines and engagement milestones.
2. Gather, validate and analyse usage data across hardware and software configurations, "via multiple agreed-upon methods of data collection".
3. Deliver a report comparing actual usage with contractual entitlements, with a list of actions for resolution if needed.
4. If a compliance issue is found, work with you on an approach to reconcile it.

The phrase to hold on to is "agreed-upon". Scope, method and timeline are set at the start, and that is when you have the most room to shape them.

What to do in the first weeks

1. Read the clauses that apply. Find the audit clause and the support terms in your own agreements and ordering documents. They set notice periods, cooperation duties and how fees are calculated, and they differ between contracts.
2. Name one point of contact. Route every request and every piece of data through one person, so nothing reaches Oracle that has not been reviewed.
3. Assemble entitlements. Collect ordering documents, licence certificates and support renewals, and reconcile them into one list of what you bought, for which metric and which edition.
4. Build your own deployment inventory. Record every installation: version, edition, host, virtualisation layer, and which database options and management packs are installed or in use. Oracle sells Enterprise Edition options and management packs separately from the database, so check which features are used, not only what is installed.
5. Agree the scope in writing. Which legal entities, products, environments and dates are in scope, which data-collection method will be used, and when the report is due.
6. Review the findings line by line. Check each one against your inventory and entitlements before agreeing to anything, and get advice on any you dispute.

The four options

Comply and negotiate

Settling with Oracle is the right answer when Oracle Database is staying for the long term. Negotiate from your own inventory, not from the audit report, and keep the renewal date in view, because that is when you have the most choices. Know Oracle's support stages for the versions you run. Oracle's Lifetime Support Policy gives Premier Support for five years from general availability, Extended Support after that for an additional fee, and Sustaining Support for as long as you use the software, with access to pre-existing fixes.

Third-party Oracle support

Independent firms support Oracle Database in place of Oracle. Rimini Street sells third-party support for Oracle Database with 24/7/365 coverage and what it calls a rolling 15-year support commitment. Spinnaker Support offers 24/7 Oracle third-party support and says it supports existing Oracle products for as long as they are part of your business process. Both suit stable systems on a version you intend to keep. Third-party support changes who fixes problems, not what you are licensed to run, so an open compliance finding still has to be settled with Oracle. Check the effect on any licences that stay on Oracle support before splitting an estate between providers.

Partial migration

Many Oracle estates mix a few complex systems with many simple ones: reporting databases, internal tools and applications with little PL/SQL. Moving the simple ones to PostgreSQL reduces what you license and support, and builds the team's migration skills before the hard systems. ora2pg's assessment ranks schemas by effort, and its ora2pg_scanner runs that assessment across many instances at once. Our Oracle migration cost factors post explains how to read the results. Before counting on savings, check what your support terms say about dropping some licences from a support contract, because the terms decide how the remaining licences are priced.

Full exit

A full exit removes the audit exposure for good and takes the longest. It suits custom applications whose owners can change code, and it needs a sponsor because it competes with feature work for the same engineers. The Oracle to PostgreSQL migration guide lays out the steps, and Oracle database alternatives compares the targets. A partial migration can also become a full exit, one system at a time.

Comparing the ongoing cost

Whatever Oracle quotes, compare it with what the alternative costs to run, not just what it costs to migrate. The database support cost calculator takes your own inputs and shows the comparison with your numbers; we do not publish anyone else's prices.

Where OSSeva fits

OSSeva does not support Oracle Database. For the Oracle systems you keep, Oracle or a third-party Oracle provider is the right call. For the databases that move, OSSeva for PostgreSQL includes Oracle-to-Postgres migration design on the Assure tier and supports the PostgreSQL you land on from the day of cutover, including versions past community end of life, on bare metal, VMs, Kubernetes or any cloud, priced per cluster. See Oracle to PostgreSQL with OSSeva.

Frequently asked questions

What happens in an Oracle license audit?

By Oracle's own description, LMS agrees objectives and a timeline with you, collects and analyses usage data by agreed methods, reports usage against your entitlements with any actions needed, and then works with you to resolve any compliance issue.

What are the alternatives to Oracle support?

Third-party Oracle support from firms such as Rimini Street and Spinnaker Support, Oracle's own Sustaining Support for versions past Extended Support, or migrating the database to an engine with a different support model.

Who offers Oracle third-party database support?

Rimini Street and Spinnaker Support both publish third-party support offerings for Oracle Database, with 24/7 coverage.

Does moving to third-party support end an Oracle audit?

No. Audits concern what you are licensed to run, which a change of support provider does not alter. Resolve any open finding with Oracle on its own terms.

Should we start migrating off Oracle during an audit?

Planning can start at any time, and an assessment of which schemas could move is useful evidence in a negotiation. Take advice before changing deployments while an audit is open, so the changes do not complicate the review.