Oracle's SAP Lawsuit: The ISV Protests Too Much, Methinks

Oracle's SAP lawsuit accuses SAP of "corporate theft on a grand scale." So what was stolen? Support material freely available to any of thousands of Oracle customers. These are the super-secret corporate espionage documents that Oracle is screaming about?

The Oracle lawsuit against SAP, although fascinating in its detailed tracking of who took what and when, is so much pure Oracle. This would be like Microsoft suing a small software company and accusing them?with great indignation?of not treating their partners with courtesy and respect.

Based on the full text of the accusation portion of the lawsuit, Oracle certainly seems to make a rock-solid case that tech support documents were downloaded by those without direct authorization. But we need to distinguish between someone hacking their way into a private R&D database and stealing under-development sourcecode and someone looking at documents available t any and all customers, along the lines of?according to Oracle's own lawsuit filing?"program updates, software updates, bug fixes, patches, custom solutions, and instructional documents across the entire PeopleSoft and JDE family of software products."

Who is accused of having done these dastardly downloads of instructional documents? Yes, it was SAP, but specifically the TomorrowNow group, which provides third-party support for PeopleSoft and JD Edwards ERP applications, both of which are now owned by Oracle.

The documents in question would likely help this tech support unit better understand Oracle products and thereby be able to better help Oracle's customers. It's hard to see how this is injuring Oracle customers.

Assuming the lawsuit's representations are accurate?which is assuming quite a lot?it seems that one likely scenario of how this happened is that customers migrating away from Oracle and to SAP wanted SAP?and specifically TomorrowNow?to help make the transition easy. In an attempt to help make that happen, they simply gave the SAP people their passwords to the Oracle database.

This would be likely be seen as more of a convenience than some earth-shattering act of corporate espionage, akin to an E-Commerce company giving an outside programmer login credentials to its Web host, so that the programmer could access whatever was needed.

Let's be fair here. Were the documents proprietary and legally protected? No doubt they were. Did some people at SAP get carried away and do more than was necessary to help those specific customers? If the accusations in the lawsuit are correct, yes, it seems likely they did.

But even examining this case solely from the Oracle perspective based only on the claims that Oracle is making, it's hard to see this as some monumental case that threatens to cripple Oracle.

Indeed, the claim that the people accessing the data didn't even try to mask their IP addresses?and it stands to reason than many SAP people certainly would have had the knowledge and the wherewithal to do so?strongly suggests that the downloaders saw little wrong with what they were doing. That's not the action of a Megabyte Mata Hari, trying to steal code that they'll sell for millions on the black market. That sounds more like a tech support professional who sees a lot of tech support documents and files that he might have access to later on and should download now, just in case it will help a customer at some later date.

Please don't get me wrong. SAP and Oracle are both very aggressive rivals and I wouldn't it past either company to engage in true corporate espionage. But this doesn't feel like that. It feels like Oracle finding a technicality that it can say "Gotcha!" with.