This month brings with it the tenth anniversary of our resolving and settling the landmark Mars v. Oracle lawsuit, the first – and to this date only – publicly filed complaint by a licensee targeting Oracle’s deeply unpopular licensing and auditing tactics. We served as the lead litigation counsel for Mars in this fight against Oracle, simultaneously safeguarding our client’s interests while drawing much-needed attention to Oracle’s audit script. The impact of Mars v. Oracle on the ERP sector was – and continues to be – seismic.
The public awareness raised by Mars v. Oracle was as immediate as it was profound. IT professionals at businesses both global and local finally understood that they were not alone in their struggle to protect their company against Oracle’s predatory practices. In many ways, the seeds of Beeman & Muchmore’s mission were planted back then – our quest to educate and protect our clients and colleagues regarding the subtly shifting and nuanced pressures attendant to licensing ERP technologies. A decade later, what we started is now the full-time job of Beeman & Muchmore.
As the ten-year anniversary of the date on which the Mars v. Oracle matter was resolved, we cannot help but look to the future and ask: Why does Mars v. Oracle still matter? In sum, though the litigation was settled in the early stages, Mars v. Oracle continues to cast a steady light on Oracle’s ongoing licensing and auditing practices.
By drawing public attention to Oracle’s deeply unpopular audit script, we had provided a lifeline to scores of beleaguered licensees. Our phones began ringing off the hook. The callers had also found themselves in Mars’ untenable position yet lacked the resources to stand up to what they strongly believed were Oracle’s abusive auditing and licensing tactics.
Mars v. Oracle drew back the curtain and revealed Oracle’s underground economy of attacking its licensees to upsell its fledgling product offerings and otherwise materialize new revenue streams. To this day, Mars v. Oracle continues to be an important reference point, eagerly acknowledged by many of our clients.
In the ten years that have passed since we filed Mars v. Oracle, we have seen many changes to Oracle’s auditing and licensing script while also observing many elements of its script remaining unchanged. We hope to continue to offer insights that can only be provided by the litigation team which challenged Oracle in the Mars v. Oracle matter – a litigation team which later became Beeman & Muchmore.
It is not hard to look at Oracle’s current Java licensing push as a natural extension of the playbook that was first exposed through Mars v. Oracle. As we have stated before, if you have not been approached yet by Oracle regarding Java, you will be. And, even if you believe you have resolved your Java license with Oracle, be extra wary. We are seeing Oracle return to certain licensees for round two of Java licensing. Your vulnerabilities may change, but Oracle’s aggression remains.
Published on December 3, 2025
Software licensors are known for vague contracts—they’ve made a business of it.
Read the latest industry news.