Oracle Named User Plus Licensing Explained

Oracle Named User Plus Licensing

This guide explains Oracle’s Named User Plus (NUP) licensing model in detail, covering key topics such as definitions, user-counting rules, minimum requirements, and common pitfalls, in a step-by-step format.

For more on Oracle license metrics, read our complete guide, Oracle License Metrics & Definitions.

Step 1 – What Named User Plus Licensing Means

Oracle’s Named User Plus (NUP) is a user-based software licensing metric.

Each individual or device that accesses an Oracle program must have a license. It’s an alternative to processor-based licensing, typically used for systems with a limited, known user population.

Checklist: NUP Basics

• ✓ User-based licensing metric
• ✓ Counts each human and non-human user
• ✓ Must meet Oracle’s product-specific minimums
• ✓ Applies to certain Oracle programs (databases, middleware, etc.)
• ✓ Best for environments with smaller or controlled user groups

Table: NUP Overview

NUP licensing counts every user or device with direct or indirect access to the Oracle software.

Step 2 – What Counts as a Named User Plus

Oracle defines “named user” very broadly under NUP. Any person or non-human device that accesses Oracle software, directly or indirectly, counts as a Named User.

This includes people who log in to Oracle, users of applications that connect to Oracle in the background, and automated scripts or tools that query the database.

For instance, if 100 employees use an application backed by an Oracle database, all 100 require NUP licenses (even if the app uses only one Oracle account in the back end).

Checklist: Users Who Count

• ✓ Employees or contractors with direct Oracle logins
• ✓ End-users accessing Oracle through web apps or middleware
• ✓ External users via third-party integrations or APIs
• ✓ Service accounts, bots, and batch scripts
• ✓ Non-human devices (sensors, IoT devices) interacting with Oracle

Table: User Types Under NUP

NUP covers every individual and device that uses Oracle software, even through other systems.

Read our article on Oracle core factor table, Oracle Core Factor Table – License Calculator.

Step 3 – Understanding Oracle NUP Minimums

Oracle sets minimum NUP license requirements per product to ensure a baseline number of licenses. These minimums override your actual user count if it’s lower.

For example, Oracle Database Enterprise Edition requires at least 25 Named User Plus licenses per processor, even if you have fewer than 25 users. Oracle Database Standard Edition 2 typically requires 10 Named User Plus licenses per server.

In practice, a lightly used system might still need more licenses than it has users, just to meet Oracle’s minimums.

Checklist: Minimum Rules

• ✓ Oracle defines minimum NUP counts for each product
• ✓ Often expressed as NUP per processor or per server
• ✓ Must license the greater of actual users or the minimum requirement
• ✓ Minimums can raise costs for systems with few users
• ✓ Misunderstanding these rules is a common audit issue

Read our license metric comparision, Oracle Licensing: Named User Plus vs. Processor – Which to Choose?.

Table: Minimum User Example

Oracle’s minimums can force a higher NUP count than your actual user total.

Step 4 – How to Calculate Named User Plus Licensing

Calculating NUP requirements involves a step-by-step method. Identify all access paths to the Oracle software. Count every unique user and device using those paths. Include both direct users and all end-users of any connected applications.

Next, apply Oracle’s minimums if your total user count is below the product’s required minimum. Finally, compare the total required NUP licenses to the number of NUP licenses you have to ensure you meet the requirements.

Checklist: Calculation Steps

• ✓ List every Oracle access point (applications, direct logins, integrations)
• ✓ Count all unique users across these (including indirect users)
• ✓ Include non-human accounts and devices in the total
• ✓ Apply product minimums if the count is below Oracle’s threshold
• ✓ Confirm your NUP licenses meet or exceed the required count

Table: NUP Counting Framework

Accurate NUP counting requires knowing every user (human or device) that touches the Oracle system.

Step 5 – Common NUP Compliance Pitfalls

Even with a good process, companies often miscount NUP licenses. Common mistakes include failing to count indirect users, overlooking non-human users, not tracking external third-party access, and ignoring Oracle’s minimum rules. Any of these can lead to under-licensing and surprise costs in an Oracle audit.

Checklist: NUP Pitfalls

• ✓ Not counting users hidden behind middleware or web services
• ✓ Overlooking non-human users (scripts, bots, service accounts)
• ✓ Failing to include external partner or integration users
• ✓ Ignoring Oracle’s minimum license requirements

Table: Pitfall Examples

Most NUP issues stem from missing user groups or misinterpretation of the rules.

Step 6 – NUP in Virtualized and Clustered Environments

Virtualization and clustering can broaden the scope of an Oracle deployment, affecting NUP licensing. If Oracle runs on a cluster of multiple servers, you may need to meet NUP minimums for each server (or processor) in that cluster.

This can multiply the number of licenses required, even if the user population is small. Similarly, if several applications across a cluster use a single Oracle database, all their combined end users must be counted.

Keep track of where Oracle is installed or can run (especially if using VM migration), since infrastructure changes can alter your NUP obligations.

Checklist: Virtualization Considerations

• ✓ Apply NUP minimums to each host or processor in a cluster
• ✓ Count all users across all applications that connect to the Oracle database
• ✓ Define clear boundaries for Oracle installations and monitor any cluster/VM changes
• ✓ Adjust license counts when adding servers or moving Oracle to new hosts

Table: Virtualization Impact on NUP

In virtual or clustered setups, NUP requirements can increase because Oracle’s footprint spans more servers and users.

Step 7 – NUP in Cloud and Hybrid Environments

Cloud deployments change the environment but not the core NUP rules. In a bring-your-own-license (BYOL) cloud scenario, count users the same as on-premises and meet all the usual minimums.

If you use Oracle’s cloud subscription services (without BYOL), NUP licensing doesn’t apply to that service since licensing is built into the subscription. In hybrid setups (some systems on-prem and others in the cloud), track the total number of users across both to ensure you stay within your licensed count. Monitor cloud usage via logs if possible.

Checklist: Cloud NUP Considerations

• ✓ BYOL inthe cloud follows the same NUP counting and minimum rules as on-prem
• ✓ Pure cloud subscription services don’t use NUP, but consider interactions with any licensed systems
• ✓ In hybrid setups, track users across on-prem and cloud deployments together
• ✓ Use cloud monitoring tools or logs to watch user counts in cloud instances

Table: NUP in Cloud Scenarios

Moving Oracle to the cloud changes the location but not how you count NUP—always count all users and respect minimums in any environment.

Step 8 – How to Maintain NUP Compliance Over Time

NUP compliance requires ongoing management. Audit Oracle user accounts regularly and remove any that are no longer needed. Evaluate new applications or integrations for any Oracle users they may add before those systems go live.

Update your license records whenever your environment changes or you purchase additional licenses, so you always know your license status. Document how you count users and any assumptions you make. If an audit occurs, these records will show that you’ve been diligent in managing your licenses.

Checklist: NUP Compliance Practices

• ✓ Conduct periodic audits of Oracle users; deactivate unused accounts
• ✓ Evaluate new integrations or applications for impact on Oracle user counts
• ✓ Update license records after any significant changes or purchases
• ✓ Document your counting methods and assumptions for future reference

Table: NUP Compliance Framework

Continuous monitoring and updates are key to staying compliant as your Oracle usage evolves.

5 Expert Recommendations for NUP Licensing

Here are five expert tips for effectively managing Oracle Named User Plus licensing:

• Count direct and indirect users together – Always include all end-users, whether they connect directly or through another application.
• Apply Oracle’s minimums upfront – Know the minimum license counts for your Oracle products and use those as a baseline for compliance.
• Treat bots and devices as users – Service accounts, batch jobs, and devices all count as named users. Include them in your license calculations.
• Review integration logs regularly – Monitor logs to detect new user activity from integrated systems, and adjust your counts accordingly.
• Document assumptions for audits – Keep records of how you counted users and what was included. This documentation helps you justify your licensing during an audit.

NUP compliance relies on complete visibility and disciplined tracking of all users who access your Oracle systems.

Read about our Oracle License management services

Do you want to know more about our Oracle services?

Please enable JavaScript in your browser to complete this form.

Name *

First

Last

Email *

Message *

Submit