When an audit finds a gap, Oracle often offers a new unlimited agreement to make it disappear. That settlement resets the certification cycle and raises your support base. The disciplined answer is to license the genuine gap directly and keep the problem defined.
By the Meridian advisory team · Ex Oracle licensing analysts · Updated June 2026
Because a new unlimited agreement is the most valuable outcome the vendor can extract from a compliance discussion. When an audit surfaces a gap between your certified counts and your live deployment, the immediate problem feels acute: a finding, a number, and pressure to resolve it. A fresh ULA answers all of that at once. The finding is folded into a new contract, the immediate exposure appears to vanish, and the conversation shifts from confrontation to renewal. For a buyer under pressure this feels like relief. The difficulty is what the relief costs. A new ULA resets the certification cycle you just completed, commits you to another multi year fixed fee, and lifts your recurring support base to a higher level that persists long after the audit is forgotten. The gap was a defined, one time problem. The settlement is an open ended one.
A new ULA offered to settle an audit is a trap dressed as a solution. It converts a manageable, bounded gap into a larger multi year commitment with a higher support base and a reset cycle. License the genuine gap directly instead. Keep the problem defined, keep the cost proportionate to the actual shortfall, and treat any decision to re enter a ULA as a forward looking strategy, never as a way to make a finding go away.
The mechanism is psychological as much as commercial. An audit creates urgency, and urgency narrows thinking. Faced with a remediation number, a buyer wants the matter closed, and the vendor offers a path that closes it cleanly. The new agreement is presented as good value: unlimited deployment again, the audit exposure absorbed, a single signature to make it all stop. What is rarely placed beside that offer is the honest comparison. How large is the actual gap. What would it cost to license only that gap. How does that compare against years of a new fixed fee and a permanently higher support line. When the comparison is drawn properly, the new ULA usually looks far more expensive than the problem it claims to solve. The trap depends on the comparison never being drawn.
The most durable cost is support. Oracle support fees are calculated from the agreement value and tend to rise rather than fall over time. A new ULA establishes a fresh, higher support base that you will pay year after year, indefinitely, regardless of how much you actually deploy. Settling a finite audit gap by lifting a perpetual annual cost is a poor trade in almost every case, because the gap is paid once and the support is paid forever. This is the quiet part of the re ULA that the urgency of the moment tends to hide.
License the genuine gap directly. If deployment grew beyond the count you certified, the proportionate response is to buy the specific licenses that cover that growth, scoped to the actual products and quantities involved. This keeps the problem exactly as large as it really is and no larger. It is a defined cost, paid against a defined shortfall, and it leaves the rest of your estate untouched. It does not reset the cycle, does not raise your support base across the board, and does not commit you to another term of unlimited deployment you may not need. The discipline is to separate two questions that the vendor would prefer to merge: what does the audit gap actually require, and what is the right long term licensing strategy. Answered separately, they rarely point to a new ULA.
| Response to an audit gap | What it costs | What it does to your position |
|---|---|---|
| License the specific gap | One time, proportionate to the shortfall | Problem stays defined and closed |
| New ULA as settlement | Multi year fee plus a higher support base | Cycle resets, support ratchets up |
| Deliberate strategic re ULA | Justified only by large certain future growth | A forward decision, not a settlement |
Consider a financial services firm, figures indicative only, audited two years after certifying and presented with a modest gap on one database option. The vendor offered a new three year ULA to resolve it, framed as the simplest path. On comparison, the gap could be licensed directly for a fraction of the new agreement value, while the proposed ULA would have raised annual support materially for years. The firm licensed the specific shortfall, closed the finding, and avoided a commitment many times the size of the original problem.
Yes, but only as a deliberate strategy, never as a reflex to close a finding. A new unlimited agreement can make sense when genuine future growth is large, spread across many Oracle products, and certain enough that unlimited deployment again would deliver real value. That is a forward looking decision, evaluated on its own merits with the numbers tested in advance, and it would be the right call whether or not an audit was in progress. The trap is specifically the use of a new ULA to dissolve an audit gap under time pressure, where the agreement is sized by the vendor to the moment rather than by you to your strategy. If a re ULA is genuinely right for your business, it will still be right after the audit gap has been licensed and closed on its own terms. Decoupling the two is how you tell a strategy from a trap.
The strongest protection against the re ULA trap is to never arrive at the audit with an undefended gap. Read defending your certified counts in an audit for how the evidence file keeps findings small, and LMS and GLAS after certification for how the engagement that leads here usually begins. Our post certification audit guide is the pillar that frames the whole defence. When an audit gap is on the table and a new agreement is being offered, the next step is an independent read before you sign anything.
Because it converts a one time compliance gap into a multi year commitment with recurring support. A new unlimited agreement can feel like relief, since it makes an immediate finding disappear, but it resets the certification cycle and raises the support base. The relief is real and short; the cost is larger and lasting. It is a settlement that benefits the vendor more than the buyer in most cases.
License the genuine gap directly. If deployment grew beyond the certified count, the disciplined response is to buy the licenses that cover that growth, on their own terms, rather than absorbing the gap into a fresh unlimited term. This keeps the problem defined and the cost proportionate, and it avoids resetting the cycle you just exited.
Occasionally, where genuine future growth is large, broad across many products, and certain enough to justify unlimited deployment again. That is a deliberate strategic choice, not a settlement reflex. The trap is using a new ULA to make an audit finding go away. The legitimate case is a forward looking decision made on its own merits, with the numbers tested first.