Oracle has been in the process of moving its complex installed base to the cloud for some time now, changing from on-premises perpetual software to a subscription-based model. Those at the helm of SPVM, who may have recently wrestled with the intricate licensing rules and metrics, as well as the ever-present danger of more compliance audits, must now adapt to a totally new cloud environment.
Putting too much trust in Oracle’s impartiality, even when it’s your strategic partner, might not always be smart when transitioning from on-premises to Oracle Cloud. For example, while the risks of unused software in on-premises systems are well-known, these same risks continue in the cloud as Oracle has a knack for overselling. The complexity of contracts remains, and getting significant concessions from Oracle hasn’t gotten any easier.
For clients who opt to stick with Oracle’s on-premises software, the twisted nature of licensing terms, metrics, and functionality can quickly lead to non-compliance issues.
This article uncovers risks that present and future Oracle clients might face. It highlights the top five most common traps to watch out for, grouped into two key areas: compliance and pricing.
Recognizing and dealing with these risks when the opportunity arises is vital.
Java licensing changes
As of 23 January 2023, Oracle shook up its Java licensing structure. Moving away from the Named User Plus and Processor models, it transitioned to a single Employee metric. Now, organizations needing a chargeable Java version must license every employee, agent, and contractor, regardless of their direct Java usage. This is relevant for Oracle Java SE 8 (from updates 8u211 or 8u212 onwards) and all versions of Oracle JDK 11 LTS.
These mentioned versions fall under the My Oracle Support license or the Oracle Technology Network (OTN) License Agreement for Oracle Java SE. This limits its use to personal, development, and certain Oracle-related purposes.
Considering that the majority of Java applications run on Java SE 8 or JDK 11, this might be confusing for many users.
For a detailed understanding and a list of Java distributions that don’t require a Java SE subscription, check out the Oracle Java SE Licensing FAQ.
If you’re using Oracle JDK (including both JRE and JDK), you’re likely required to get an Oracle Java SE subscription. However, Gartner’s feedback suggests that many organizations might be unaware of these changes, possibly leading to unexpected costs. Furthermore, Oracle’s specific Java licensing team is actively contacting clients about their Java SE usage and is quick to highlight any noncompliance.
Organizations should be ready for Oracle’s attempts to collect data on Java deployments, possibly seeking retroactive fees from the 2019 licensing shift, or offering to waive these in return for longer subscription commitments.
Recommended steps
- Procuring a Java SE subscription
- Transitioning to the complimentary Oracle JDK 17
- Updating to the latest Open JDK version
- Considering third-party Java solutions
If you decide on an SE subscription, make sure to familiarize yourself with the Oracle Partitioning Policy and refer to the subsequent Virtualization section for insights.
Bonus: Be prepared for possible outreach from Oracle’s Java licensing division. When engaging, confirm what data you’re legally required to share with Oracle – they might not have rights to all deployment details.
Archive note: the archived page ends here. The remaining four pitfalls and the Virtualization section it refers to are not present on the archived page.