Between the Lines

Larry Dignan, Andrew Nusca and Rachel King

SAP: Oracle damages 'grossly excessive'; Oracle wants more dough if new trial

By | February 24, 2011, 12:01pm PST

SAP has filed documents asking a U.S. District Court in Oakland, Calif. to reduce the $1.3 billion jury award to Oracle over the TomorrowNow intellectual property infringement lawsuit. Oracle scoffed at SAP’s request for a new trial and said if it weren’t for court errors damages would be more like $1.8 billion.

The documents, filed Wednesday, argue that Oracle’s jury award was based on damages for copyright infringement “in the form of a hypothetical license.” SAP is arguing that Oracle didn’t establish that it would have licensed the copyrighted works at the center of the TomorrowNow trial.

Bottom line (for SAP at least): Damages should be between $28 million (SAP’s assessment) and $408.7 million (Oracle’s expert).

According to SAP:

At trial, Oracle did not contend that it is entitled to a hypothetical license because it lost the opportunity to license the works to third parties for the same use as was made by TomorrowNow. Thus, to establish its entitlement to recover hypothetical license damages, Oracle was required to show that the parties would have agreed to license for the use of the copyrighted works at issue. But Oracle offered none of the evidence on which plaintiffs typically rely to prove that the parties would have entered into such a license, such as past licensing history between the parties or plaintiffs’ previous licensing practices.

To SAP, Oracle’s $1.3 billion award is a “miscarriage of justice” and may deserve a new trial.

Oracle in its response obviously disagrees. Oracle’s argument in a motion, via AllThingsD, go like this:

  • There’s no need for a new trial.
  • Damages are supported.
  • If a new trial is necessary, Oracle will seek an additional $500 million in damages due to errors during the last trial. Oracle argues that the court erred in excluding projections of Oracle’s upsell and cross-sell revenue from the PeopleSoft and Siebel acquisitions.

Bottom line for Oracle: SAP should pay $1.8 billion in damages.

Related:

Kick off your day with ZDNet's daily e-mail newsletter. It's the freshest tech news and opinion, served hot. Get it.

Topics

Larry Dignan is Editor in Chief of ZDNet and SmartPlanet as well as Editorial Director of ZDNet's sister site TechRepublic.

Disclosure

Larry Dignan

Larry Dignan has nothing to disclose. He doesn’t hold investments in the technology companies he covers.

Biography

Larry Dignan

Larry Dignan is Editor in Chief of ZDNet and SmartPlanet as well as Editorial Director of ZDNet's sister site TechRepublic. He was most recently Executive Editor of News and Blogs at ZDNet. Prior to that he was executive news editor at eWeek and news editor at Baseline. He also served as the East Coast news editor and finance editor at CNET News.com. Larry has covered the technology and financial services industry since 1995, publishing articles in WallStreetWeek.com, Inter@ctive Week, The New York Times, and Financial Planning magazine. He's a graduate of the Columbia School of Journalism and the University of Delaware.

For daily updates, follow Larry on Twitter.

1
Comments

Join the conversation!

This is pretty sad. Oracle does not realize that database is a commodity and that SAP customers invested more in SAP implementation than database implementation. For SAP, this is a problem as customers demand lower prices on its products because most sit on Oracle and thus are experiencing the risk first hand such as the ~1yr window to upgrade from 10g to 11g. For many SAP customers with 100 or so dev/qa/sandbox/pre-production/production/DR systems it is a big deal. Spending very limited resources on upgrading Oracle vs. bringing value to the company makes IT look bad, so IT throws SAP under the bus. The first victim is BW. With BEx getting RIP sign and replacement by BO products, many SAP customers are looking at alternatives and finding them rather quickly. BW is not a prime time ready product after all these years and killing BEx is a good "excuse" to ditch BW. This is just the beginning of things to come to SAP on customer defection front.

Join the conversation!

Formatting +
BB Codes - Note: HTML is not supported in forums
  • [b] Bold [/b]
  • [i] Italic [/i]
  • [u] Underline [/u]
  • [s] Strikethrough [/s]
  • [q] "Quote" [/q]
  • [ol][*] 1. Ordered List [/ol]
  • [ul][*] · Unordered List [/ul]
  • [pre] Preformat [/pre]
  • [quote] "Blockquote" [/quote]
ie8 fix

The best of ZDNet, delivered

ZDNet Newsletters

Get the best of ZDNet delivered straight to your inbox

Facebook Activity

White Papers, Webcasts, & Resources
ie8 fix