Oracle PULA contract traps: ten defaults to rewrite. Each one lasts as long as the agreement.

The ten traps in an Oracle PULA contract are defaults in the standard order form, not hidden clauses. In a ULA, bad wording expires at certification. A PULA has no certification day, so the paper you sign is the paper you keep.

What are the ten traps in an Oracle PULA contract?

They are ten defaults in Oracle's standard order form: five on scope, three on money and two on exit. None of them is hidden. Each one is simply what the form does with a question you did not answer in writing, and on a Perpetual Unlimited License Agreement anything left vague at signature resolves in Oracle's favor.

If the form says nothing about cloud rights, cloud deployments are outside the grant. If it says nothing about affiliates, your subsidiaries are outside it too. The table lists each default, what it does to you, and the line to put in the order form instead.

Why the exposure sits in three lists

Most of the risk in a PULA sits in three ordinary lists: products, entities and territories. Those lists decide what the unlimited grant covers, so the side that drafts them controls the deal.

The drafts Oracle sends describe your company as it looked on the day of the quote. A perpetual agreement has to fit the company you will be in ten years.

Why is a drafting mistake in a PULA permanent?

A drafting mistake in a PULA is permanent because the agreement has no certification day. Under a standard ULA the term ends, you certify your deployments, and a badly drafted clause expires with the term. The PULA removes that deadline, so a mistake made in year one is still on the support invoice in year fifteen.

Certification is more than an exit. It disciplines the drafting on both sides, because everyone knows the language will be tested and reopened within a few years. Take the deadline away and the whole weight of the deal falls on the version you sign.

What does the perpetual premium add to your support bill?

Oracle starts from your current processor and named user position, adds a three to five year growth projection, and prices a perpetual premium of 20 to 40 percent over a comparable ULA. The premium pays for removing certification, and with it every future point at which both sides must renegotiate.

The premium does not stay on the license line, because Oracle derives annual support from the fee. Say Oracle would quote a comparable ULA at $6,000,000. The PULA then lands between $7,200,000 and $8,400,000, and at 22 percent support the premium alone adds $264,000 to $528,000 to every year's support invoice.

Why a line by line review of Oracle's draft is not enough

The usual advice is to read Oracle's order form carefully and push for a bigger discount at quarter end. We disagree with both halves. A careful read catches bad wording, yet the ten defaults live in what the form leaves out, and a larger discount does nothing about a scope gap you pay for every year.

Treat every line as yours to draft. A scope term you fail to write in 2026 stays unwritten, because a PULA has no next renewal at which to add it. The result to aim for is a short list of unwritten items, ideally none, with the price negotiated only after the lists and clauses are settled.

The license fee is paid once. A sentence left out of a PULA is paid for every year the software runs.

How do the five scope defaults work in a PULA?

Each scope default narrows which products, which companies, which places and which platforms the unlimited grant covers. Over a perpetual horizon, acquisitions, disposals and cloud migrations are close to certain, so a scope written narrowly today turns into a licensing gap later.

Trap 1: a product list written as SKUs

The product list is the entire universe of the grant. Written as SKUs, it excludes every option, pack and acquired product Oracle ships after signature. Written as product families, the same paragraph covers the software you will actually run in year five.

Before you agree the list, query DBA_FEATURE_USAGE_STATISTICS on every database to see which options and management packs are in use, and read why to run the feature usage report before Oracle's scripts. Then ask application owners what they plan to add or retire.

Trap 2: an entity clause narrower than the group

The entity clause decides who may use what you bought. A company you acquire arrives outside the grant, and a business you sell leaves stranded, unless the clause covers the legal parent plus all controlled affiliates and carries an M&A and divestiture mechanism. Our note on carve out license transfers covers the divestiture side.

Trap 3: territory tied to named countries

The grant covers only the territories the paper lists, wherever your workloads end up. Country level scope blocks the disaster recovery region you have not built yet and the market you have not entered yet. Ask for regions wherever the business operates, and check the list against your three year infrastructure plan.

Trap 4: cloud rights left unwritten

A PULA covers public cloud deployments only if the order form says so. Oracle's authorized cloud policy lists AWS (EC2 and RDS), Microsoft Azure and Google Cloud Platform, and counts two vCPUs as one processor license where multithreading is enabled. It sets counting rules only and places nothing inside your unlimited grant.

A PULA silent on the hyperscalers is a data center agreement carrying an unlimited label. Ask for a BYOL clause that names AWS, Azure and Google Cloud and says how cloud deployments are treated if the agreement is ever certified. Our page on Oracle licensing in cloud environments sets out the counting rules.

Trap 5: Java outside the list

Java SE Universal Subscription is a separate product priced per employee, and it almost never sits inside the PULA product list. Its metric counts your workforce, so the cost follows headcount rather than the number of servers running Java.

If the account team implies Java is covered, that sentence belongs in the order form. Our note on contractors and the Java employee count explains who Oracle counts.

How much will PULA support cost over fifteen years?

Over fifteen years, PULA support costs more than three times the license fee, even with no uplift at all. Oracle's price list sets annual support at 22 percent of the net license fee, so cumulative support passes the fee itself within five years.

The PULA order form also adds a 3 to 5 percent yearly uplift by default. At the top of that range the support line doubles inside fifteen years, on an agreement designed never to end. The table below takes a hypothetical $8,000,000 PULA fee, so year one support is $1,760,000, under three uplift terms.

The gap between a zero cap and a 5 percent uplift is $11,578,272 over fifteen years, which is more than the license fee in this example. That is why the support clauses deserve more negotiating time than the discount.

Trap 6: support that never sunsets

A ULA's end date forces a negotiation in which the support base can be challenged, although Oracle usually carries the ULA support amount forward onto the certified licenses. A PULA never reaches that point, and an unlimited grant has no license count you can drop to shrink the bill.

Ask for a support cap and a defined recalculation basis, so any change to the support base follows a formula agreed at signature.

Trap 7: uplift and reset rights

The standard form applies a yearly uplift and reserves Oracle's right to reset support pricing. Cap the escalator in the order form, at zero if you can, and strike or narrow the reset right. A cap that appears only in a slide or email binds Oracle to nothing, as our guide to price hold and uplift cap clauses explains.

Trap 8: audit exposure when scope drifts

Deployment beyond the named scope triggers a compliance review, and an unlimited label makes teams stop checking what they install. A newly acquired subsidiary running the database, or a migration to a cloud the contract does not name, becomes an audit finding. Write the definition of drift, a cure period and the audit mechanics into the order form.

How do you build an exit into a perpetual agreement?

You write one in, because the standard PULA has none. Nothing in the form ever forces the agreement open again, and once you are committed Oracle has little reason to return to the table. Both exit defaults need a sentence at signature.

Trap 9: no certification day

Ask for a scheduled renegotiation window in the order form, for example at the end of year five and year ten, with the support basis and the three scope lists open for review. Pair it with the divestiture and M&A clause.

If Oracle refuses, put a price on the missing exit: compare the PULA with a ULA of the same scope, whose certification gives you that checkpoint for nothing. Our PULA exit strategies cover what to do once you already hold one.

Trap 10: cloud spend tied to the PULA

Oracle Cloud Infrastructure commitments tend to become entangled with the PULA relationship. Oracle Support Rewards return 33 percent of OCI Universal Credits consumption as credit against technology support invoices for customers with an unlimited license agreement, against 25 percent for everyone else, so cloud choices start to feed the support bill.

Keep the OCI order on separate paper, with its own term and no cross default to the PULA, so either can change without reopening the other. If the Support Rewards rate matters to your case, get written confirmation that your PULA qualifies at the higher rate, since Oracle's program terms refer to ULA customers.

What will Oracle's account team say about a PULA, and how should you reply?

The same lines come up in most PULA discussions. Each reply below turns a verbal assurance into a sentence in the order form.

• "Unlimited means you never have to count again." Reply: unlimited applies only to the listed products, entities and territories, so we will count whatever falls outside those lists, and we want the lists wider.
• "Java is covered under the agreement." Reply: then add Java SE Universal Subscription to the product list in the order form, or quote it separately in writing.
• "The cloud policy already allows AWS, Azure and Google Cloud." Reply: the policy sets counting rules, so name those providers inside the grant with a BYOL clause.
• "The uplift is standard for every customer." Reply: we are pricing a support stream with no end date, so the uplift term decides the value of this deal and has to be capped in writing.
• "Acquisitions are handled case by case." Reply: case by case means priced at the time of the deal, when we have the least room, so write the mechanism now.

Questions to ask Oracle before you sign

1. What is the three year ULA fee for the identical product list, quoted the same week?
2. How was the support base derived, in dollars, and what cap applies to future increases?
3. Which legal entities does the grant cover today, and how does a newly acquired company join?
4. What license position does a divested business leave with?
5. Which cloud providers sit inside the grant, and how are cloud deployments treated at any future certification?
6. Is Java SE in scope, and if not, what is the separate price?

What have we seen in Oracle PULA proposals from 2024 to 2026?

Across the 20 to 30 PULA proposals we modeled between 2024 and 2026, none of the findings turned on the license fee. In roughly nine of ten, a structured set of perpetual licenses with standard support beat the PULA over a ten year horizon once the support stream was priced in full.

All of them, 10 of 10, arrived with the ten defaults intact: SKU level product lists, single entity scope, no cloud clause, no renegotiation window and uncapped uplift. Three problems recurred most often.

• SKU lists. Product lists written as SKUs rather than families excluded the options and packs the customer later needed.
• No M&A mechanism. Entity clauses without acquisition or divestiture terms turned ordinary corporate activity into license events.
• Silence on public cloud. Every migration conversation became a fresh Oracle negotiation.

In every case the fix followed the same order: draft the lists and clauses first, then negotiate the price. More Oracle material sits in our Oracle knowledge hub.

When does a PULA earn its premium?

Only when scope is volatile and exit is not a priority, for example a fast growing Oracle footprint whose product and entity mix is hard to predict. Most companies lack that volatility, while the PULA's cost compounds regardless.

Price the PULA against the ULA it replaces with our PULA analysis, and test the unlimited need against the ULA guide.

What to do next

1. Before you reply to the proposal. Model the structured perpetual alternative over ten years. It is your strongest comparison even if you still choose the PULA.
2. Before discussing the number. Rewrite the three lists: product families instead of SKUs, parent plus controlled affiliates instead of one named entity, regions instead of countries.
3. Write the cloud and Java sentences yourself. A BYOL clause naming AWS, Azure and Google Cloud, and a separate written Java price, close the two gaps that surface most often after signature.
4. Cap the support stream. Get an escalator cap, at zero if possible, a limit on reset rights and a defined recalculation basis into the order form.
5. Put a checkpoint back. Add a scheduled renegotiation window and a divestiture and M&A clause, and keep any OCI commitment on separate paper.
6. Before signature. Walk the ten row table against the final order form and confirm every line is written. Our Oracle practice drafts and negotiates these terms with you.

Frequently asked questions