Most ULAs certify the deployment that exists at the end of the term, not the highest point you reached during it. So a peak hit mid term and then reduced may not count unless the deployment is still live at certification. The exact wording is contract specific, and it decides your certified number.
By the Meridian advisory team · Ex Oracle licensing analysts · Updated June 2026
This is one of the most consequential questions in the whole exit, and the honest answer is that it depends on your contract. Most ULAs are written to certify the deployment that exists at the end of the term. Under that wording, a peak you reached in year two and then unwound does not count if those instances are gone by certification. What is live at the measurement point is what converts to perpetual entitlement. Some agreements are worded differently, which is exactly why you read your own contract rather than relying on a general rule. The wording on what you measure, and when, sets the ceiling on your certified number.
Treat the measurement point, usually the term end, as the moment that counts. Anything legitimate you want as permanent entitlement should still be deployed at that moment. A peak you have already torn down is, for most contracts, a peak you cannot certify.
Once you understand that most contracts count what exists at the term end, several decisions look different. Routine infrastructure cleanup stops being neutral. Decommissioning an Oracle server a month before certification can quietly remove it from the count, surrendering entitlement that the unlimited right paid for. Equally, a legitimate build out you complete late in the term, and keep live through the measurement point, lands in the certified number. The measurement point is the line everything is measured against, so the estate should be deliberately shaped toward it rather than drifting into it.
The table below shows an indicative example of the same estate measured two ways. The figures are illustrative.
| Environment | Live at term end? | Counts (term end basis) |
|---|---|---|
| Production | Yes | Yes |
| Disaster recovery | Yes | Yes |
| Mid term project cluster, since removed | No | No |
| Test, kept live to certification | Yes | Yes |
Indicative only and assumes a contract that counts deployment at the term end. The mid term project cluster represented real entitlement that was lost simply by being removed before the measurement point.
You can, and sometimes you should, but it has to be a decision rather than a habit. If a server is genuinely surplus and you have no reason to want the permanent entitlement it represents, removing it before the term ends is reasonable. But removing a server you would have valued as perpetual licensing, just because a project finished or a team wanted to tidy the estate, permanently surrenders that entitlement. Before any pre certification decommissioning, the question to ask is simple: is this hardware worth more to us as a retired box or as permanent Oracle entitlement we never have to buy again?
As a general rule, yes, for any deployment that is legitimate and that you may want as permanent entitlement. Because most contracts count what exists at the measurement point, tearing down legitimate environments early lowers your certified position for no commercial gain. The discipline is to freeze the estate ahead of the measurement point, hold the legitimate deployments live, and only then certify. This is not about inflating the count with environments you do not use. It is about not throwing away entitlement you are genuinely entitled to claim.
Everything above assumes the common term end basis, and your agreement may say something else. Some contracts use different language about the measurement, and capped or hybrid structures can change what is countable. This is a place where reading the exact words matters more than applying a remembered rule, because a wrong assumption about the measurement basis can cost or expose a large number. Where the contract is ambiguous, that ambiguity should be resolved before you shape the estate, not after.
Read processor counting rules at certification to see how the deployments you keep live are converted into a processor number, and server lists, screenshots, and tool output to evidence the estate as it stood at the measurement point. When you want the measurement basis read against your own contract, our Oracle ULA certification guide is the pillar that covers counting and certification in full.
It is contract specific. Most ULAs certify deployment that exists at the end of the term, so a peak reached mid term and then reduced may not count unless the deployment still exists at certification. Read your own agreement, because the precise wording on what and when you measure decides the certified number.
If your contract counts deployment at the term end, removing a server before you certify usually removes it from the count. That can be the right move for hardware you no longer need, but it permanently surrenders the entitlement, so the decision should be deliberate rather than a routine cleanup.
Generally yes, where the deployment is legitimate and you may want the permanent entitlement. Because most contracts count what exists at the term end, tearing down legitimate environments early can quietly lower your certified position. Keep what you are entitled to count live until the number is locked.