One of Oracle’s signature moves to gain leverage on their customers is changing the URL, or embedded URL in your contract. Oracle will use links – they they don’t think you’ll read – to take an opportunity to put you at risk, lower the quality of service, or just reduce Oracle’s liability.
What’s hiding in your Oracle contract URLs?
Oracle is notorious for their unclear and incredibly complex contracts. A purchase of Oracle database contains literally hundreds of pages of terms and conditions when you look at your contracts and the URLs contained in those contracts. It’s often the URLs where Oracle hides their biggest “gotchas.” Oracle repricing policies around their technical support is a great example of this strategy.
Oracle uses non-contractual ‘policies’ to extract revenue
Most Oracle customers have a contract that states the actual contract, and URLs embedded in that contract constitute the arrangement of the parties. According to the Entire Agreement clause in the Oracle contract itself, nothing else should really apply. If it’s not in the contract, it doesn’t bind the parties. Well, that’s how it should work, but the reality is different.
Oracle will often use non-contractual “policies” to extract revenue from their customers or restrict their customers’ freedom to use competitive products.
It appears that Oracle is now taking this approach one step further.
Technical support portal terms of service
In 2017, Oracle made a change to their terms of service policies related to usage of their technical support portal. Did you even know there were terms of services for that portal? Have you ever read them? Of course you haven’t. Not only did Oracle change their policies, but Oracle still has not made any type of announcement to their customers about the change (at least I could not find any announcement). Do you know how we found out about the change? We found out because Oracle started sending letters to their customers who were “violating” the terms.
Let’s give you a little more detail where these policies sit:
- You have a contract with Oracle that you signed. In that contract are a bunch of URLs pointing to different Oracle policies. (Now remember, these direct ULAs are usually incorporated into your Oracle agreement by the entire agreement clause you and Oracle signed up to.)
- One of these URLs is Oracle’s Technical Support Policies.
- Oracle Technical Support Policies have URLs in them as well. One URL points to the Oracle Support Portal where you log into Oracle support and use the service you are paying for.
- The Oracle Support Portal has a series of links on it. One of these links is their Terms of Service policies. It’s in this link that Oracle made a change.
In summary, Oracle changed text in a URL, contained in a URL, contained in a URL, contained in your contract. Oracle used that as an opportunity to send letters to customers who they say are violating that link.
So what did Oracle change?
They made two changes:
- First, Oracle is limiting the number of downloads you can make each day when you have Oracle support. You were able to make unlimited downloads, and now Oracle is capping it at 500. In typical Oracle fashion, they did not actually prevent you from downloading more than 500 documents/patches in a day. Rather, the Oracle system allows you to go out of compliance and then you are hit with the nasty-gram. Sound familiar?
- The second change Oracle made is that if you download a patch from Oracle you must apply it within 90 days. Previously, you could apply it whenever you liked. We have not yet seen Oracle audit their clients and use this as a non-compliance finding. But knowing Oracle the way we do, I wouldn’t be surprised if Oracle LMS did just that. Oracle knows when you downloaded the patch. Running Oracle LMS scripts could tell Oracle when you applied that patch. After that, it’s just a math problem.
What are the issues around this move by Oracle?
It’s two years later and what’s happened because of this policy? Honestly, the only thing we see is that Oracle has created a lot of anxiety for their customers. Oracle customers continue to use the Oracle support portal as they were doing before. We have not seen Oracle sue any customers over violations of this “policy” and we have not witnessed any change of behavior by Oracle customers. It looks as if Oracle put out this policy to try and prevent their clients from moving off of Oracle support and on to third-party support with Rimini Street. I don’t think it’s worked like Oracle anticipated. Their customers continue to move to Rimini.
Once again, Oracle made a change to benefit Oracle and to the detriment of their clients. This time Oracle customers seem to ignoring Oracle’s move. They’ve taken control!