Oracle ULA Product List: What's Typically Included & What's Not

How the ULA Product Schedule Works

An Oracle Unlimited License Agreement grants the named Licensee entity the right to deploy unlimited quantities of specific Oracle software products during the ULA term. The products covered are listed in a Schedule, Exhibit, or Annex attached to the Order Form — typically called the Product List, Schedule A, or similar. The product list is the legal boundary of the ULA: products appearing in the list are covered with unlimited deployment rights; products not in the list require separate Oracle licenses regardless of how closely related they are to the listed products.

Each product in the ULA product list is described with three key attributes: the product name (which must match Oracle's then-current product naming), the license metric (Processor, Named User Plus, Employee, or application-specific metric), and the license type (typically Perpetual for database products, Subscription for newer products like Java SE). Understanding all three attributes for every product in your ULA is essential for both compliance management during the ULA term and for certification planning.

Oracle's product naming has changed significantly over the past decade. Products that were licensed under one name at ULA signature may have been renamed, bundled, or split into separate products by Oracle's current product catalog. When reviewing your ULA product list, verify each product name against Oracle's current product catalog to confirm you understand what is actually covered. Oracle has commercially exploited product renaming in certification discussions to argue that a product listed in the ULA no longer matches the currently deployed version — a position that requires careful contractual challenge. The Oracle ULA Guide covers these product definition disputes in detail.

Products Commonly Included in Enterprise ULAs

Enterprise ULAs are typically centred on Oracle's highest-value database and middleware products. The following products appear most frequently in enterprise ULA product schedules, based on our experience with 40+ ULA certifications and negotiations.

Products Oracle Typically Excludes from ULAs

Oracle's commercial strategy for ULA product lists is to include high-volume deployment products — products the enterprise will definitely deploy extensively — while excluding high-value niche products that Oracle can license separately at full price. Understanding what Oracle typically excludes helps enterprises negotiate more comprehensive product schedules at ULA inception, and identifies compliance risks for enterprises already holding ULAs.

Oracle consistently excludes its newer cloud products and SaaS applications from ULA product schedules. Fusion ERP, Fusion HCM, Oracle Analytics Cloud, and OCI infrastructure services are cloud-native subscription products that Oracle does not include in traditional ULA frameworks. An enterprise that expands from on-premises Oracle Database under a ULA into OCI or Fusion Cloud is not licensing its cloud footprint under the ULA — it is creating a separate cloud subscription relationship with Oracle that the ULA does not address.

Several high-value Oracle products are also routinely excluded: Oracle In-Memory (a database option that Oracle sells as a premium add-on), Oracle Spatial and Graph (often technically available but commercially charged when used at scale), Oracle Label Security, Oracle Database Vault, and most Oracle Analytics products. If your organization uses any of these products, verify their status in your ULA's product schedule immediately. The Oracle Database Options licensing guide documents which options are typically excluded from ULAs and the compliance implications of each.

NetSuite, Oracle Retail, Oracle Transportation Management, and other industry-specific Oracle applications are user-metric applications licenced entirely separately from infrastructure ULAs. A ULA covering Oracle Database EE does not cover the Oracle application layer running on that database. This is a critical distinction for enterprises whose Oracle application footprint (EBS, PeopleSoft, JD Edwards, Siebel, Fusion) runs on Oracle Database infrastructure covered by the ULA.

Database Options: The Compliance Trap Inside the ULA

Oracle Database Enterprise Edition is almost always included in enterprise ULAs. But the ULA's coverage of Database EE does not automatically cover all Oracle Database options that can be enabled on an EE installation. Oracle's database option model requires separate licenses for each option — Diagnostics Pack, Tuning Pack, Partitioning, In-Memory, Advanced Security, Label Security, Database Vault, Spatial and Graph, RAC One Node, and others. A ULA that includes Database EE and RAC but not Diagnostics Pack does not license Diagnostics Pack usage, even though Diagnostics Pack is part of the Oracle Database EE feature set.

The dangerous reality is that many of these options can be enabled accidentally — through routine DBA activities, automated installations, or Oracle Enterprise Manager default configurations. Oracle's USMM audit scripts detect which options have been enabled (i.e., used at least once) during the audit collection window. Oracle's position is that "enabled" equals "used" equals "licensed required" — creating compliance claims for options that may have been enabled by default rather than by deliberate business decision.

For ULA holders, the critical question is: which database options are explicitly included in my ULA product schedule? Pull your Order Form product list and cross-reference every Oracle Database option your environment might have enabled against that list. Diagnostics Pack is particularly high-risk because enabling it also enables Tuning Pack (they share a license), and Enterprise Manager uses both for standard performance monitoring. If Diagnostics Pack is not in your ULA's product schedule, disable it across every Database EE instance before running any Oracle certification measurement. The Oracle Diagnostics Pack licensing guide explains the technical remediation steps for disabling these options safely.

Java SE and Middleware: Separate Negotiation Required

Java SE and Oracle middleware products (beyond WebLogic) are the two categories most commonly missing from enterprise ULA product schedules — and the two categories generating the largest compliance claims when their absence is discovered at certification or audit. Java SE in particular has become Oracle's most aggressive compliance enforcement area since the 2019 commercialisation of Oracle JDK and the 2023 introduction of the Employee Metric.

If your organization deploys Oracle JDK in a production environment and Java SE is not in your ULA's product schedule, you have a Java SE compliance gap. The scale of that gap depends on your Java SE deployment profile and Oracle's current pricing metric. For an enterprise with 10,000 employees, the Java SE Universal Subscription at Employee Metric pricing can exceed $2M annually — a compliance gap that Oracle is highly motivated to identify and monetise. The Oracle ULA and Java guide provides the complete analysis of how Java SE interacts with ULA coverage.

Oracle middleware products beyond WebLogic — SOA Suite, OSB (Oracle Service Bus), ODI (Oracle Data Integrator), BPEL Process Manager — require explicit inclusion in the ULA product schedule to be covered. Many enterprises that deployed these middleware products under a previous era of Oracle licensing (pre-2010 bundled options, etc.) have not verified whether their current ULA explicitly lists each product. A ULA that says "WebLogic Suite" may cover a bundle of middleware products — but the definition of "WebLogic Suite" varies between Oracle product catalog versions. Verify every middleware product against the specific product definition in your contract, not against Oracle's current product marketing materials.

OCI and Cloud Products in ULA Context

Oracle Cloud Infrastructure (OCI) services — compute, storage, networking, database-as-a-service, autonomous database — are cloud subscription services that are not covered by traditional on-premises ULAs. A ULA that was signed before OCI existed, or that covers Oracle Database EE for on-premises deployment, does not license OCI deployments. Moving Oracle Database workloads from on-premises (covered by ULA) to OCI without a separate OCI contract creates a compliance gap — you are now running Oracle software on Oracle-managed cloud infrastructure without an Oracle cloud service agreement.

The BYOL (Bring Your Own License) mechanism for OCI is the correct path for applying ULA-certified perpetual licenses to OCI deployments. After ULA certification, the perpetual licenses created by the certification process can be applied to OCI deployments under BYOL terms — reducing the OCI cloud service cost by the value of the applied license. But BYOL on OCI has specific rules about which license types qualify, which OCI shapes are eligible, and how license quantities are calculated for multi-core OCI instances. These rules are set by Oracle and are subject to change. The Oracle Cloud Advisory service provides expert guidance on BYOL optimization for post-ULA cloud migrations.

Some newer ULAs include Oracle Database Cloud Service (DBCS) or Oracle Autonomous Database as covered products — allowing unlimited deployment of Oracle's managed cloud database services during the ULA term. These cloud product ULAs are structurally different from traditional on-premises ULAs: the "unlimited" deployment right applies to cloud service consumption units, the certification mechanism is different, and the post-ULA license position may be structured as a subscription rather than a perpetual license. Enterprises holding cloud-product ULAs should engage advisory support well in advance of certification to understand the specific mechanics of their agreement. The Oracle Cloud Licensing Guide provides the full framework.

Negotiating the Product List: What to Push For

When negotiating a new ULA or renewing an existing one, the product list negotiation is the single most important commercial activity — more important than the headline price or the ULA term length. Every product that is not in the product schedule at signature requires separate licensing (at full cost) for the entire ULA term. Every product that is included benefits from the unlimited deployment right — providing cost certainty regardless of how extensively the enterprise deploys that product.

Include all Oracle Database options you currently use or might use. At the time of ULA negotiation, Oracle is motivated to close the deal and will accept a broader product list at a lower incremental cost than at any other commercial moment. Diagnostics Pack and Tuning Pack should be standard inclusions. In-Memory, if your organization uses it or might use it, is worth negotiating now rather than licensing separately later. Advanced Security for pre-19c database versions should be explicitly addressed.

Include Java SE if you deploy Oracle JDK in production. Oracle's Java SE pricing has increased dramatically since 2019 and again in 2023. If you have 5,000+ employees and deploy Oracle JDK in any production workloads, the cost of including Java SE in the ULA product schedule is likely less than the annual Java SE subscription cost you will face post-ULA. Push for Java SE Universal Subscription (Employee Metric) to be included in the ULA product schedule. The Java SE pricing guide provides the benchmark cost data for this negotiation.

Include disaster recovery and test/dev environments explicitly. Some ULA product schedules include specific provisions for DR and non-production environments. Negotiate these explicitly rather than relying on general non-production exclusions that Oracle may challenge at certification. A named DR provision in the product schedule is stronger than a disputed non-production exclusion interpretation.

Negotiate a worldwide territory with comprehensive affiliate coverage. As discussed in our ULA territory and entity restrictions guide, the territory and entity provisions of the ULA are as important as the product list. Negotiate worldwide territory and a comprehensive affiliate definition at inception rather than facing coverage gaps for global subsidiaries during the ULA term.

Reviewing Your Current ULA Product Schedule

If you currently hold an Oracle ULA and have not recently reviewed your product schedule against your actual Oracle software deployment, conduct this review immediately. The review should map every Oracle product installed or deployed in your environment against the product schedule, identify products not in the schedule, assess the license requirement for each out-of-schedule product, and prioritize remediation or negotiation based on compliance risk and cost.

The review should be conducted by an independent advisor with Oracle licensing expertise — not by Oracle's account team, and not solely by your internal ITAM team without external validation. Oracle's account team has a commercial incentive to identify compliance gaps they can monetise; your ITAM team may lack the specific Oracle product definition expertise to correctly classify edge cases. Independent advisors with Oracle LMS experience understand exactly how Oracle approaches product definition disputes in certification and can assess your compliance position from Oracle's perspective as well as your own.

The Fortune 500 Bank Oracle Agreement Restructure case study demonstrates the value of a proactive product schedule review: our team identified $8M in projected Oracle compliance claims before the client's ULA certification, allowing a structured resolution through targeted product list negotiation rather than a contentious certification dispute. In virtually every case where we have conducted a pre-certification ULA compliance review, we have identified product gaps that the client was unaware of — and resolved those gaps at significantly lower cost than Oracle's certification claims would have required.

Engage the Oracle ULA Advisory service for a comprehensive product schedule review. Our former Oracle LMS auditors know exactly which products Oracle targets in certification reviews and can prepare your compliance position before Oracle's team enters the process.