Oracle may be next in EU software licensing hot seat following SAP deal

The European Commission has begun seeking third-party views on Oracle's software licensing practices, potentially laying the groundwork for a formal antitrust investigation, though no formal case has been opened. Scrutiny centers on licensing models including Oracle Java SE's employee-based subscription, which Gartner estimated can cost 2-5x more than legacy licensing, and Oracle's Unlimited License Agreements. The review follows the EC's SAP case, which ended in July with binding commitments to remove reinstatement fees and cut back-maintenance charges.

Analysis

The relevant exposure is not a one-time fine but the durability of Oracle's high-margin maintenance, Java subscription, and audit-driven licensing yield. A formal EC process would likely encourage European procurement teams to defer renewals, challenge employee-count assumptions, and seek third-party support or OpenJDK alternatives before any ruling; that can pressure bookings and renewal pricing within 1-3 quarters. The most sensitive metric is not consolidated revenue but the support/maintenance growth and operating-margin trajectory that underpins ORCL's valuation premium during its infrastructure buildout.

SAP's remedy framework creates a practical regulatory template: behavioral commitments can lower switching costs without forcing a breakup or producing a large immediate P&L charge. That makes a near-term short on ORCL less attractive unless evidence emerges of a formal Statement of Objections, broad customer complaints, or disclosed changes in Java renewal terms. The second-order effect is that CIOs may separate Java/runtime decisions from database and cloud purchasing, weakening Oracle's account-control advantage and benefiting open-source Java distributions, IBM/Red Hat ecosystem vendors, and third-party support specialists.

The contrarian view is that this is initially a procurement and multiple-risk issue, not necessarily an earnings event: Oracle's cloud backlog and AI infrastructure demand can overwhelm any modest European licensing concession. Conversely, consensus may underprice the reputational spillover if customers use regulatory scrutiny as leverage across Oracle Database, ULA renewals, and cloud credits; that would show up first in lower support price realization rather than reported churn. A decisive falsifier is sustained support revenue growth and operating-margin expansion through the next two earnings cycles despite unchanged or tighter European contract terms.

Key Decisions for Investors

• Do not initiate a directional ORCL short on preliminary scrutiny alone. Set an event-driven alert for formal EC proceedings or a disclosed licensing-policy revision; if either occurs, consider a 1-3 month ORCL underweight versus IGV, targeting 5-8% relative downside, with a 4% relative stop if cloud backlog or support growth accelerates.
• Prefer a relative-risk hedge over outright SAP weakness: long SAP / short ORCL in equal beta for 3-6 months only if Oracle's next earnings release shows support or applications renewal deceleration. The trade expresses greater regulatory uncertainty at ORCL while avoiding broad enterprise-software multiple risk; exit if ORCL support growth remains resilient and SAP's cloud backlog weakens.
• Monitor RMNI and private/open-source Java vendors as second-order beneficiaries, but do not add RMNI without confirming customer-demand acceleration and litigation/liquidity conditions. Its historical Oracle legal exposure makes it an alert candidate rather than a clean long.
• For existing ORCL longs, require quarterly monitoring of support revenue growth, remaining-performance-obligation growth, and management commentary on European Java/ULA renewals. Reduce exposure if support growth misses guidance by more than 200 bps or management acknowledges broader pricing concessions; retain if cloud infrastructure growth offsets any licensing softness.