Oracle ULA subsidiary and M&A clauses.

Every Oracle ULA includes a section defining which entities are covered by the unlimited rights. That section is usually drafted by Oracle, and the default language quietly limits coverage in ways that surface only during an acquisition, a divestiture, or a certification event years later. The cost of missing this language at signature can reach into seven figures by term end. This piece walks through the clauses that matter, the default Oracle language to push back on, and the buyer side drafting that protects future flexibility.

1. Why the subsidiary clause matters.

The ULA grants unlimited rights to a defined set of entities. The standard Oracle draft names the signing entity and any subsidiary that the signing entity controls through majority ownership. That sounds reasonable in isolation. The problem appears when the corporate structure changes during the term. A new acquisition. A joint venture. A spin off. Each of these triggers a question Oracle is happy to answer in its favour: is this entity covered by the unlimited rights, or does it need its own licences.

The default answer in most Oracle ULA templates is restrictive. New subsidiaries acquired during the term may not automatically inherit the unlimited rights. Joint ventures may sit outside coverage entirely. Spin offs may lose their entitlements at the moment of separation. Each of these gaps becomes a compliance exposure that Oracle can convert into a new sale or an audit finding. See our ULA deal page for the broader contract structure.

2. The standard Oracle subsidiary definition.

Oracle's template subsidiary clause usually reads something like this. A subsidiary is any entity in which the signing entity owns more than 50 percent of the voting equity, directly or indirectly. That entity is covered by the ULA for as long as the ownership threshold is maintained. The moment ownership drops below 50 percent, the subsidiary loses coverage.

This drafting creates several silent risks. A joint venture at 50 percent or less is excluded. A minority investment that operates Oracle Database is excluded. An entity that the parent controls operationally but not equitably is excluded. The clause is written for clean corporate structures and breaks down in any organisation with complex ownership.

3. The acquisition coverage question.

If your organisation has an active M&A pipeline, the acquisition coverage clause is the single most valuable piece of negotiation leverage in the ULA. Oracle will normally argue that any new acquisition is automatically covered as long as the parent ownership requirement is met. That sounds favourable until the acquired company is itself running an Oracle deployment that, when added to the parent footprint, dramatically expands the certification baseline.

Oracle does not want acquisitions to inherit ULA rights for free. Their preferred language carves out acquired entities above a certain revenue or deployment threshold, requiring a separate true up purchase before coverage extends. Buyer side drafting reverses this default. Acquisitions inside the term automatically inherit coverage, with no incremental fee, and the only requirement is notice to Oracle. See our renewal negotiation pillar for how this language plays through subsequent term decisions.

4. The divestiture clause.

The mirror image of the acquisition question is divestiture. When the buyer sells a business unit during the ULA term, what happens to the Oracle entitlements that supported that unit. The default Oracle position is that all entitlements remain with the signing entity. The divested unit walks away with no licences, no support, and immediate exposure.

This is unworkable in practice. Buyers selling a business unit almost always need to provide the buyer of that unit with continuing Oracle support for at least a transition period. The buyer side drafting either grants the divested entity perpetual licences carved from the ULA at separation, or provides a defined transition services arrangement that protects continued Oracle use for 12 to 24 months post separation.

5. The certification scope question.

When the ULA term ends and the buyer certifies out, the certification scope is determined by the subsidiary clause as it stood at term end. Every entity covered by the unlimited rights at termination contributes its deployment to the certified count. Entities not covered are excluded from the count.

This becomes a strategic question in the final months of the term. If a recently acquired subsidiary is covered, the certified perpetual licence quantity includes its deployments. If the same subsidiary is not covered, its deployments are an audit exposure and a separate licence requirement. The difference can be millions of dollars in licence value. See our renewal versus certification decision tree for the full framework.

6. What disciplined buyers ask for.

• Broad subsidiary definition. Coverage of any entity controlled directly or indirectly by the parent, including joint ventures and minority controlled entities.
• Automatic acquisition coverage. New acquisitions inside the term automatically inherit unlimited rights with no incremental fee, subject only to notice.
• Acquisition true up cap. If Oracle insists on a true up, the fee is capped at a defined percentage of the ULA price, not open ended.
• Divestiture entitlement carve out. Divested business units receive perpetual licences for their current deployment at the moment of separation.
• Transition services rights. The buyer can provide Oracle support to the divested entity for 12 to 24 months post separation.
• Certification scope freeze. The subsidiary list for certification is the list as of 90 days before term end, preventing late stage Oracle gamesmanship.
• Notice rather than consent. Coverage extensions require notice to Oracle, not Oracle approval.

7. Common Oracle counterproposals.

Oracle will not accept buyer side language without negotiation. The most common counterproposals to expect are these. First, Oracle will limit acquisition coverage to entities below a defined revenue or deployment threshold. Push back on this and ask for the cap to apply only above a meaningful number, such as $1 billion in revenue or 1,000 named users. Second, Oracle will require notice and approval rather than notice only. The buyer side response is to convert approval into a defined notice period after which coverage extends by default. Third, Oracle will tie divestiture treatment to a true up payment. The buyer response is to require the carve out to be free of charge for any business unit that was covered for the full ULA term.

For deeper context on Oracle's commercial behaviour during these negotiations see our Oracle sales playbook and the discussion of pressure tactics in our ULA negotiation service page. The product context for Oracle Database deployments inside ULAs sits on our Oracle Database product page. The complete buyer side framework is documented in the ULA Exit Framework white paper.

8. When to renegotiate the subsidiary clause.

The subsidiary clause is normally negotiated at ULA signature. It can be reopened at three other points. First, during a renewal cycle, when the buyer is preparing to sign another term and has fresh leverage. Second, during a major acquisition, when the buyer is bringing significant new Oracle scope into the perimeter and Oracle has incentive to formalise treatment. Third, during a contract amendment for an unrelated reason, where the subsidiary language can be modernised as part of the same paperwork.

Buyers who treat the subsidiary clause as a negotiable lever rather than a fixed Oracle term consistently end the term with broader coverage, cleaner certifications, and lower true up exposure. The work happens at the contract drafting stage, not at the audit stage, and that distinction is everything.