How an Oracle ULA works, from scope to certification and exit.

An Oracle ULA gives you unlimited deployment of named products across named entities for a fixed fee over three to five years. Certification then freezes what you deployed into a perpetual count that sets your Oracle costs for the next decade.

What is an Oracle ULA and how does it work?

An Oracle Unlimited License Agreement (ULA) allows you to deploy as much as you like of a named list of Oracle products, inside a named set of legal entities, for one fixed fee. The term usually runs three to five years. It ends with a certification that turns what you deployed into a fixed number of perpetual licenses.

Three mechanics set a ULA apart from ordinary licensing, and buyers make the least use of the second.

• Unlimited deployment during the term. Every install of a named product in a named entity is covered until the position is frozen at certification, by a document you sign.
• A fixed fee with support priced off it. Annual support is calculated from the ULA fee, not from the count you certify. The four hundredth processor costs nothing extra, nor does any further processor you can legitimately prove at certification.
• A count taken on one date. Certification counts what is installed and running on the certification date. The peak you reached during the term does not count if those servers were retired before it.

What does a processor above the certified count cost?

The certified number becomes a hard ceiling with a list price attached. The first Database Enterprise Edition processor above it is a new purchase at roughly $47,500 list, plus 22 percent of that every year for support, which is $10,450. So the certification quarter decides more money than any other period of the agreement.

Worked example: what the fee buys per processor

Say Oracle quotes a three year ULA for Database Enterprise Edition and four options at $5,000,000. At a 22 percent support rate, support is $1,100,000 a year. Neither figure changes with the number of processors you deploy.

At 100 processors the fee is higher than the database list value, so the deal only pays if you run the options widely. At 320 processors the same contract costs about a third of list.

What does the certification clause in an Oracle ULA say?

The certification clause sets the rules for the end of the agreement: when you declare, who signs, what counts and how cloud is treated. It sits in your ordering document from day one, yet most buyers first read it around month 34, when nothing in it can change, so pull it in month one.

Does cloud deployment count toward ULA certification?

Only in part, under most ordering documents written since 2019. The carve out either keeps public cloud deployment out of the count or averages it over the trailing year. Shifting Oracle workloads to cloud under an exclusion clause builds installs you cannot certify.

Where cloud does count, Oracle's cloud licensing policy sets the conversion for AWS, Microsoft Azure and Google Cloud. Two vCPUs equal one processor license when multithreading is enabled, and one vCPU equals one license when it is not. Our note on ULA deployments on AWS covers the detail.

When is ULA certification finished?

Certification is finished when Oracle returns a countersigned schedule listing your quantities. Signing and sending the declaration does not complete it. Until the schedule comes back, your certified position is a claim, and our ULA certification guide covers how to get it signed.

Which products and entities should an Oracle ULA cover?

Build the product list from your own deployment plan, and strike anything the account team adds beyond it. Most ULAs center on Database Enterprise Edition plus the options you run in production: Partitioning, Advanced Compression, Advanced Security, Real Application Clusters (RAC) and Multitenant. Middleware ULAs usually center on WebLogic Suite.

Applications rarely fit, because their user metrics do not grow the way processor counts do. Every product in scope that you never install still raises the fee, and with it the support line.

How wide should the entity scope be?

Draw it wide at signature. Name every subsidiary and the acquisitions you expect during the term, because deployments in an entity that is not listed are not covered and cannot be certified. Scope was drawn too narrowly in about half the agreements we worked on, which left certifiable deployments outside the fence.

How to check what you actually run before you sign

• Options and packs in use. Query DBA_FEATURE_USAGE_STATISTICS on each database, or run Oracle's options and packs usage script from My Oracle Support. Our note on the feature usage report explains how to read the output.
• Processor counts. Count physical cores per host and apply Oracle's core factor table. On VMware, export host and cluster data from vCenter, since Oracle's partitioning policy treats most virtualization as soft partitioning.
• Cloud instances. List every instance running Oracle software in AWS, Azure and Google Cloud, with its vCPU count and multithreading setting.
• Legal entities. Compare your current entity list, name by name, with the draft ordering document.
• Planned projects. Ask each application owner for funded deployments over the term, with budget and dates.

When does an Oracle ULA make sense?

A ULA makes sense when funded growth beats the breakeven, the point where the fixed fee costs less than licensing the same growth one purchase at a time. Treat it as a spreadsheet decision and leave the account relationship out of it.

• Right for funded growth. A database footprint expanding 25 percent or more a year with budget behind it, and deployment curves already climbing before anyone mentioned a ULA.
• Right for an acquisition pipeline. Companies that fold into entity scope and deploy before certification, or a funded rollout of database options across the business.
• Right for a known gap. An existing license shortfall absorbed at a negotiated rate instead of at the rate of an audit settlement.
• Wrong for flat usage or a funded exit. A shrinking footprint or a funded migration off Oracle turns the fixed fee into pure premium.

Worked example: where the breakeven sits

Say you run 200 Database Enterprise Edition processors and Oracle offers a three year ULA at $3,000,000 on top of what you already pay. Assume your normal net price is $23,750 per processor, half of list. The table prices the same growth bought one order at a time.

Support runs at 22 percent of the net amount on both sides, so it does not change the ranking. Funding does: if the 25 percent line has no approved projects behind it, the win in the last row is only a forecast.

What the Oracle account team will say, and how to answer

The first three lines are also the usual signs of a ULA sold for Oracle's reasons.

• "A ULA closes the audit finding cleanly." Ask for the finding to be settled on its own numbers first, then judge the ULA on your growth. A settlement priced into a fee is hard to see and harder to challenge.
• "The extra products are included at no cost." Ask for the fee quoted with and without products you have never installed. Anything that lifts the fee also costs 22 percent of that amount in support every year.
• "OCI credits make the overall deal cheaper." Ask for two quotes, one for the ULA and one for the credits, each on its own terms. A bundle hides which side carries the discount.
• "Renewing is simpler than certifying." Ask for the renewal quote in writing and compare its forward cost with the perpetual position you would hold after certifying.

How long should an Oracle ULA term be?

Three years is the most common term, and four or five years are worth considerably more when the project pipeline is real. Two extra years of unlimited installs are two extra years of certifiable deployment.

Why a short term is often the expensive choice

The usual advice is to keep a ULA short to limit the commitment. We disagree whenever funded projects exist for years four and five. A five year ULA at roughly a 15 percent premium over three years is usually a bargain. Using the $5,000,000 fee from the first example:

• Extra fee. 15 percent adds $750,000 to the license fee.
• Extra support. At 22 percent, support rises by $165,000 a year.
• Extra count. If funded projects add 40 processors a year in years four and five, the premium buys 80 processors at $9,375 each, against the $23,750 net price assumed in the breakeven example.

If the pipeline exists only on a slide, take three years and plan the certification properly instead.

How do you prepare for Oracle ULA certification?

Start nine to twelve months before the end date, with records kept to certification standard from month one. Teams starting in the final quarter lost 10 to 25 percent of the count they could have proven. Six in ten reached the window with incomplete records and paid that price.

Common certification mistakes

• Planning around the peak. Teams size their headroom on the highest deployment during the term, then find the count on the certification date is lower.
• Leaving standby nodes undecided. Whether a standby or DR node counts depends on "installed and running" versus "deployed". Settle it with legal at least three months before the window opens.
• Treating the declaration as paperwork. The signing officer is making a representation for the company, so legal should review the text and the evidence behind it.
• Stopping at submission. Without the countersigned schedule you have nothing to show in the next audit.

Our 90 day certification checklist covers the final quarter. The perpetual variant, which has no certification date and a trap of its own, is covered in our PULA versus ULA analysis.

What have we seen in recent Oracle ULA engagements?

Across the 40 to 50 Oracle ULA scopings, renewals and certifications I ran or benchmarked in 2024 and 2025, the count a buyer could prove was consistently above the number Oracle opened with. The gap came from evidence, scope and timing.

• Records decided the count. The count is only as good as its evidence, and a server with no record for the certification date stayed out of the declaration.
• Scope left count outside. In about half the agreements, subsidiaries and recent acquisitions sat outside the certifiable scope because they were not named at signature.
• Renewal arrived as partnership. Oracle pitched renewal as a relationship step in cases where the arithmetic already favored certify and exit.

A ULA pays off for the buyer who runs it as a three to five year project and decides the ending on breakeven arithmetic.

Should you renew an Oracle ULA or certify and exit?

Certify and exit, unless a renewal beats the perpetual position you already hold on forward cost. Where buyers let the arithmetic decide, certify and exit beat the pitched renewal by 30 to 50 percent on the forward license position. Support stays priced off the ULA fee either way, so the certified count is capacity you have already paid for.

A renewal has to beat that locked perpetual position, which covers current deployment plus the headroom you can prove. If it adds only products and years you do not need, it is a new purchase. Our guide to ULA renewal negotiation covers the offer itself.

How support and Support Rewards change the comparison

After certification, support continues at the level the ULA fee set. Oracle's matching service levels rule stops you dropping support on part of a license set, and its repricing rule raises support on what remains if you terminate licenses, so the line is hard to cut. Within Oracle's own programs, the one way to bring it down is Support Rewards.

Support Rewards credit a share of OCI consumption against technology support invoices. Customers with an active ULA accrue 33 cents per OCI dollar, against 25 cents for other customers. See our 2026 Support Rewards guide for the details, and the ULA exit strategy guide for the exit paths and their order.

Contract wording to ask for at signature or renewal

• Entity definition. Cover all majority owned subsidiaries, plus entities acquired during the term once you notify Oracle. This keeps acquisitions inside the count.
• Counting wording. Define "installed and running" and state how standby and DR nodes are treated. This settles the standby question before the window opens.
• Cloud counting. Count deployments in AWS, Azure and Google Cloud on the certification date under Oracle's published vCPU rules, with no trailing average.
• Countersignature timing. Oblige Oracle to return the signed schedule within a fixed number of days of your declaration.
• Divestiture rights. Let certified licenses move with a business you sell, so the unit you sell is not left unlicensed.
• Support increases. Cap the annual increase on ULA support during the term and in the years after certification.

What to do next

1. This week. Pull the certification clause and note the window, the signatory, the counting wording and the cloud carve out.
2. This month. Compare the ULA entity list with your legal structure and the acquisitions planned for the term.
3. Every quarter of the term. Keep deployment records to certification standard for every host, cluster and cloud instance.
4. Nine to twelve months out. Start the count, then compare certify, renew and exit on forward cost with any Oracle offer in writing.
5. In the window. Submit the signed declaration and keep going until Oracle's countersigned schedule arrives. Our Oracle practice runs the certification with you.

Frequently asked questions