Oracle Named User Plus (NUP) License: Definition and Counting Users
An Oracle Named User Plus (NUP) license allows specific, identifiable users or devices to access Oracle Database software. Licensing costs depend on the number of distinct users or devices accessing the database.
This article covers:
- What is a Named User Plus (NUP) license?
- How to accurately count users for licensing
- Oracle’s minimum user licensing requirements
- Practical examples to illustrate counting and minimums
Read more Oracle Database Licensing FAQs.
What is an Oracle Named User Plus (NUP) License?
A Named User Plus license is based on the number of unique users or devices authorized to access an Oracle database.
Key characteristics:
- Licenses are user- or device-specific.
- Each named user or device requires an individual license.
- Suitable for databases with a limited or easily identifiable user base.
How to Count Users for Named User Plus Licensing
Oracle counts each unique user or device separately.
Important considerations:
- Direct Users: Any individual directly logging into the database requires a license.
- Indirect Users (Multiplexing): Users accessing data through an application or middleware must have a separate license, even when using a shared connection.
- Devices: Non-human-operated devices (e.g., automated systems, sensors, batch-processing servers) accessing the database independently must also be counted.
Read Oracle Licensing: Named User Plus vs. Processor – Which to Choose?.
Oracle’s Minimum Named User Plus Licensing Requirements
Oracle enforces minimum user licensing per processor:
- Enterprise Edition (EE):
- Minimum of 25 Named Users per Oracle Processor license.
- Standard Edition 2 (SE2):
- There is typically a minimum of 10 Named Users per server (SE2 is licensed by sockets, with a maximum of 2 sockets per server).
Key rule:
- The actual number of users is licensed if it exceeds the minimum requirement.
- You must still meet Oracle’s minimum user count if the actual count is lower.
Example: Counting Users for Enterprise Edition (EE)
- Server Configuration:
- It requires two processor licenses (based on CPU cores and core factor).
- Minimum Users Required:
- 2 Processor licenses × 25 Named Users per Processor = 50 Named Users.
Scenario 1:
- You have 40 actual users accessing the database.
- Oracle still requires licensing 50 Named Users as the minimum.
Scenario 2:
- You have 70 actual users.
- You must license all 70 Named Users, exceeding the minimum.
Read Oracle Database Processor Licensing: Definition and Calculation.
Example: Counting Users for Standard Edition 2 (SE2)
- Server Configuration:
- Single server with up to 2 sockets.
- Minimum Users Required:
- The minimum is typically 10 Named Users per server.
Scenario 1:
- You have 7 actual users.
- You still must license at least 10 Named Users.
Scenario 2:
- You have 25 actual users.
- You must license all 25 Named Users.
Oracle NUP Licensing Checklist
✅ Identify all direct and indirect database users.
✅ Include all non-human devices that access the database independently.
✅ Check the minimum user licensing based on your database edition (EE or SE2).
✅ If actual users exceed the minimum license actual count.
✅ If actual users are fewer, license Oracle’s minimum requirement.
Common Misunderstandings Corrected
- Misconception: “Shared connections require only one license.”
- Reality: Each user accessing data through shared connections (multiplexing) must have their Named User Plus license.
- Misconception: “Fewer actual users mean fewer licenses always.”
- Reality: Oracle enforces minimum Named User Plus licenses regardless of user count.
Practical Summary of NUP Licensing
| Edition | Minimum Required Users | Licensing Rule |
|---|---|---|
| Enterprise Edition (EE) | 25 Named Users per Processor license | License actual users if greater, minimum otherwise. |
| Standard Edition 2 (SE2) | 10 Named Users per server | License actual users if greater, minimum otherwise. |
Conclusion: Oracle Named User Plus Licensing
Oracle’s Named User Plus licensing model requires careful counting of every unique individual and device authorized to use the database, respecting minimum user licensing rules based on edition and processors. Understanding these guidelines ensures accurate licensing and avoids compliance risks.
