Oracle ULA certification is the one time event that converts unlimited deployment into a permanent entitlement. The count you declare becomes your perpetual license forever, so the number has to be complete, defensible, and built on evidence before the window closes.
A ULA, or Unlimited License Agreement, grants unlimited deployment of named Oracle products for a fixed term, usually three to five years, for a fixed fee. At the end of the term you do one of two things. You certify, which converts the quantity you have deployed into a perpetual entitlement and ends the unlimited right, or you renew for another term. Certification is declared in a letter the contract typically requires a senior executive to sign. Whatever you can count and defend at that moment, you keep for good. Whatever you miss, you lose.
You should enter your certification window already knowing your number, measured independently, reconciled to your contract, and ready to defend. Surprises favour the vendor.
No, and this is the single most expensive myth in ULA work. There is no fee to certify, and support continues at the ULA level no matter how many licenses you certify. A higher certified count is free value. An organisation that certifies the minimum it can prove pays exactly the same annual support as one that certifies a maximized, fully evidenced count. The only difference is how much perpetual entitlement each one owns afterward. We debunk this and the rest in the ULA myths that cost money.
Certification is a measurement exercise followed by a declaration. The work that decides the outcome happens before you ever send a letter to Oracle.
Your certification rights, the cloud clause, the customer and entity definitions, and the territory language all live in the agreement. They decide what counts. Start by reading your ULA contract properly, because in ULA work the answer almost always depends on the specific wording.
Measure true deployment across databases, options, and packs, including production, test, disaster recovery, virtualization, and cloud. Oracle LMS scripts are a choice, not an obligation, and that choice deserves analysis rather than reflex.
Every environment you are entitled to count, you count, each one backed by evidence. Certified counts often land 1.5 to 2.5 times higher than a first internal estimate once cloud, disaster recovery, and non production deployments are handled properly. These figures are indicative and depend on your estate.
Prepare the certification letter and the evidence file behind it, close the exchange with Oracle, then document and monitor the entitlements so a future migration, acquisition, or audit cannot erode them.
Processor counting applies core factors to physical cores. Named User Plus applies where the metric calls for it. Production, test, and disaster recovery instances deployed inside the term are all in scope. The evidence file matters as much as the number itself: server lists, tool output, and methodology documentation are what make a count survive the two years of heightened audit risk that follow an exit.
| Environment | Physical cores | Core factor | Processor licenses |
|---|---|---|---|
| Production cluster | 320 | 0.5 | 160 |
| Disaster recovery | 160 | 0.5 | 80 |
| Test and development | 96 | 0.5 | 48 |
| Authorized cloud (365 day rule met) | 64 vCPU | per policy | 32 |
| Certified total | 320 |
The figures above are indicative and the core factor and cloud treatment depend on your products and contract. The point is structural: the disaster recovery, test, and cloud rows are the ones teams routinely leave out, and they are often half the certified value. The core factor mechanics are worked through in how to read your ULA contract.
Cloud counting is contract specific. Many ULAs require deployments 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, the workloads can be repatriated on premises or moved to OCI before the exit so they do count.
Under Oracle's partitioning stance, soft partitioning does not limit scope, so an entire VMware cluster can be swept into the count. Isolation, dedicated clusters, and documentation are the defense. In a maximization context the same rule can work in your favour, because a broad cluster that is genuinely running Oracle can lift a defensible count.
Cloud eligibility, the 365 day rule, the customer definition, and territory scope are all decided by your specific wording. Treat any general statement here as a starting point and confirm it against your agreement.
Audit risk rises in the first two years after certification, and the evidence file behind your certified counts is the defense. Growth beyond the certified number needs new licenses bought deliberately, not a panic decision to re enter a ULA. A clean exit is the start of a managed position, not the end of the work.
Each guide below goes deep on one part of the certification. Start with the fundamentals, then the process, then the counting.
The structure, the term, the fixed fee, and the certify or renew choice that ends it.
The clauses that decide your count: certification rights, cloud, customer definition, and territory.
The estates where unlimited deployment never pays back, and the signals to watch.
The support fear, the cloud assumption, and the other beliefs that quietly shrink a certified count.
No. Support fees continue at the ULA level regardless of the number you certify, so a higher certified count is free value. The fear that certifying more raises support is a myth. You pay the same support whether you certify the minimum or the maximum defensible number.
No. Certification itself carries no fee. You declare your deployed quantities and Oracle converts them to perpetual entitlements. The cost of certifying badly is the value you fail to capture, not a charge from Oracle.
It depends on your contract. Many ULAs require AWS or Azure deployments to run 365 continuous days to count, some exclude public cloud entirely, and many are silent on GCP. Silence is not inclusion. Read the cloud clause before you rely on cloud volume.
Book a confidential assessment and we will tell you what your certification is really worth and what we would do to protect it.