Global Retailer Saves $9.6M by Unraveling Contractual Obligation from Oracle Partitioning Policy

Download Case Study PDF ↓

Executive Summary

When the Senior IT Manager at a leading global retailer was confronted with an aggressive Oracle audit threatening millions in unexpected license fees—fueled by ambiguous contract language and Oracle’s noncontractual Partitioning Policy—they knew they needed expert intervention. Turning to LicenseFortress, the retailer leveraged unparalleled legal expertise and a comprehensive audit defense strategy. LicenseFortress meticulously identified the retailer’s true contractual obligations, skillfully minimized Oracle’s overreach, and ultimately secured $9.6 million in savings. This decisive action delivered an extraordinary 27,329% ROI on a modest $35,000 project cost, reinforcing the value of specialized guidance in navigating complex licensing challenges.

Project Cost

Savings

ROI

Challenges

The stressors upon this retailer began with an Oracle audit of one of their subsidiaries. Their investigation into one subsidiary quickly bled into other arms of the company. This audit overreach by Oracle was complicated by the following:

  • A large number of subsidiaries and nonprofits operated by the retailer
  • Ambiguous language in Oracle contracts that had been in place and used by the retailer for more than twenty years
  • Legal issues emanating from Oracle’s assertion that the language ambiguity of the contracts fell in their favor and that the retailer owed them millions
  • License issues stemming from subsidiary use of licenses and license use across diverse regions of the globe

At a Glance

The Oracle Partitioning Policy was at the core of Oracle’s claims against the retailer. The intent of this policy is to ensure that Oracle customers are only Oracle software on machines licensed to use that software. However, in their attempt to ramp up revenue, Oracle uses the noncontractual language of their Partitioning Policy to push companies into paying for licenses they don’t need or use. This is the vendor attempting to use internal policy as a contractual obligation.

For example:

Under the partitioning policy, they do not recognize soft partitioning. If you have a five-node VMware cluster, Oracle runs on two of those nodes and has never been on the other (2) three nodes. Oracle wants to make you pay for all five nodes retroactively. If that VMware cluster can talk to another cluster with five other nodes, Oracle claims usage for all ten nodes. This is the case even if Oracle isn’t running on any but two active nodes. However, the Oracle Partitioning Policy says that the policy is “not for contractual purposes.” But they will try to leverage the policy against a customer and charge them without a contractual basis. Our global retail client faced these and other challenges surrounding the audit when dealing with Oracle.

Solution

To help our retail client deal with the noncontractual claims of the Oracle Partitioning Policy in the audit process, the LicenseFortress team leveraged the following internal resources through our audit defense:

  • We determined what devices and nodes throughout their vast organization were running Oracle.
  • We outlined for the client and Oracle what licenses and fees were contractually necessary.
  • We harnessed the legal power of our law firm to demonstrate to Oracle the overreach of their extra-contractual claims against the retailer.
  • We utilized our law firm’s extensive experience in dealing with Oracle to produce a “close letter” that prohibited Oracle from reaching back into history and starting up new audits that pre-date the current audit.
  • We saved our retail client in the ballpark of $9.6 million by reviewing their use of licenses and optimizing their license use.

Results