Oracle raised a compliance question in six of ten exits, almost always at the end

Certification turns your deployed usage into a permanent license count. It is the most valuable hour of the whole agreement, and Oracle earns more from a renewal than from an exit, which makes the pressure that arrives in the final two quarters entirely predictable and entirely manageable.

Prepared by Redress Compliance · August 15, 2026 · Oracle advisory. 30 to 40 ULA certifications supported, 2024 to 2026.

• Start nine to twelve months out so no compliance question can arrive before you hold your own number, and no deadline can force a rushed count.
• Run your own measurement across physical, virtual, and cloud hosts rather than accepting an offer to be counted, because the declaration is yours and so is the evidence behind it.
• Commission an independent sweep, since one found eligible deployments the internal team had missed in four of five engagements, typically in virtual estates and uncatalogued option usage.
• Count on the contract metric, processor or named user as your signed agreement defines it, rather than on the metric anyone remembers.
• Keep the count complete but defensible, which means every genuinely deployed workload and nothing merely theoretical, per the production reality standard.
• Separate the renewal conversation from the compliance conversation in writing, and decline to price a second term until the baseline is finished.

When a compliance question arrives in the last two quarters of a ULA term, buyers tend to read it as a signal about their estate. It is better understood as a signal about the calendar. Oracle's commercial interest at that moment is unambiguous: a renewal extends and grows the support annuity, while a certification caps it at a fixed number. Everything else follows from that, including the timing, which in six of ten exits we supported placed the question precisely where it would do the most work.

What makes the tactic effective is not the substance of the question but the buyer's inability to answer it quickly. An organization without a finished count cannot say whether the concern is material, cannot scope the exposure, and cannot distinguish a routine inquiry from a genuine finding. Uncertainty of that kind has a natural resolution, and the resolution being offered is a renewal, which conveniently makes the question moot. The buyer who already holds a documented count faces the same question as a matter of fact checking rather than existential risk.

The second reason to start early has nothing to do with pressure and everything to do with money. Counts improve with time: early prepared certifications came in 12 to 22 percent above the client's own first internal estimate, and independent sweeps found eligible deployments the internal team had missed in four of five engagements. Those are not rounding errors; they are perpetual entitlements, paid for during the term, that a rushed count silently returns to Oracle. Estates that began inside ninety days certified low for exactly this reason, and there is no mechanism to revise the number afterwards.

So the defense against retention pressure is the same work as the defense against under counting, done once, early. Nine to twelve months out, run your own discovery, reconcile it, document it, and hold the number. A compliance question then becomes correspondence rather than a crisis, a renewal quote becomes a comparison rather than a rescue, and the certification letter becomes the audit defense that protects the estate for years afterwards. The declaration mechanics are in the certification guide, the walk away decision in the exit strategy, and the wider library in the Oracle practice.

Watch the briefing · 4:30How to Negotiate an Oracle ULA: No Price List, Just Your Business CaseThe certification mechanics and the renewal trap that decides whether a ULA was worth signing at all.

Across 30 to 40 Oracle ULA certifications supported, the gap between a rushed count and a prepared one was stark:

The patterns: estates beginning inside 90 days certifying low and permanently, internal counts missing eligible deployments in four of five engagements, and compliance questions landing hardest on buyers who had no number of their own.

The buyer side move is to hold your count before the question arrives. The wider library sits in the Oracle practice.

Why would Oracle discourage certification?

Because Oracle earns more from a renewal than from an exit. Certification converts your deployment into a fixed perpetual count and ends the unlimited right, so retention pressure in the final quarters of a term is the predictable commercial response rather than a sign that anything is wrong with your position.

What form does the pressure take?

Most often a compliance question or a proposed review: Oracle raised one in roughly six of ten exits we supported, almost always in the final two quarters. The effect is to introduce doubt at the exact moment the buyer needs certainty, which makes a renewal feel like the safer path.

How much does starting early change the count?

Clients who started early certified counts on average 12 to 22 percent higher than their first internal estimate. Estates that began inside 90 days of the deadline certified low and left perpetual entitlement on the table, because there was no time to find what the first pass missed.

Does an internal count find everything?

Rarely. An independent discovery sweep found eligible deployments the internal team had missed in four out of five engagements, typically in virtual estates, forgotten environments, and option usage nobody had catalogued.

Who should measure the estate?

You should. Run your own measurement rather than relying on Oracle to count your estate, because the declaration is yours to make and a certification backed by your own discovery evidence is hard to question. It is also your best audit defense afterwards.

What makes a certification defensible?

Evidence and metric discipline. Count using the metric in your signed agreement, processor or named user, document the discovery output behind every number, and file a structured declaration. A count backed by evidence withstands a challenge; an asserted number invites one.

When should certification work start?

Nine to twelve months before the term ends, so the calendar never forces a rushed count. That window also means a compliance question raised in the final quarters lands on a buyer who already has their own number, which is what turns retention pressure into noise.