5 Common Risks to Manage with Oracle Java Audits
With more than 17 years of experience working with clients on their Oracle relationships, Software Licensing Consultants has unique insights into risks that are often overlooked and can lead to paying more in Oracle audits. If you’re going through a Java audit, here are five common risks you should be aware of:
Go deeper into these five risks and other common Oracle audit issues, and get helpful tips from our pros by watching our recent webinar, “Oracle Java Audits: Understand Your Risks Before You Get a Notice.” Please fill out the form below, then enjoy the webinar.
#1 – Licensing Oracle Java in VMware
Clients often don’t understand this product is licensed by Oracle just like a database and is determined by the number of processor cores across the entire VM environment. It’s a high risk that can bring a high price tag during an audit.
#2 – Using Oracle Java with third-party apps
Clients often upgrade applications without involving IT, which can include going from on-premise to the cloud or other scenarios where Java is a requirement, but the license is not provided by the application vendor. This is a hidden risk during an audit process that could lead to back-support fees.
#3 – End users downloading from Oracle.com or Java.com.
Most audits start with Oracle approaching you with a list of people who have downloaded Java updates, saying something like, “We see you’ve downloaded these updates and we need to talk about this.” In some recent cases, we’ve even seen Oracle reach out to the end-users who downloaded the update to get information that was not accurate, putting the organization in a bad position.
#4 – Licensing too much Java.
We see many cases where clients didn’t know what to do, so they just bought Java. This often creates over-licensing where Oracle now has the bar set for a new minimum. Scaling back a contract with Oracle is much harder than increasing it.
#5 – Not licensing Java 6 or 7 (or 8) as required.
Clients often don’t look back and see they had older versions of Java licensed before April 2019, the date of the first release that required a license. Now they have downloaded patches for those versions since the beginning of 2019 that require licensing, and are now at risk of back-support fees.
Artboard 2
Go deeper into these five risks and other common Oracle audit issues, and get helpful tips from our pros by watching our recent webinar, “Oracle Java Audits: Understand Your Risks Before You Get a Notice.” Please fill out the form below, then enjoy the webinar.
