Oracle Licensing FAQ: 50 Most Common Questions Answered

Processor licensing is based on the number of CPU cores on which Oracle software is installed or running. Named User Plus (NUP) licensing counts every individual (and every device) authorised to access the software. Processor is generally used for large or unknown user populations; NUP is used where users can be counted and restricted to a defined list.

Oracle Database Enterprise Edition requires a minimum of 25 Named User Plus licences per processor. Even if a database has only 3 users on a single-processor server, you must purchase 25 NUP licences for that server. The minimum applies after applying the core factor.

The Core Factor is a multiplier Oracle applies to physical CPU cores to calculate the number of Processor licences required. Most modern Intel Xeon and AMD EPYC processors have a factor of 0.5, meaning 2 physical cores = 1 Processor licence. IBM POWER typically carries a 1.0 factor. The core factor table is published by Oracle and updated periodically.

No. The core factor table applies only to on-premises deployments and OCI BYOL (where 1 Processor licence covers 2 OCPUs). On AWS, Azure, and Google Cloud, the rule is 2 vCPUs = 1 Processor licence — the on-premises core factor table does not apply.

Only if you use Oracle-approved hard partitioning technology (such as Oracle VM with CPU pinning, or IBM LPAR with capped partitions). Without hard partitioning, Oracle requires you to licence all physical cores on the server regardless of which cores are actually used by Oracle.

No. Oracle does not recognise VMware vSphere, ESXi, or any VMware technology as hard partitioning. If Oracle software runs in a VMware environment, Oracle's policy requires all physical cores in the VMware cluster (across all hosts where Oracle could run) to be licensed, not just the VM's vCPU allocation.

No. Microsoft Hyper-V is also classified as soft partitioning by Oracle. The same cluster-wide licensing requirement applies: all physical cores on Hyper-V hosts in the cluster where Oracle could be deployed must be licensed.

Oracle Database Standard Edition 2 (SE2) requires a minimum of 10 Named User Plus licences per server — not per processor. SE2 is also capped at a maximum of 2 CPU sockets per server and does not support clustering.

Yes. Any automated process — a batch job, a middleware connection, a scheduled task, a device polling Oracle — must be counted as a Named User Plus licence. The "Plus" in NUP explicitly covers automated and device access. Organisations frequently undercount NUP by excluding automated connections and then find they are under-licenced during an audit.

The crossover depends on the Oracle edition, core count, and negotiated discount. For Oracle Database Enterprise Edition on a 4-core Intel server (2 Processor licences at $47,500 each = $95,000 list) versus NUP at $950 per licence (list), the crossover is at 100 users. Above 100 users, Processor is cheaper. Below 100 users, NUP may be more cost-effective.

Hard partitioning uses physical or enforced technology controls to restrict Oracle software to a defined subset of CPU cores. Oracle recognises hard partitioning as a valid way to limit licence scope. Examples include Oracle VM Server with CPU pinning, IBM LPAR with capped partitions, Solaris Zones with CPU capping, and Oracle Linux KVM with hard cgroups. All other virtualisation is considered soft partitioning and does not limit licence scope.

On AWS, the rule is 2 vCPUs = 1 Oracle Processor licence (with hyperthreading). The on-premises core factor table does not apply. All EC2 instances running Oracle software must be licenced based on their vCPU count. AWS Dedicated Hosts may allow licence optimisation but only under specific conditions documented in Oracle's cloud licensing policy.

Bring Your Own Licence (BYOL) allows customers to apply existing on-premises perpetual Oracle licences to cloud environments. Oracle officially authorises BYOL on OCI (Oracle Cloud Infrastructure), AWS, Microsoft Azure, and Google Cloud Platform. Each cloud has the same 2 vCPU = 1 Processor rule (except OCI, where 1 Processor = 2 OCPUs).

This depends on how the instance is stopped. A "stopped" (OS-stopped) instance in AWS or Azure still has allocated compute resources and Oracle may argue the software remains installed. A "deallocated" Azure VM or "terminated" AWS instance with no persistent installation generally does not require a licence. Always consult your contract and Oracle's cloud licensing policy document for the specific language applicable to your situation.

Yes. Google Cloud is an Oracle-authorised cloud environment (ACE), and BYOL rules apply: 2 vCPUs = 1 Processor licence. Google Cloud Bare Metal Solution (BMS) is an alternative for workloads requiring dedicated hardware or Oracle RAC, and licensing on BMS follows on-premises rules with all physical cores counted.

Not if you BYOL. Existing on-premises perpetual licences can be applied to OCI workloads under BYOL. On OCI, 1 Processor licence covers 2 OCPUs — twice the coverage of AWS, Azure, or GCP. This OCI advantage means that migrating to OCI can reduce the number of Processor licences required relative to other cloud providers.

Oracle does not recognise Nutanix as hard partitioning. The same soft partitioning rules apply: all physical cores in the Nutanix cluster where Oracle software could run must be licenced. This is a significant source of compliance exposure for organisations that migrated from VMware to Nutanix under the assumption that licensing treatment would change.

Yes. Oracle OCI offers licence-included options for Oracle Database (sometimes called OLTP or HTAP services) where you pay a consumption-based fee that includes the Oracle Database licence. This is an alternative to BYOL and can be economically attractive for organisations that do not hold large perpetual licence estates.

Under BYOL, any Oracle Database Options installed on or enabled in a cloud instance must also be licenced, the same as on-premises. If you enable Oracle Advanced Compression, Oracle Partitioning, or Oracle RAC in a cloud VM, you must hold the corresponding option licences. Oracle's LMS audit process checks for enabled options regardless of whether they are in cloud or on-premises environments.

Yes. Docker containers and Kubernetes pods are treated as soft partitioning by Oracle. If Oracle Database runs in a container, Oracle will require all physical cores on all host nodes that could potentially run the container to be licenced. This is one of the fastest-growing sources of Oracle licence exposure in enterprises modernising their application architectures.

Oracle typically audits customers on a cycle of every 3 to 5 years. Audit likelihood increases significantly around major events: M&A transactions, cloud migrations, renewal negotiations, and periods following significant deployments. Organisations that have not been audited in 5+ years should treat that gap as a risk indicator, not a guarantee of safety.

Common audit triggers include: signing a ULA (Oracle audits to establish the certification baseline), major M&A activity, a renewal negotiation that Oracle wants to resolve in its favour, customer complaints about Oracle products, signals from Oracle sales that a customer's licence estate is growing, and random selection cycles. Oracle's LMS team operates on targets and will prioritise customers with the highest estimated shortfall.

Whether you are contractually required to cooperate depends on your specific Oracle contract. Most Oracle licences include an audit rights clause giving Oracle the right to audit upon notice. The notice period, scope of audit, and data sharing requirements vary by contract version. Always have legal counsel review your contract before responding to an audit letter.

Oracle License Management Services (LMS) is Oracle's internal audit and compliance organisation. LMS conducts software audits on behalf of Oracle and uses proprietary data collection scripts to inventory Oracle software deployments. LMS teams are trained to identify unlicensed use across database, middleware, Java, and applications, and they operate independently of Oracle's sales organisation.

Oracle's standard support contract includes an annual support fee escalator of 8% per year. This is a contractual provision, not an ad hoc increase. Over five years, this compounding means a support bill that starts at £100,000 reaches approximately £147,000 in year five and £216,000 in year ten. Managing this escalator is a key objective in Oracle contract negotiations.

Cancelling Oracle support means you lose access to patches, security updates, bug fixes, and Oracle Support portals. To reinstate support after cancellation, Oracle requires backdated support payments for the period support lapsed (plus a reinstatement fee). This can make cancellation a costly strategy if there is any chance of needing to reinstate. Third-party support from providers like Rimini Street is an alternative for non-cloud Oracle products.

Oracle's fiscal year ends 31 May. The Q4 window runs from March to May, when Oracle sales teams are under maximum pressure to close deals and achieve their annual targets. This creates genuine negotiating leverage for customers — Oracle sales will offer their best discounts, extended support commitments, and deal sweeteners during Q4. Organisations planning major Oracle contract actions should aim to conclude them during this window.

The most common unlicensed Oracle Database Options found in audits are: Advanced Compression, Diagnostics Pack, Tuning Pack, Real Application Testing, Partitioning, Active Data Guard, and Database Vault. Many of these options are enabled by default during database creation or by DBA scripts, and organisations often use their features without realising a separate licence purchase is required.

MySQL Community Edition is available under the GPL licence and is free for users complying with GPL terms. MySQL Enterprise Edition and MySQL Commercial licences require a paid subscription. Oracle does not require a licence for MySQL Community Edition under standard GPL use, but usage in proprietary commercial applications may require a commercial licence under GPL's viral provisions.

Yes, and this is strongly recommended. Many organisations have successfully negotiated support fee caps — freezing support at the current level for 2–3 years, or capping the annual escalator below 8%. Oracle will typically agree to support caps in exchange for additional licence commitments, a multi-year support contract, or as part of a broader ULA or cloud migration deal. The Q4 negotiating window is the best time to seek caps.

An Oracle Unlimited License Agreement (ULA) is a fixed-term contract (typically 2–4 years) under which you pay an agreed fee and may deploy unlimited quantities of specified Oracle products during the term. At expiry, you certify your actual deployment count, which becomes your perpetual licence entitlement. Support fees during the ULA are fixed — they do not increase with deployment volume.

Yes — absolutely. Since support fees are fixed regardless of deployment volume during a ULA, every additional deployment is effectively free in licence cost. Maximising deployment before the certification date increases your certified perpetual entitlement without increasing cost. Every Processor licence certified out of the ULA reduces the effective cost per licence. Failing to maximise deployment is one of the most common and costly ULA mistakes.

Oracle ULAs are negotiated on a product-by-product basis. Common ULA products include Oracle Database Enterprise Edition, Oracle Real Application Clusters (RAC), Oracle Partitioning, Oracle Advanced Compression, and selected middleware products. The covered products are explicitly listed in the ULA schedule — products not listed are not covered by the unlimited rights.

A ULA has a fixed term (typically 2–4 years) and requires certification at expiry. A PULA (Perpetual ULA) grants unlimited deployment rights in perpetuity — there is no certification requirement and no expiry date. PULAs are significantly more expensive than ULAs (often 2x the cost) and are extremely rare, typically reserved for very large Oracle customers.

No. Oracle does not offer an Enterprise Agreement (EA) equivalent to Microsoft's EA or SAP's ELA. The closest Oracle equivalents are the ULA (time-bound unlimited deployment), PULA (perpetual unlimited deployment), OCS subscription bundles, and CSI-based arrangements. Any commercial structure Oracle sales presents should be evaluated on its specific terms — not assumed to be equivalent to a competitor's EA structure.

Yes — Oracle typically allows ULA extensions, though they come at a cost (an additional fee, often structured as a percentage of the original ULA investment). Extensions are valuable when an organisation needs more time to maximise deployment before certification. Oracle's Q4 window is the best time to negotiate extension terms.

A CSI is Oracle's support account number — it is issued with every Oracle support contract and is required to access patches, updates, and Oracle Support portals. Organisations with complex Oracle estates often have multiple CSIs accumulated through acquisitions and legacy contracts. Reconciling CSIs is an important step in Oracle licence management to prevent duplicate support payments and establish a clean entitlement picture.

Oracle Cloud Services (OCS) is Oracle's umbrella term for its cloud subscription offerings — including SaaS (Fusion Cloud ERP, HCM, SCM), PaaS (Oracle Integration Cloud, APEX), and IaaS (OCI compute, storage, database services). OCS subscriptions grant time-limited usage rights — they do not confer perpetual licence entitlements, unlike traditional perpetual licences.

This depends on the ULA contract terms. Some ULAs include cloud deployment rights; others restrict deployment to on-premises environments. It is essential to review the specific ULA schedule for cloud deployment language before deploying ULA-covered products in any cloud environment. Oracle may attempt to argue that cloud deployments are not covered by an on-premises ULA during certification.

Oracle licences are typically entity-specific — they are granted to the contracting legal entity and its subsidiaries at the time of signing. In an acquisition, the acquirer's licences do not automatically extend to cover the acquired entity's Oracle deployments (and vice versa). Both entities must be mapped against their respective licence entitlements, and a licence reconciliation should be conducted before the transaction closes to avoid audit exposure and identify cost-saving opportunities.

Oracle JDK 17 and later releases are available under the No-Fee Terms and Conditions (NFTC) licence, which permits free commercial use for all users. However, organisations that need regular security patches, extended support, or Oracle's GraalVM Enterprise features must subscribe to Oracle Java SE Universal Subscription. This subscription is priced per employee of the total organisation — not per Java user — which dramatically increases the cost for large enterprises.

Oracle Java SE Universal Subscription is priced per employee of the subscribing organisation. The current pricing is approximately $15 per employee per month (subject to volume tiers and negotiated discounts). Critically, this is based on the total employee count — not the number of employees who use Java. A company with 10,000 employees pays for 10,000 units, even if only 500 employees' devices have Java installed.

Yes, and Oracle Java audits have become significantly more common since the 2023 introduction of the employee-based subscription model. Oracle targets organisations with large employee populations that are using Java SE 8 or Java SE 11 (both of which require a commercial licence for production use without a current support subscription). 2026 is a peak year for Java audit activity as "soft" inquiries from 2023–2024 are being converted to formal audits.

The primary free alternatives are: OpenJDK (the open-source reference implementation, available from multiple vendors), Eclipse Temurin (from the Adoptium project), Amazon Corretto, Microsoft Build of OpenJDK, Azul Zulu, and BellSoft Liberica. All of these are production-ready, TCK-compliant Java distributions that provide equivalent functionality to Oracle JDK without Oracle's commercial licence requirement.

Yes. Oracle WebLogic Server is a separately licenced middleware product, available in Standard Edition and Enterprise Edition. It is typically licensed by Processor or NUP, the same as Oracle Database. WebLogic licences are independent of Oracle Database licences — holding a Database licence does not grant WebLogic rights, and vice versa. Oracle Fusion Middleware Suite bundles are available but must be reviewed carefully for product scope.

Yes. Oracle Forms and Oracle Reports are separately licenced Oracle Fusion Middleware products. They are commonly found as legacy components in Oracle E-Business Suite (EBS) environments and require active licence entitlements even in modern EBS deployments. Organisations migrating from EBS to Oracle Fusion Cloud need to account for the ongoing Forms/Reports licence obligations on any remaining on-premises deployments.

Oracle Application Specific Full Use (ASFU) licences are granted by Oracle to ISVs (Independent Software Vendors) and passed to end customers as part of an application bundle. An ASFU licence permits Oracle technology use only in support of the specified application. If you receive Oracle software as part of a packaged ERP, HR, or industry application from a third-party vendor, that deployment is likely licenced under ASFU — not Full Use. ASFU misuse (using the database for other purposes) is a frequent audit finding.

Yes. Oracle E-Business Suite requires Oracle Database to run, and that database must be licenced. Historically, Oracle sold EBS with a bundled database licence (sometimes under ASFU terms). Modern EBS contracts typically include Full Use database rights. Always review your EBS contract to determine whether the database rights are included, ASFU-restricted, or require a separate purchase.

In a divestiture, Oracle licences generally cannot be transferred to the divested entity without Oracle's consent (Oracle licence agreements typically prohibit transfer without prior written consent). The divested entity will need to establish its own Oracle contracts. The divesting organisation must also update its own licence position to remove deployments that transfer with the divested business. Oracle licence teams should be engaged early in any carve-out transaction — post-completion surprises are very costly.

Redress Compliance provides independent Oracle licensing advisory — working exclusively for customers, never for Oracle. Our advisors have 20+ years of Oracle contract and audit experience and have managed over $4 billion in Oracle contract value across all industry sectors. We provide licence position assessments, audit defence, ULA and PULA negotiation support, and ongoing Oracle contract management. Contact us via redresscompliance.com/contact or explore our Oracle services at redresscompliance.com/oracle-services.