Free white paper: the NUP optimisation toolkit used by our team in 500+ Oracle engagements — covering NUP minimum rules, user count audit methodology, NUP vs. Processor metric decision framework, and step-by-step processes to reduce over-licensed Named User Plus positions by 30–60%.
Six chapters of practical frameworks, decision tools, and forensic audit methodology for eliminating unnecessary Named User Plus licences — without creating new compliance exposure.
The precise Oracle definition of a Named User Plus — every individual who can access Oracle software, directly or indirectly, including batch users, application service users, and external users accessing via web applications. The four categories of users Oracle's LMS team always looks for that enterprises routinely miss, and why "active users" is not the same as "Named Users" under Oracle's rules.
Oracle's product-specific NUP minimum rules — Database EE requires a minimum of 25 NUP per Processor, SE2 requires 10 NUP per server. How these minimums create traps when you have small user counts on high-core servers, and the specific calculation Oracle uses during LMS audits to determine whether your minimum NUP count is met. The three scenarios where the minimum rule costs more than Processor licensing.
The quantitative framework for deciding whether Named User Plus or Processor licensing is the lower-cost option for each Oracle database deployment. Variables: core count, active user count, application type (OLTP vs. batch vs. reporting), and Oracle product options in use. The crossover point where Processor metric becomes cheaper, and how to use this analysis to restructure your Oracle estate to the lowest-cost metric mix.
The step-by-step methodology our team uses to conduct an independent NUP user count audit: extracting DBA_USERS from each Oracle database, identifying system and application-level accounts, distinguishing "can access" from "does access," and reconciling the database user list against HR and Active Directory data. How to identify and remove inactive users, service accounts, and application middleware accounts that inflate your NUP count.
The seven types of phantom NUP positions that inflate enterprise Oracle licence costs: departed employees not removed from Oracle, test and development accounts mirrored in production, batch processing accounts incorrectly counted as NUPs, shared application login accounts, monitoring tool accounts, report extraction accounts, and integration middleware users. How to challenge each category with Oracle during licence compliance discussions.
The 90-day NUP optimisation process: user census, metric analysis, compliance verification, and renegotiation with Oracle. How to present NUP reduction findings to Oracle in a format that protects you from counter-audit risk, the commercial discussions to have at renewal time, and the licence contract amendments needed to formalise NUP count reductions. Case study: manufacturing company reduces NUP count by 45%, saving $2.8M annually.
From NUP definition to 90-day optimisation roadmap — everything needed to right-size your Named User Plus estate.
Evidence-based findings from real NUP optimisation engagements across 500+ Oracle accounts.
"In a typical enterprise Oracle environment with 500 licensed Named User Plus positions, we find on average 180–220 user accounts that don't qualify as Named User Plus under Oracle's own rules — departed employees, unused service accounts, monitoring tools, and test accounts replicated from production. Removing these positions, with proper documentation, reduces the annual Oracle Support bill by $180,000–$220,000 without any change to the actual user population."
"The NUP vs. Processor crossover point for Oracle Database EE depends entirely on your server's core count and the Core Factor Table. A 4-socket server with 20 cores per socket — 80 total cores at 0.5 Core Factor — requires 20 Processor licences. The NUP minimum for 20 Processors is 500 Named User Plus. If your actual user count is under 500, NUP licensing is cheaper. Above 500 authenticated users, Processor licensing wins. Most enterprises have never done this calculation per server."
"Oracle's LMS team counts batch users — automated processes that connect to Oracle Database under a service account — as Named User Plus if the service account was created for that purpose. We challenge this in every engagement. Where the batch process connects via an application account shared across multiple functions, Oracle's own licensing policy supports treating it as a single Named User Plus, not multiple. The difference can be hundreds of phantom NUP positions across a large Oracle estate."
Our licence optimisation practice delivers independent NUP audits with the methodology in this toolkit — identifying phantom positions, running NUP vs. Processor analysis, and managing the commercial process with Oracle. Buyer-side only. Not affiliated with Oracle Corporation. View our case studies to see results from similar engagements.
Get a Confidential NUP AssessmentThe complete framework for auditing, right-sizing, and renegotiating Oracle Named User Plus licensing — built from 500+ Oracle engagements and designed to reduce NUP costs by 30–60% without new compliance exposure.
Also see our Compliance Review service for a full independent assessment of your Oracle NUP and Processor licence positions before an LMS audit request arrives.