Certification converts your deployed Oracle quantities into a permanent entitlement, and support fees stay flat whatever number you certify. So the count you can defend is the value you keep. This guide shows how to grow that defensible count before exit.
Deployment maximization is the disciplined work of deploying and counting every Oracle license you are entitled to before the ULA term ends, so the certified perpetual entitlement is as large and as defensible as possible. Because support cost does not move with the count, a higher defensible number is free value you keep forever.
There is no fee to certify, and your support stream continues at the ULA level no matter what you certify. Counting more does not cost more. Counting less simply hands value back.
Whatever you certify becomes your perpetual entitlement and the unlimited right ends. Deployments you fail to count are lost. Deployments you cannot evidence become audit exposure.
Certified counts often land 1.5 to 2.5 times higher than a first internal estimate once cloud, disaster recovery, and non production are handled properly. That range is indicative and depends on your estate and contract.
The table below shows an indicative database estate. The first column is a typical first pass that counts only obvious production servers. The second is the maximized, defensible position once every entitled environment is measured and evidenced. The figures are illustrative and a real position always turns on the contract language.
| Environment | First pass (processors) | Maximized and defensible |
|---|---|---|
| Core production | 800 | 800 |
| Test and development | 0 | 260 |
| Disaster recovery and standby | 0 | 340 |
| Virtualized clusters counted in full | 0 | 420 |
| Eligible cloud meeting the contract test | 0 | 180 |
| Certified total | 800 | 2,000 |
The maximized position is 2.5 times the first pass, and every added processor carries no extra support cost. The whole difference is captured by counting what the agreement already permits and by holding the evidence to defend it.
Read the customer definition, the territory and entity scope, and the cloud and virtualization language first. The contract decides what counts, so the count starts there, not in a tool.
Disaster recovery, standby, test, development, and eligible cloud are routinely missed. Each is potential permanent entitlement when it sits inside scope and is deployed within the term.
Where headroom exists and a real business need supports it, deploy inside the term so the workload counts. A cloud workload that must run 365 continuous days has to start early enough to qualify.
Server lists, tool output, and a written methodology turn a count into a defensible count. The evidence is what protects the position in the first two years after exit, when audit risk rises.
The same rules that can inflate your exposure can grow your defensible count when you read them early and act on them.
Cloud counting is contract specific. Many agreements require a deployment in AWS or Azure to run 365 continuous days to count toward the certification baseline. Some exclude public cloud entirely. Contracts are frequently silent on GCP, and silence is not inclusion. Where cloud does not count, eligible workloads can be repatriated on premises or moved to OCI before exit so they do count. This is one of the places an answer always depends on your specific wording.
Under Oracle's partitioning stance, soft partitioning does not limit scope, so an entire VMware cluster can be swept into a count. In an audit that is a threat. In a maximization context the same rule lets a properly documented cluster contribute its full processor count to your permanent entitlement. Isolation, dedicated clusters, and documentation decide which way it goes.
Read the contract before you read the tooling. The agreement, not Oracle's default interpretation, sets what you may count. Maximization is the discipline of claiming every entitlement the words already grant you.
No. Support fees continue at the ULA level after certification regardless of the certified count. A higher defensible number is free value. The fear that certifying more raises support is a myth worth retiring.
Indicative experience puts certified counts at 1.5 to 2.5 times higher than a first internal estimate once cloud, disaster recovery, and non production deployments are counted properly. The exact uplift depends on your contract language and your estate.
Disaster recovery and standby instances, test and development environments, virtualized clusters, and eligible cloud workloads are the deployments most often left uncounted. Each can be legitimate certified entitlement when it sits inside scope and is supported by evidence.
We measure your true position, find every entitlement you can defend, and build the evidence file behind it. Tell us where you are in your term.