An Oracle ULA grants unlimited deployment of named Oracle products for a fixed term and a fixed fee, ending in either a certification or a renewal. Understanding that structure before you sign, and long before you exit, is how buyers turn unlimited deployment into permanent value.
By the Meridian advisory team · Ex Oracle licensing analysts · Updated June 2026
An Oracle ULA is an Unlimited License Agreement. It grants unlimited deployment of a named set of Oracle products for a fixed term, usually three to five years, in return for a single fixed fee. During the term you can deploy as much of those products as you want. At the end you certify the quantities you deployed into perpetual licenses, or you renew for another term.
A ULA is not unlimited forever. It is unlimited for a term, after which the number you certify becomes the number you keep. The whole value of a ULA is decided in the weeks around that exit.
The mechanics are simpler than the contracts make them look. A ULA has three moving parts: the products in scope, the term and fee, and the exit.
A ULA covers a named list of Oracle products, not the whole Oracle catalogue. Common inclusions are the Database, options such as partitioning and advanced security, and management packs, but your agreement lists exactly which products carry the unlimited right. Deploying a product that is not on the list creates exposure, not entitlement, so the scope list matters as much as the unlimited promise.
You pay a single fixed fee for the term and an annual support fee alongside it. The support fee continues after the agreement ends and is the cost that follows you for years, so it deserves more attention than the headline ULA fee. Within the term, deployment is unlimited and costs nothing extra, which is why the period is meant for building out the estate, not holding back.
As the term ends you reach a fork: certify or renew. This is the single most important moment in the life of the agreement, and it is the moment Oracle has refined most carefully to its own advantage. We cover it next.
You either certify or renew. Certification converts the quantities you deployed during the term into permanent entitlements. You declare your deployment, usually in a certification letter that a senior executive signs, and once accepted those quantities are yours in perpetuity while the unlimited right ends. Renewal instead buys another fixed term of unlimited deployment for a new fee, deferring the same decision to a later date.
The choice is not about preference, it is about arithmetic. Certify when your deployment is mature and a complete, defensible count captures most of the value you will ever use. Renew when a large deployment wave is still ahead. Our companion guide on whether to certify or renew models both paths in detail.
There is no fee for the certification itself. The cost question that actually matters is support, and here a stubborn myth does real damage. Support continues at the ULA level regardless of how many licenses you certify, so certifying a larger number does not raise your support bill. A higher certified count is free value. Organisations that believe the opposite often renew out of fear or under count at exit, and both choices leave permanent entitlement on the table.
Suppose an organisation signs a four year Database ULA. Over the term it deploys the Database across production, a disaster recovery site, and several test environments. At exit it counts only production and certifies a modest number. A complete count, including disaster recovery and qualifying test environments, would have certified far more for the same support fee. The figures below are illustrative.
The support fee is identical in both rows. The only difference is how much permanent entitlement the organisation walks away with. Whether each environment qualifies depends on the contract and the evidence, which is the substance of the work.
Not every unlimited agreement behaves the same way. A capped ULA limits the unlimited right to a stated ceiling. A hybrid ULA folds cloud rights into the agreement. A PULA, or Perpetual Unlimited License Agreement, is perpetual and has no certification exit at all. We unpack the variants in capped and hybrid ULAs explained, and the meaning of the word unlimited itself in what unlimited really means in a ULA.
If your ULA is within roughly eighteen months of expiry, the next step is to understand your real deployment before Oracle does. Our Oracle ULA certification guide is the pillar that ties these fundamentals together and walks through the certification window end to end.
An Oracle ULA is an Unlimited License Agreement. It grants unlimited deployment of a named set of Oracle products for a fixed term, usually three to five years, in return for a single fixed fee. At the end of the term you certify your deployed quantities into perpetual licenses or you renew.
You either certify or renew. Certification converts the quantities you deployed during the term into permanent entitlements, declared in a letter a senior executive usually signs, and the unlimited right ends. Renewal buys another fixed term of unlimited deployment for a new fee.
There is no fee for the certification itself. Support continues at the ULA level regardless of how many licenses you certify, so a higher certified count is free value. The belief that certifying more raises support is a myth that costs organisations real entitlement.