Full Use vs ASFU: Which Oracle Licence Do You Have?

What Is the Core Difference Between Full Use and ASFU?

The difference between Full Use and ASFU is a usage restriction, not a technical one. A Full Use licence is an Oracle licence granting unrestricted use of the program — you may deploy Oracle Database with any application, internal or third-party, custom or packaged. An ASFU (Application Specific Full Use) licence grants the full functionality of the same Oracle program, but restricts its use to one specific application named in the ordering document, almost always a third-party vendor's product.

Both deliver the complete database. With either licence you get the same Enterprise Edition or Standard Edition 2 software, the same performance, the same features. ASFU is not a cut-down database — that is exactly why the restriction matters. Because the software is identical, nothing technically prevents you using an ASFU database for other purposes. The only thing stopping you is the contract, and the only thing enforcing the contract is an Oracle audit.

This is the trap. Enterprises treat ASFU as "a database we own" and quietly extend it — a reporting tool here, an integration there — without realising each extension steps outside the licence grant. For the full taxonomy of Oracle licence models including embedded and OEM variants, see our Oracle license types explained guide.

How Do I Know Whether I Have a Full Use or ASFU Licence?

You determine your licence type from the contract paperwork, not the software. The Oracle program looks identical either way, so the answer lives in your ordering document and the third-party vendor's agreement. Check these signals in order:

1. The ordering document. ASFU orders explicitly name the application the Oracle program may be used with and include a restricted-use clause. A Full Use order grants the program without naming an application.
2. Who sold it. ASFU is most often sold through the application vendor or an Oracle partner bundling the database with their product. Full Use is typically bought directly from Oracle.
3. The price you paid. A database that cost dramatically less than Oracle list for the same processor count is a strong ASFU signal.
4. The support contract. ASFU support is sometimes routed through the application vendor's contract rather than your direct Oracle CSI.
5. The licence metric language. ASFU ordering documents reference the same Processor and Named User Plus metrics but bind them to the named application.

Full Use vs ASFU: Side-by-Side Comparison

The two licence types sit on opposite ends of a flexibility-versus-price trade-off. The table below maps the dimensions that matter when you are deciding which you hold — or which to buy.

For the deeper single-topic treatments of each side, see Oracle Full Use License Explained and Oracle ASFU Licensing. The even more restrictive embedded variant is covered in Oracle ESL (Embedded Software License) Explained.

What Does an ASFU Licence Restrict You From Doing?

An ASFU licence restricts the Oracle program to the single application named in your agreement. Every practical limitation flows from that one rule. The actions that most often breach an ASFU grant:

• Connecting reporting or BI tools directly to the ASFU database for purposes beyond the named application.
• Running a second application against the database, even an internal one, even from the same vendor.
• Building custom schemas, tables, or jobs for your own use inside the ASFU database.
• Using the database as a data source for ETL, integration, or a data warehouse outside the application.
• Activating database options — Partitioning, Diagnostics Pack, Tuning Pack, Advanced Security — that the ASFU bundle does not include. These are licensed separately and frequently triggered accidentally.

Oracle treats any of these as converting the deployment from application-specific to general-purpose use — that is, from ASFU to Full Use. The compliance gap is then valued at Full Use list, not the discounted ASFU price you paid. This is the mechanism by which a modestly priced ASFU database becomes a Full Use back-licence claim several times its size.

How Does Pricing Compare — and What's the Trade-Off?

ASFU is cheaper to acquire and that is the whole appeal. ASFU licences typically carry a 40–60% discount against Oracle's Full Use list price for the same Processor or Named User Plus count. Oracle discounts ASFU heavily for a deliberate reason: a database that can only ever run one application is no threat to Oracle's Full Use enterprise revenue, so Oracle can afford to price it aggressively to win the application bundle.

The trade-off is everything you give up for that discount. Three costs routinely erase the saving over a deployment's life:

• No flexibility. The moment the business wants the database to do anything beyond the named application, you face a conversion — and Oracle prices conversions from a position of strength.
• No leverage. Because ASFU is tied to the vendor bundle, you have little independent negotiating position with Oracle at renewal or trade-up.
• Same support burden. Oracle Enterprise Support runs 22% of net licence value per year under ASFU just as under Full Use — the discount applies to the licence, not the perpetual support stream.

Whether ASFU is genuinely cheaper depends entirely on whether the deployment stays inside its named-application boundary for its whole life. If it does, the discount is real money saved. If the business outgrows the boundary, the conversion and audit exposure can make Full Use the cheaper choice in hindsight. Benchmarking that decision against projected usage is exactly what independent Oracle negotiation support exists to do.

How Does Full Use vs ASFU Change Your Audit Exposure?

The two licence types fail audits in completely different ways, and knowing which you hold tells you where Oracle will look. With ASFU, Oracle's License Management Services (LMS) and GLAS teams target the boundary: every tool, user, schema, and application touching the database is examined for whether it falls inside the named application. The classic finding is a reporting layer or integration that "just reads the data" — direct Oracle use outside the grant, re-valued at Full Use list.

With Full Use, there is no application boundary to breach, so the audit risk shifts to quantity and options. Oracle measures processor counts under the Core Factor Table, counts Named User Plus against the contractual minimums, and runs scripts to detect accidental option usage — Partitioning, Diagnostics Pack, Advanced Compression — that may be active without a separate licence. The exposure is real but it is a counting and configuration problem, not a scope problem.

In both cases, Oracle's opening number is a negotiating position, not a settled debt. Our Oracle Audit Defense team challenges ASFU scope findings by reconstructing what the named-application grant actually covers, and challenges Full Use findings by re-checking processor maths, option usage, and the contractual minimums Oracle applies. The full sequence is set out in the Oracle audit defense guide, and a worked outcome appears in our case studies.

Can You Convert ASFU to Full Use — and Should You?

Yes, ASFU can be converted to Full Use through a trade-up negotiated with Oracle, where you pay the difference between the discounted ASFU price and the Full Use price for the same metric and quantity. The mechanism is straightforward; the economics are where enterprises lose money. Because ASFU gives you limited leverage, Oracle typically prices the trade-up near the full delta to list and treats the request as a buying signal for a broader conversation.

There are three situations where a deliberate conversion makes sense: when the business has decided the database will serve workloads beyond the named application; when an audit has surfaced out-of-scope usage and Full Use is cheaper than the back-licence claim plus penalties; or when consolidating multiple ASFU instances into a Full Use estate simplifies compliance and support. In each case the move should be benchmarked against alternatives — including re-architecting the offending workload onto a separate licensed database, or moving to cloud — before you accept Oracle's number.

The wrong way to convert is reactively, under audit pressure, with Oracle setting the price. The right way is proactively, with independent benchmarking establishing the fair trade-up value first. That is the difference our Oracle Contract Negotiation team makes on conversion deals.

Which Is Right for Your Estate — Full Use or ASFU?

The decision turns on one question: will this database ever serve more than the one application? If the answer is a confident never — a dedicated database running a single packaged product with no reporting, integration, or custom development against it — ASFU is the right-sized, cheaper choice. The discount is real and the restriction costs you nothing you would have used.

If there is any realistic chance of additional workloads — a reporting layer the business will inevitably ask for, an integration to another system, a second app that "could just use the existing database" — Full Use is the defensive choice. Paying the higher upfront price avoids both the conversion cost and the audit exposure that scope drift creates. The most expensive outcome is buying ASFU to save money, then drifting out of scope and paying Full Use plus back-support anyway.

For multi-instance estates the answer is rarely uniform: some databases are genuinely single-application and belong on ASFU, others are shared platforms that must be Full Use. Getting the classification right across the estate — and documenting the boundaries so they hold under audit — is the core of license optimization and the surest way to right-size Oracle spend without creating compliance gaps. See the broader framework in the Oracle Database Licensing Guide.