Navigating Oracle Java Rights After Support Ends
When organisations move away from Oracle support for products like Oracle E-Business Suite (EBS), Java licensing quickly becomes a complex and often misunderstood issue. This blog breaks down what actually happens to your Java rights—and what practical paths are available to stay compliant while managing costs and risks.
Key takeaway: You don’t lose the right to use Java—but you lose the right to update it.
The “Frozen Java” Reality
If your organisation still holds a valid Oracle EBS licence, you can continue using Java as part of that system. However, as soon as Oracle support ends:
- You can no longer download Java updates, patches, or upgrades
- You lose access to Oracle support tools and non-public binaries
- Your Java environment becomes effectively locked to the version you were using at the time support ended
This creates what many call a “frozen version” state—perfectly legal, but operationally restrictive.
What You Can (and Can’t) Do
Even without support, organisations are still entitled to:
- ✅ Run EBS using their existing Java version
- ✅ Use Java on servers and desktops strictly for EBS functionality
But there are strict limitations:
- ❌ Java must only be used for EBS—not for general-purpose computing
- ❌ No updates or new installations are allowed
- ❌ Expanding usage beyond the original scope risks non-compliance
In short, your rights remain—but they are tightly constrained.
The Risks You’re Taking
Operating on an unsupported Java version introduces three key risks:
- Security Risk: Without patches, known vulnerabilities remain exposed
- Licensing Risk: Downloading updates outside entitlement may violate Oracle licensing
- Audit Risk: Misuse of Java beyond its restricted scope could trigger compliance issues
For many organisations, the security risk alone becomes a major concern—especially for environments still running older Java versions like Java 8 or 11.
Your Strategic Options
The report outlines several common approaches organisations take post-support:
1. Do Nothing (High Risk)
Continue using the frozen Java environment. This is legally viable but exposes the business to increasing security and operational risks over time.
2. Move to OpenJDK
A popular path is replacing Oracle Java—especially on desktops—with OpenJDK distributions (such as Azul Zulu or Eclipse Temurin).
Benefits include:
- No Oracle licensing costs
- Full commercial usage rights
- Reduced audit exposure
The trade-off is that Oracle does not officially certify OpenJDK for EBS, which may complicate support scenarios. Also be aware of additional risks of using open-source software, as AI-driven attacks on public code sets are increasing.
3. Adopt Oracle’s Free NFTC Model
Oracle’s newer “No-Fee Terms and Conditions” (NFTC) model allows temporary free use of newer Java versions—but only within defined time windows.
4. Purchase a Java Subscription
For organisations prioritising stability and support, Oracle’s Java SE Universal Subscription provides ongoing updates and support.
However, this comes at a cost:
- Pricing is based on total employee count, not actual Java users
- Typical pricing ranges from $5 to $15 USD per employee, per month
That means even limited Java usage can result in significant enterprise-wide costs.
Cost Reality Check
For a mid-sized organisation of around 1,000 employees, the report estimates:
💰 ~$180,000 USD per year (~$270,000 AUD) at list price
Real-world negotiated costs may range lower, but still represent a significant increase compared to legacy licensing models. This shift to employee-based pricing is often the tipping point that drives organisations toward alternatives like OpenJDK.
A Practical Hybrid Approach
Many organisations are settling on a balanced strategy:
- Keep Oracle Java (frozen) on EBS servers where required
- Replace desktop Java with alternatives like Azul Zulu
- Tighten controls to prevent unauthorised updates or usage
This approach reduces licensing exposure while maintaining operational continuity.
Governance and Compliance Matter
Remaining compliant isn’t just about technology—it’s about documentation and control.
Key practices include:
- Declaring and documenting your frozen Java version
- Disabling auto-updates across environments
- Restricting usage strictly to EBS
- Maintaining audit-ready evidence
⚠️ Common mistakes - such as reinstalling Java during desktop refreshes or allowing auto-updates—can quickly invalidate your compliance position.
Looking Ahead
Running a “frozen” Java environment is rarely a long-term strategy. Most organisations eventually:
- Centralise EBS access (e.g., via virtual desktops)
- Replace Oracle Java completely
- Or migrate away from EBS altogether
The key is to treat the current setup as a transition state, not a permanent solution.
Final Thought
Oracle’s licensing model doesn’t explicitly say “your Java version is frozen”—but in practice, that’s exactly what happens. Understanding this nuance is critical.
With the right mix of strategy, governance, and tooling, organisations can remain compliant, manage risks, and avoid unexpected costs—even after leaving Oracle support.
Targetbase has extensive experience helping clients navigate these challenges, ensuring they stay compliant while optimising costs and operational efficiency. Contact us to discuss your Java licensing and compliance strategy today.
Ready to move forward? Get in touch.