'We had to educate Oracle about our contract,' CIO says after Big Red audit
11–20 of 152 posts
Re: 'We had to educate Oracle about our contract,' CIO says after Big Red audit
#12"a specialist advisory company helping clients deal with Oracle licenses" I would (naively, I know) imagine that if you need to hire a third party to help you sort out your licenses with a vendor, you would do whatever it takes to get rid of that vendor. It's almost as if Oracle wants their customers to ditch them the first chance they get.
Re: 'We had to educate Oracle about our contract,' CIO says after Big Red audit
#13> Earlier last year, it made changes to the Oracle Java SE subscription model, basing it on a per-employee metric many said would increase costs for users. Would running Java under Corretto 21 change this?
Yes, all of this Oracle Java licensing drama only applies if you're using the Oracle JDK. The vast majority of people can just use a JDK from any of the other vendors and tell Oracle to pound sand. Even if you do need paid support, you should pay Azul instead of Oracle, just out of principle.
Re: 'We had to educate Oracle about our contract,' CIO says after Big Red audit
#14Re: 'We had to educate Oracle about our contract,' CIO says after Big Red audit
#15Oracle's favourite phrase seems to be "You're out of compliance", and their only solution is for you to pay more.
And if they can’t say that (ie when it’s not true), they will intimate that you might be out of compliance, and hope you’re worried enough to just pay more anyway.
Re: 'We had to educate Oracle about our contract,' CIO says after Big Red audit
#16"a specialist advisory company helping clients deal with Oracle licenses" I would (naively, I know) imagine that if you need to hire a third party to help you sort out your licenses with a vendor, you would do whatever it takes to get rid of that vendor. It's almost as if Oracle wants their customers to ditch them the first chance they get.
Once you're using an Oracle database, you are probably using proprietary Oracle features, SQL syntax, client libraries, etc. The first chance you get might be a while. I once worked on a project porting an app from Oracle to another commercial DB. When Oracle is deeply embedded in your applications, it's easier said than done.
Re: 'We had to educate Oracle about our contract,' CIO says after Big Red audit
#17Nothing their database does can't be done with a different database. Even paying for a proprietary database can be done with a different party than Oracle. Do not, I repeat, do not do business with Oracle under any circumstances.
If you are already an Oracle customer and you have the opportunity to drop them from your stack. Do not hesitate, Do not pause, Immediately take that opportunity. There is no downside only upside in not doing business with Oracle.
Re: 'We had to educate Oracle about our contract,' CIO says after Big Red audit
#18Short of imagining some long ongoing legal action, is there really any incentive for Oracle to be truthful about anything?
It seems like this entire auditing system is just a wildcard as far as time / money sunk into the auditing process and Oracle can deploy it at will...
Re: 'We had to educate Oracle about our contract,' CIO says after Big Red audit
#19Re: 'We had to educate Oracle about our contract,' CIO says after Big Red audit
#20"a specialist advisory company helping clients deal with Oracle licenses" I would (naively, I know) imagine that if you need to hire a third party to help you sort out your licenses with a vendor, you would do whatever it takes to get rid of that vendor. It's almost as if Oracle wants their customers to ditch them the first chance they get.
https://aws.amazon.com/solutions/case-studies/amazon-databas...
https://aws.amazon.com/blogs/aws/migration-complete-amazons-... https://news.ycombinator.com/item?id=21258127 (Edit: 2019)