The most expensive belief in Oracle ULA work is that certifying a higher count raises your support bill. It does not. Support stays flat at the ULA level whatever you certify, so the myths below quietly cost customers entitlement they were entitled to claim for free.
By the Meridian advisory team, former Oracle LMS and GLAS licensing analysts. Updated 4 June 2026.
This is the costliest myth, so it goes first. Support fees under a ULA are set at the ULA level and continue at that level after certification, regardless of how many processors you declare. Certifying 3,000 processors rather than 2,000 does not raise your support invoice. The extra 1,000 are perpetual licenses you receive at no additional fee and no additional support cost. The fear of a higher support bill makes teams hold their number down, and every processor they fail to certify is permanent entitlement surrendered. The correct instinct is the opposite: count everything you are legitimately entitled to count, because the marginal cost of a higher defensible number is zero.
A higher defensible certified count is free value. Support does not move with the number you certify. The only question worth asking is whether each deployment is real, in scope, and supported by evidence.
Running Oracle LMS measurement scripts is a choice, not an obligation, unless your specific contract requires them. You are entitled to measure your own estate with your own tooling and to certify on the evidence you assemble. The scripts produce a particular view of your deployment, and that view is not always the one most favourable or most defensible for you. The decision to run them, or not, deserves analysis rather than reflex. Handing Oracle a full script output before you understand your own position can surface exposures you were not ready to discuss. Measuring independently first puts you in control of the conversation.
Cloud counting is contract specific, and the default assumption that anything running in AWS or Azure counts toward your certification is wrong more often than it is right. Many ULAs require cloud deployments to run for 365 continuous days to count. Some exclude public cloud entirely. Many are silent on GCP, and silence is not inclusion. Building a certified number on cloud volume you assume qualifies, without reading the cloud clause, is how teams end up declaring a count they cannot defend. The reverse error is just as costly: cloud that does count, left out of the number because nobody checked. Read the clause, then count, as we set out in reading your ULA contract properly.
Certification is not paperwork. It is the single irreversible event that converts unlimited deployment into a fixed perpetual entitlement, declared in a letter that the contract typically requires a senior executive to sign. Whatever you fail to count, you lose. Whatever you cannot defend becomes audit exposure in the years that follow. Treating the certification as a form to be filled at the last minute is how organisations under count and over expose at the same time. It is a project with a finite window, and it rewards preparation.
When Oracle proposes a renewal, the first number is an opening position, not a settled price. Renewal quotes typically move by 20 to 40 percent through a properly run negotiation, and the product list, the term, and the conditions are all in play alongside the fee. Accepting the first quote as the price leaves money on the table by definition. The decision between certifying out and renewing should be made on your own model of both paths, not on the figure Oracle leads with.
| Myth | The reality | What the myth costs |
|---|---|---|
| Certifying more raises support | Support stays flat at the ULA level | Perpetual entitlement surrendered |
| LMS scripts are mandatory | They are a choice unless required by contract | Control of the count handed away |
| Cloud always counts | Counting is contract specific | An indefensible or undersized number |
| Certification is a formality | It is irreversible and evidence based | Under count plus audit exposure |
| The renewal quote is the price | It is an opening position | 20 to 40 percent overpaid, indicative |
Figures here are indicative and the outcome in your case depends on your contract and your estate, but the direction holds across the engagements we see.
Most ULA money is lost not to bad luck but to belief. Certify everything you can defend, because support does not move with the number. Treat the scripts and the cloud clause as decisions, not defaults. Run the certification as a project, and treat any quote as a starting point. For the full mechanics, read the pillar, the Oracle ULA certification guide, and the structural overview in what an Oracle ULA actually is.
No. Support fees continue at the ULA level regardless of the number you certify. A higher certified count is free perpetual value. The belief that a larger number raises support is the single most expensive myth in ULA work, because it makes customers leave entitlement on the table.
No. Running Oracle LMS scripts is a choice, not an obligation, unless your contract specifically requires them. You can certify using your own measurement and evidence. The decision deserves analysis, because the tooling you use shapes the number you declare and the risk you carry.
Book a confidential assessment and we will tell you what your certification is really worth and what we would do to claim it.