Submitting the certification letter is the moment unlimited deployment becomes a fixed, permanent entitlement. What follows decides whether that entitlement holds. This is what actually happens after the letter, and why the evidence behind your count still matters long after it is signed.
The deployment quantities you declared convert into perpetual entitlements and the unlimited right ends. Support continues at the existing ULA level regardless of the number you certified. Oracle may review the declaration, so from that point the evidence behind the count has to stand on its own. The letter is not the finish line. It is the start of the period you have to defend.
The certified count is only as durable as the evidence behind it. A confident letter with a thin file is an invitation. A measured letter with a complete file is a fortress.
At certification the named products you deployed convert from an unlimited right into a fixed quantity of perpetual licenses. That number is now your entitlement forever. Whatever you counted, you keep. Whatever you missed, you have lost, because the unlimited deployment right is gone the moment the term closes. This is why the count submitted on the letter carries so much weight and why it should be maximized and defensible before it is ever sent.
A persistent fear is that certifying a larger number drives up the annual support bill. It does not. Support fees continue at the level set under the ULA and do not rise because the certified count is higher. A larger defensible number is therefore free value, captured at no additional support cost. The myth that certifying more raises support keeps organisations from claiming entitlement they are fully due, and it is worth debunking plainly.
Submitting the letter does not end Oracle's interest. A certification can be reviewed, and audit risk rises in the first two years afterward. The review tests whether the deployments you certified were genuinely live within the term and whether the methodology behind the count holds up. This is not an adversarial certainty, but it is a real possibility, and it is the reason the evidence file is assembled before the letter rather than reconstructed after a request arrives.
The evidence file is the record that makes the certified count defensible after the fact. It typically holds server inventories, tool output, the methodology used to count processors and Named User Plus, and documentation showing each counted instance was deployed within the term. If Oracle asks how a number was reached, this file answers. Without it, a perfectly legitimate count can look unsupported, and an unsupported count is where remediation demands begin.
Where cloud deployments were counted, the file should show they met the contract's conditions, for instance a 365 day continuous run where the agreement requires it. Where virtualized estates were counted, the file should document how the VMware footprint was measured, because Oracle's partitioning stance treats soft partitioning as not limiting scope and the record needs to reflect what was actually counted.
A retailer certified a database estate and archived a complete evidence file with server lists, deployment dates, and methodology. Roughly 18 months later Oracle questioned a block of disaster recovery instances. Because the file showed each instance live within the term, the count held with no remediation. A peer that had certified a similar estate without the file faced a far harder conversation. Figures are indicative and depend on the specific contract language.
After certification your deployment is capped at the perpetual quantity you secured. Genuine growth beyond that count needs new licenses bought deliberately, not a panic return to another ULA. Treating ordinary growth as a crisis is how organisations end up paying for flexibility they do not need. A measured purchase plan keeps you compliant without overcommitting.
The exact review rights, the support continuation terms, and the conditions on counted deployments all live in your specific agreement. Two organisations can face very different post certification realities because their contract language differs. In ULA work the answer almost always depends on the specific wording, so the durable approach is to know your own terms and hold the evidence that matches them.
If your certification letter is signed or about to be, make sure the period that follows is one you can defend. Start with the Oracle ULA certification guide, then read the difference between certification and an audit and negotiating the certification outcome.
The declared deployment quantities convert to perpetual entitlements and the unlimited right ends. Support continues at the ULA level regardless of the certified number. Oracle may review the declaration, so the evidence behind the count has to stand on its own from that point forward.
No. Support fees continue at the existing ULA level and do not rise because you certified a higher count. A larger certified number is therefore free value, which is why the fear that certifying more raises support is a myth.
Audit risk rises in the first two years after certification. Oracle can examine whether the certified deployments were genuinely live within the term. The evidence file behind the declared count, including server lists and methodology, is the defense, so it must be preserved.
Book a confidential assessment and we will make sure the count you certify is backed by an evidence file that holds for years, not weeks.