An Oracle Full Use license is the most flexible — and most expensive — way to license Oracle software. It carries no application restriction, which is exactly why Oracle's audit team treats it as the default deployment right against which every other license type is measured. Understanding what Full Use grants, and what it does not, is the difference between a clean entitlement position and a seven-figure back-licence claim.
Short answer: An Oracle Full Use license grants unrestricted use of an Oracle program for any application or workload — it is not tied to a specific vendor application — subject only to the licensed metric (Processor or Named User Plus) and quantity. It is sold at Oracle's standard price list and is the broadest, costliest license type, in contrast to the cheaper but restricted ASFU and Embedded (ESL) licenses.
Definition: An Oracle Full Use license is a license grant that permits unrestricted productive use of an Oracle program for any purpose, with no restriction on which applications may run against it. The only limits are the licensed metric and the quantity you purchased.
Most enterprise Oracle estates are licensed Full Use whether or not the buyer ever used those words. When you purchase Oracle Database Enterprise Edition, WebLogic, or the Diagnostics Pack directly from Oracle at price-list rates, you are buying a Full Use license. The defining characteristic is the absence of an application restriction: you can run a packaged ERP, a home-grown analytics platform, a third-party data warehouse, and ad-hoc developer queries against the same Full Use database, and every one of those uses is permitted.
This is what separates Full Use from the two restricted alternatives. An ASFU (Application Specific Full Use) license is bound to one named independent software vendor (ISV) application and may not be used for anything else. An Embedded Software License (ESL) is even narrower — the Oracle technology is embedded inside a third-party product and cannot be accessed directly by the customer at all. Full Use is the only one of the three that gives you the keys to the database itself.
The trade-off is price. Because Full Use carries no restriction, Oracle charges the most for it. Buyers who pay Full Use rates but only ever run a single application are overspending; buyers who pay ASFU rates but actually use the software for general-purpose workloads are out of compliance. Getting the license type right is the single largest lever in an Oracle estate, and it is precisely the area where our independent reviews most often find both overspend and audit exposure sitting side by side.
Full Use licenses are sold under two primary metrics, and the choice between them drives your cost and your audit exposure more than almost any other decision.
The Processor metric counts every physical core on which the program is installed and/or running, multiplied by the value in Oracle's Core Factor Table. A 32-core Intel server at a 0.5 core factor requires 16 Processor licenses. The Processor metric is used where the user population is large or uncountable — internet-facing systems, for example — because it ignores user numbers entirely.
A Named User Plus is an individual authorized to use the program, whether or not they are actively using it at any given moment, plus any non-human operated device that accesses the program. NUP is subject to per-processor minimums: Oracle Database Enterprise Edition requires a minimum of 25 Named User Plus per processor, regardless of how few humans actually log in.
The NUP minimum is the trap that catches most Full Use buyers. An enterprise running Database EE on a 16-core server (8 processors after core factor) must license at least 200 Named User Plus — 8 processors × 25 — even if only 30 named users exist. Buyers who size NUP against their actual user count, ignoring the minimum, walk straight into a back-licence claim. The forensic rule we apply on every engagement: count the metric Oracle will count, not the metric that feels intuitive.
Insider note: Oracle's LMS scripts report installed cores and authorized users from the same data pull. If your Named User Plus count falls below the per-processor minimum, the audit report quietly substitutes the minimum and prices the gap. You will not see a separate line explaining this — you have to challenge it.
Our Oracle License Optimization service maps every Order Form to its true license type and metric — surfacing both overspend and audit exposure before Oracle's LMS team does.
The three Oracle license types differ on one axis: how much freedom you have to use the software. Full Use sits at the unrestricted end; Embedded sits at the locked-down end. The table below is the comparison Oracle's sales team rarely lays out in writing, because the restrictions are where the cheaper licenses lose their value.
| Attribute | Full Use | ASFU | Embedded (ESL) |
|---|---|---|---|
| Application restriction | None — any workload | One named ISV application only | Locked inside the vendor product |
| Direct database access | Yes | Yes, for the named app | No customer access |
| Sold by | Oracle direct | The ISV / reseller | The ISV / OEM |
| Relative price | Highest (list price) | Discounted (often 30–70% off) | Lowest (bundled) |
| Use for in-house dev | Permitted | Prohibited | Prohibited |
| Audit risk profile | Scope creep on cores/users | Using it beyond the named app | Direct access by customer |
The most common compliance gap we see is an ASFU license being used as if it were Full Use. A buyer purchases discounted ASFU database licenses bundled with an ISV application, then their DBA team — not knowing the restriction — points reporting tools, ETL jobs, or a second application at the same database. Every one of those additional uses is a breach of the ASFU restriction, and Oracle prices the remediation at full Full Use list rates. The discount that looked attractive at purchase becomes the lever Oracle uses to back-licence the entire deployment.
Short answer: Oracle Database Enterprise Edition Full Use is listed at US$47,500 per Processor or US$950 per Named User Plus on Oracle's Technology Price List, plus first-year support at 22% of net license value. Options such as Partitioning, Diagnostics Pack, and Advanced Security each add their own per-processor list price on top.
Full Use pricing follows Oracle's published Technology Price List, but the list price is a starting position, not a settlement. Oracle routinely discounts new license purchases, and the discount is a negotiation variable — not a fixed rate. The number that matters long term is the net license value, because Oracle's Enterprise Support is priced at 22% of that net figure every year, and that support stream typically costs more over a five-year horizon than the licenses themselves.
Across more than 600 engagements, we have found that enterprises buying Full Use licenses without independent benchmarking pay materially more than peers of comparable size for the same products (Oracle Licensing Experts engagement data, 2026). The gap is rarely about the headline discount Oracle advertises; it is about the options stacked on top, the NUP minimums applied, and the support base that compounds at renewal. A Full Use purchase negotiated in isolation almost always leaves money on the table.
See how a manufacturer cut its Oracle renewal by rebuilding its license position — read the case studies, then talk to a former Oracle insider.
Full Use licenses are most commonly sold as perpetual licenses, meaning the right to use the software does not expire and survives even if you stop paying annual support. This is a genuine asset on your balance sheet, and it is the foundation of any third-party support strategy: a perpetual Full Use license entitles you to keep running the software indefinitely without Oracle, even though you forgo Oracle's patches and updates.
But "Full Use" and "perpetual" are not synonyms. Oracle also sells Full Use rights as term licenses and as subscriptions, where the right to use lapses when the term ends. The license type (Full Use) describes how broadly you may use the software; the license duration (perpetual, term, or subscription) describes how long. Always read the Order Form to confirm both. We have seen enterprises assume a perpetual entitlement, plan a support-exit around it, and discover the underlying license was a term grant that expired — collapsing the entire strategy.
A Full Use license removes the application restriction, but it does not remove Oracle's counting rules. Three areas account for most of the back-licence claims we defend against on Full Use estates.
Virtualization. A Full Use entitlement does not exempt you from Oracle's Partitioning Policy. On VMware clusters, Oracle's stated position is that you must license every physical core in every host where the VM could run — not just the cores it actually uses. The Full Use license proves your right to deploy; it does nothing to cap the core count Oracle demands. This is consistently the single biggest compliance trap in virtualized environments.
Accidental option usage. Full Use Database EE includes the engine, but the options and management packs are separately licensed. Diagnostics Pack, Tuning Pack, Partitioning, Advanced Compression, and In-Memory are all enabled by default or by a single command, and Oracle's scripts detect their use. A Full Use base license offers zero protection against an unlicensed option being switched on — and Oracle's Diagnostics Pack is accidentally enabled in a large share of enterprise environments.
Cloud deployment. Moving a Full Use license to AWS, Azure, or Google Cloud invokes Oracle's BYOL counting rules, which translate cloud vCPUs into Oracle Processor licenses on terms Oracle defines and updates. The Full Use grant travels with you, but the multiplier may not be what you expect. Our Cloud & OCI Advisory team rebuilds the count before the migration, not after the audit.
Yes — Oracle permits a trade-up from ASFU to Full Use, but it is a commercial transaction, not an automatic right. You pay the difference between the ASFU price you originally paid and the current Full Use list price, plus the corresponding support uplift on the higher net value. There is no credit for the years you ran the software under ASFU, and the trade-up is negotiated at Oracle's discretion on timing and discount.
The practical takeaway: the ASFU discount is not a permanent saving if your usage is trending toward general-purpose deployment. If you anticipate running additional applications against an ASFU-licensed database, model the trade-up cost before you commit, and consider whether negotiating Full Use up front — with a deeper discount tied to the larger commitment — is cheaper than paying twice. This is exactly the kind of forward-looking position our Oracle Contract Negotiation team builds into the original deal, before the restriction becomes a liability.
An Oracle Full Use license grants unrestricted use of an Oracle program for any application or purpose, subject only to the licensed metric and quantity. Unlike ASFU or Embedded licenses, it is not tied to a specific vendor application and gives the customer direct access to the software for any workload, including in-house development.
A Full Use license can run any application and is sold at Oracle's standard list price. An ASFU license is restricted to a single named ISV application, is sold through that ISV at a discount of typically 30–70%, and cannot be used for in-house development or any other application. ASFU is cheaper but far more restrictive, and exceeding its restriction triggers a Full Use back-licence claim.
Full Use licenses use the Processor metric — physical cores multiplied by the Core Factor Table — or the Named User Plus metric, which counts authorized individuals subject to per-processor minimums. Oracle Database Enterprise Edition requires a minimum of 25 Named User Plus per processor, even if fewer users exist.
Usually, but not always. Full Use is most often sold as a perpetual license that does not expire, but Oracle also sells Full Use rights as term and subscription licenses that lapse at the end of the term. License type and license duration are independent — always check the Order Form to confirm whether yours is perpetual.
A Full Use license grants the right to deploy, but Oracle's Partitioning Policy and cloud BYOL rules determine how many licenses you need. On VMware, Oracle's position is that you license every core a VM could run on, not just the cores it uses. Full Use does not exempt you from these counting rules.
Yes, through a trade-up. You pay the difference between the original ASFU price and the current Full Use list price, plus the support uplift. There is no automatic conversion and no credit for prior years, so model the trade-up cost before relying on an ASFU discount for a workload that may expand.
Our playbook for right-sizing an Oracle estate — mapping license types, eliminating overspend, and closing compliance gaps before Oracle finds them. Independent, buyer-side, free.
Explore License Optimization →License-type traps, pricing benchmarks, and negotiation tactics — for Oracle stakeholders at 2,000+ enterprises globally.
Written by the Oracle Licensing Experts Team — former Oracle executives, LMS auditors, and contract managers with 25+ years of combined Oracle licensing experience. Not affiliated with Oracle Corporation. All advisory is independent and 100% buyer-side.