When Oracle's own products need a Java licence.
Some Oracle products come bundled with a restricted right to use Oracle Java SE — but only for running that specific product. Step outside that boundary and the same Java installation needs its own subscription. This is one of the most commonly missed sources of exposure, because it hides inside software you already run and trust.
Oracle's Approved Product Use list.
Oracle's OTN licence for Java SE permits free use in four cases: personal use, development use, Oracle Cloud Infrastructure (OCI) use, and "Oracle Approved Product Use" — running Java bundled with a specific list of Oracle products, restricted to that product's own operation. Oracle publishes the Approved Product Use case as two lists: Schedule A and Schedule B Products.
Running on Oracle Cloud Infrastructure is its own free-use case, separate from Schedule A/B. If Java is running as part of your actual OCI usage, it's covered under the OCI free-use terms directly — no Schedule A/B product needs to be involved. This is easy to miss if you're only checking the Schedule A/B list and don't realise OCI itself is a separate, simpler answer.
Schedule A is narrow. Schedule B is broader.
| Schedule A — restricted to the product itself | Schedule B — covers applications built on/with the product |
|---|---|
| Oracle SQL Developer | Oracle Forms (and applications that contain Oracle Forms) |
| Oracle Cloud Infrastructure – Oracle Management Agent (MACS Agent) | Oracle E-Business Suite (and applications that contain EBS) |
| Java bundled here is licensed only for running this specific tool — nothing else. | Oracle WebLogic Server client applications |
| Oracle Coherence client applications | |
| Oracle Agile Product Lifecycle Management client applications | |
| JD Edwards products | |
| Oracle AutoVue products | |
| Oracle Secure Global Desktop | |
| Oracle Demantra products — coverage extends to apps built using these, not just the product itself. |
Anything not on this list gets no Schedule A/B coverage at all. If a Java install bundled with some other Oracle program is used beyond development or personal use, it needs its own subscription — the product doesn't need to be obscure for this to apply.
The Java is fine for the product. It's rarely used only for the product.
Say your EBS environment bundles Java under Schedule B — that's covered, no separate licence needed for running EBS itself. The exposure shows up when the same Oracle JDK/JRE install on that server gets reused for something else: a DBA running an unrelated internal script off it, a separate WebLogic deployment that isn't actually an EBS/Forms client app, or any other case where the boundary between "supporting the approved product" and "general purpose use" gets blurred. The bundled licence doesn't travel with the JDK binary — it only covers the approved use case.
This is exactly the kind of detail a generic SAM tool won't catch, because it requires knowing which Oracle products are actually installed alongside which Java versions, and whether the observed usage stays inside the approved boundary — not just that "Java is present."
Straight from Oracle.
The Schedule A/B list above comes from Oracle's own Approved Product Use List. Oracle also documents the support angle in My Oracle Support Note 1557737.1 — "Support Entitlement for Java SE When Used As Part of Another Oracle Product" (requires an Oracle support login to view).
Find out what's actually covered — and what isn't.
A Risk Review checks exactly this kind of boundary, not just whether Java is present.
Book a Risk Review