X

Oracle wants more than the $306 million promised in SAP lawsuit

The company is appealing a court decision that allowed SAP to agree to pay millions -- not more than a billion -- in damages in a copyright infringement case.

Lance Whitney Contributing Writer
Lance Whitney is a freelance technology writer and trainer and a former IT professional. He's written for Time, CNET, PCMag, and several other publications. He's the author of two tech books--one on Windows and another on LinkedIn.
Lance Whitney
2 min read

Oracle is due to receive a hefty amount in legal damages from SAP, but the database giant wants more.

In early August, SAP agreed to pay Oracle $306 million following a trial that found SAP guilty of copyright infringement. The jury verdict reached in 2010 determined that Oracle should receive $1.3 billion in damages.

But last September, U.S. District Judge Phyllis Hamilton deemed that amount excessive and gave Oracle a choice of accepting $272 million in damages or requesting a new trial.

The amount ballooned to the$306 million agreed upon last month. At the time, Oracle general counsel Dorian Daley did note that SAP would actually end up paying "a minimum of $426 million, including attorneys' fees."

But the appeal launched by Oracle means the database company may now be looking for millions more in damages, according to Reuters.

An SAP spokesman sent the following statement to CNET:

SAP is disappointed that Oracle continues to prolong the case. We agreed to reasonable terms in this case, as we believe it's gone on long enough. We remain determined to work through the legal process to bring this case to resolution.

CNET also contacted Oracle for comment and will update the story if we receive more information.

The case harkens back to 2007 when Oracle sued SAP over accusations that SAP's TomorrowNow subsidiary wrongfully downloaded millions of Oracle files and documents. SAP admitted the violation from the start, but the two companies have been battling over the amount of damages owed to Oracle.

Updated 9/5 4:30 a.m. PT with response from SAP.