Oracle Named User Plus Licensing:
- Licenses individual authorized users/devices (no concurrency).
- Includes indirect (multiplexed) access users.
- Requires a minimum of 25 NUP licenses per processor license.
- Suitable for limited, defined user populations.
- Example: 2 processor licenses × 25 minimum = 50 NUP licenses, even if the actual users are fewer.
- Maintain accurate user/device records to ensure compliance and avoid costly audit penalties.
Oracle Named User Plus Licensing
Oracle Named User Plus (NUP) licensing is a user-based licensing model widely used by organizations with defined or limited numbers of users.
Unlike Processor licensing, which covers unlimited user access, the Named User Plus model licenses individual users or devices authorized to access Oracle software.
This article explains Oracle Named User Plus licensing, providing detailed examples and practical insights.
Oracle Named User Plus Licensing: Definition
What is Oracle Named User Plus Licensing?
Oracle defines a Named User Plus as any individual or device authorized to access Oracle software, directly or indirectly, regardless of actual usage frequency. Each named user or device must be individually licensed—no concept of concurrency or simultaneous usage exists.
This licensing metric requires careful user/device tracking to ensure compliance, particularly because Oracle sets minimum licensing requirements based on underlying processor counts.
Read about Oracle Processor Licensing.
Authorized User or Device Explained
Who Counts as a Named User Plus?
- Any user or device that can potentially access the Oracle software, whether or not it actively does.
- Users include internal staff, contractors, partners, or external individuals authorized for access.
- Devices include servers, desktops, mobile devices, or IoT devices with access rights to Oracle databases or middleware.
Examples of Named User Plus Licensing:
- Internal HR Application:
100 employees have user accounts to log into the Oracle database-powered HR system.
Licenses required: 100 Named User Plus licenses. - External Portal with Named Access:
50 customers can log into an Oracle Database-powered portal, even if only 10 use it frequently.
Licenses required: 50 Named User Plus licenses.
Oracle NUP Licensing Minimums (Per Processor)
Understanding Oracle’s Minimum Requirements
Oracle imposes a minimum Named User Plus licensing requirement tied directly to the number of processor licenses required by the hardware configuration. This minimum applies regardless of the actual number of users authorized.
The minimum is defined as follows for Oracle Database Enterprise Edition:
- Minimum of 25 Named User Plus licenses per processor license.
This means organizations must purchase at least 25 NUP licenses per processor license, even if fewer than 25 users or devices access the software.
Example of NUP Minimum Calculation:
- Server configuration:
- 2 Intel Xeon CPUs (8 cores each) = 16 cores total.
- Oracle core factor (Intel Xeon) = 0.5
- Processor licenses required:
- 16 cores × 0.5 core factor = 8 processor licenses.
- Minimum NUP required:
- 8 processor licenses × 25 NUP per processor = 200 Named User Plus licenses minimum.
Practical Scenario Applying the Minimum:
- Scenario A (Actual users below minimum):
The organization has only 150 actual authorized users. Oracle’s minimum (200) still applies.
Licenses required: 200 NUP licenses. - Scenario B (Actual users exceed minimum):
The organization has 250 actual authorized users.
Licenses required: 250 NUP licenses (actual count exceeds minimum).
Read about Oracle Database Options Licensing.
Licensing Indirect and Multiplexed Users
Indirect User Licensing
Oracle licensing rules require counting indirect access. An indirect user is someone accessing Oracle software via another application or middleware, not directly logging into the Oracle software itself.
Examples of indirect users:
- Users accessing Oracle databases through custom-built web applications.
- Users accessing Oracle via reporting tools (e.g., Tableau) that interact with the database.
Multiplexing and Licensing Implications
Multiplexing occurs when users access Oracle software indirectly via another application. Oracle explicitly prohibits multiplexing to circumvent user licensing counts. All indirect users must be licensed as Named User Plus.
Practical Example of Multiplexing Licensing:
- A web application connects to Oracle Database EE to display data.
- 300 users log into the web application; only 10 have direct Oracle access.
- All 300 users must be licensed due to indirect access, not just the 10 direct users.
When to Use Oracle Named User Plus Licensing
Appropriate Scenarios for NUP Licensing
Named User Plus licensing fits organizations or scenarios with:
- Defined and limited user groups or small-to-medium scale databases.
- Internal applications with clearly defined and stable user bases.
- Applications with easy-to-monitor and manageable user access.
Examples of Suitable NUP Scenarios:
- Internal HR, CRM, or ERP systems are used exclusively by a limited number of employees.
- Specialized analytical applications are accessible to a specific team or department.
- External-facing applications where each user is explicitly defined and authorized individually.
Oracle NUP Licensing: Best Practices
Maintain Accurate User Records
- Regularly audit user access lists, removing inactive or unauthorized accounts promptly.
- Document all authorized users and devices that require licensing.
Understand and Comply with Minimum Licensing Requirements
- Regularly verify hardware configuration to calculate Oracle’s required minimum NUP licenses.
- Always license at least the minimum, even if fewer actual users exist.
Monitor Indirect Access Closely
- Identify all indirect and multiplexed access scenarios proactively.
- Ensure indirect users are included in all NUP licensing calculations.
Common Mistakes in Named User Plus Licensing
Underestimating User Counts
- Forgetting to count indirect users or devices accessing Oracle software.
- Misunderstanding Oracle’s definition of “authorized” users versus actual concurrent users.
Ignoring Oracle’s Minimum Requirements
- Assuming actual user counts below Oracle’s minimum will be acceptable.
- Always factor in minimum licensing requirements based on processors, regardless of user count.
Poor Record-Keeping of Authorized Users/Devices
- Lack of clear documentation often leads to disputes during Oracle audits.
- Maintain clear records and regularly update user/device authorization logs.
Licensing Examples and Calculations: Practical Illustration
Scenario 1: Internal CRM Database (Below Minimum Users)
- Hardware Configuration:
- There are 2 AMD EPYC CPUs, each with eight (16 cores total).
- Core factor = 0.5 → 16 × 0.5 = 8 processor licenses.
- Minimum NUP required:
- 8 processors × 25 NUP minimum = 200 licenses.
- Actual authorized users: 120
- Licenses required: Must license minimum (200 NUP licenses).
Scenario 2: Departmental Analytics Database (Above Minimum Users)
- Hardware Configuration:
- 2 Intel Xeon CPUs, 16 cores total.
- Core factor = 0.5 → 8 processor licenses required.
- Minimum NUP required: 8 processors × 25 NUP = 200 licenses.
- Actual authorized users: 280
- Licenses required: Must license actual (280 NUP licenses).
Final Recommendations for Oracle NUP Licensing
Oracle Named User Plus licensing is cost-effective when user populations are clearly defined and stable. Organizations must carefully manage their authorized user base, consistently comply with Oracle’s processor-based minimum requirements, and regularly audit user and device access to avoid compliance risks.
By following these guidelines, organizations ensure Oracle NUP licensing aligns effectively with their business requirements, minimizing unnecessary licensing expenses and simplifying software asset management.
