The Challenge
A mid-market private equity firm had four portfolio companies approaching exit within an 18-month window. A standard vendor spend analysis flagged Oracle as a material cost item across three of the four companies. When the deal team requested Oracle licence position documents from each CFO, none could produce one. Two companies had active Oracle support contracts they could not map to specific deployments. One company had an Oracle ULA it had entered three years earlier and had never certified.
Oracle licence liabilities are a recurring problem in M&A transactions for three structural reasons. First, Oracle licences are non-transferable without Oracle's written consent — a transaction that moves Oracle licences without proper assignment procedures constitutes a compliance breach, which Oracle has historically used as a basis for post-transaction audit or renegotiation. Second, Oracle's LMS team monitors M&A activity through Oracle partner disclosures and public filing analysis — enterprise Oracle audits following completed transactions are not uncommon. Third, Oracle licence gaps that are manageable as a going concern become material liabilities in the context of W&I insurance representations and transaction warranties.
The PE firm engaged us to assess all seven portfolio companies simultaneously. The mandate was clear: establish the Oracle licence position, quantify any compliance exposure, and remediate or commercially resolve each issue before transaction close.
Our Approach
- Rapid Estate Survey Across Seven Companies: For each portfolio company, we conducted a rapid Oracle estate survey: identify all Oracle products deployed, map them to CSI numbers and Order Forms, and establish the licence metric (Processor, Named User Plus, or Employee) applicable to each deployment. Across the seven companies, we found 23 separate CSI numbers and over 140 Order Forms of varying ages and formats. For most portfolio companies, this was the first time a consolidated Oracle licence position had ever been produced.
- VMware Compliance Gap Analysis: Four of the seven portfolio companies ran Oracle Database on VMware vSphere infrastructure. In all four cases, the virtualisation architecture was non-compliant with Oracle's licensing policy: Oracle requires all physical cores in a VMware cluster to be licensed for the Processor metric unless Oracle VM Manager is used for hard partitioning. None of the four companies was using Oracle VM Manager. The aggregate undisclosed VMware compliance gap across all four companies totalled $11.4M — the single largest source of Oracle liability in the portfolio. Remediation in each case involved physically separating Oracle workloads onto dedicated, correctly licensed server pools.
- Java SE Employee Metric Assessment: Two portfolio companies were running Java SE in production enterprise environments without a valid Oracle Java SE licence. Oracle's 2019 licensing change removed free commercial use rights. The Java SE Employee Metric charges per employee (or per user, for non-employee organisations) — not per server. In an enterprise environment, this means the licence requirement is based on the company's entire headcount, regardless of how many employees actually run Java applications. Combined Java SE Employee Metric exposure across both companies: $3.1M.
- ULA Certification Management: One portfolio company held an Oracle ULA covering Oracle Database EE, RAC, and Partitioning. The ULA had a certification deadline seven months away — well within the transaction timeline. An uncertified or poorly certified ULA is a significant risk in a transaction: it creates uncertainty about the licence quantities the acquiring entity will inherit, and Oracle has the right to audit the deployment at any point before certification. We led the ULA certification process for this company, documenting all in-scope deployments, validating Core Factor calculations, and submitting the certification to Oracle. The ULA certified cleanly at quantities that matched our pre-submission analysis.
- Transaction Structuring and Disclosure: For each of the seven companies, we produced an Oracle licence position document suitable for disclosure in the transaction data room. For the two companies with the largest exposures (combined $14M), we engaged Oracle directly on restructured commercial terms — converting the compliance exposure into a forward licence purchase arrangement. This eliminated the liability from the W&I insurance calculation and provided buyers with a clean, documented Oracle position on day one of ownership.
The Results
Key Takeaways
- Oracle licence liabilities are systematically underreported in PE portfolio company due diligence — no portfolio company in this engagement had a current Oracle licence position document
- VMware-based Oracle deployments are the single most common source of undisclosed Oracle compliance exposure in M&A contexts
- Java SE Employee Metric creates silent licence requirements based on company headcount — not IT infrastructure
- Oracle ULA certification requires active management — an uncertified ULA approaching deadline is a material transaction risk
- Oracle licence positions should be assessed and documented as standard PE portfolio management practice — not only at exit
"We had no idea Oracle licences could create transaction risk at this scale. The assessment identified issues that would have surfaced in every deal we were running — and would have been significantly more expensive to resolve post-close. This is now standard pre-exit due diligence for every portfolio company."— Managing Director, Mid-Market Private Equity Firm