Oracle Licensing Vocabulary: 100 Terms Every Enterprise Buyer Must Know

A metric used for Oracle Fusion Cloud applications (ERP, HCM, SCM, CX) that charges per individual who uses a specific application module. Unlike Named User Plus, Application User metrics apply to distinct roles (Employee, Manager, Executive) at differentiated price points. Buyer implication: Your total Fusion Cloud user count is almost always higher than your NUP count on equivalent on-premise applications — Oracle's migration proposals exploit this systematically.

The ability to use on-premise Oracle license entitlements in a cloud environment. Oracle recognises BYOL for OCI, AWS, and Azure, but with different counting rules for each. Buyer implication: BYOL on AWS and Azure typically requires physical host-level licensing unless Dedicated Hosts are used — a trap that catches most enterprises moving Oracle Database to public cloud.

A multiplier published in Oracle's Core Factor Table that reduces the number of licenses required per physical processor core for certain processor families. Intel Xeon cores use a 0.5 factor (0.5 licenses per core), IBM POWER8 cores use 1.0. Buyer implication: Oracle's LMS audit scripts collect the actual processor type from target servers — if you have entered a different processor type in your license records than is actually installed, the audit will find a discrepancy. See our Core Factor Table guide.

Oracle Java SE's subscription metric, introduced in 2023. Charges based on the total number of employees in the organization, regardless of how many actually use Java SE. Buyer implication: A 50,000-employee organization pays the same Java SE subscription cost whether it has 100 Java SE deployments or 5,000. The metric is organization-wide, not deployment-specific — making it one of Oracle's most aggressive pricing innovations.

An Oracle license that grants the right to use all features and functionality of the licensed product. Distinguished from restricted-use licenses (e.g., technology licenses bundled with applications) that limit usage to specific integration scenarios. Buyer implication: Restricted-use licenses bundled with ERP applications cannot be used for standalone deployment — using them outside the permitted scope triggers back-license claims.

Oracle Database Enterprise Edition requires a minimum of 25 Named User Plus licenses per processor. Even if fewer than 25 users access the database, the 25-NUP minimum applies. Buyer implication: For databases accessed by only a handful of users, the processor metric may actually be cheaper than NUP once the 25-NUP minimum is factored in — this calculation should be modelled before purchasing.

An Oracle licensing metric that requires a separate license for each individual authorized to use the software, including users who access the software indirectly through third-party applications. The "Plus" refers to the inclusion of both direct and indirect users. Buyer implication: Indirect access — where users access Oracle Database through non-Oracle applications — is the most commonly exploited NUP gap. Every user of a system that queries Oracle Database in the background potentially requires a NUP license.

Oracle's primary database licensing metric. Calculated as: (number of physical processor cores) × (Core Factor). For Oracle Database Enterprise Edition on Intel, this is typically: cores × 0.5. Buyer implication: All cores in the physical server must be licensed if the server runs Oracle software — not just the cores assigned to the Oracle VM. Virtualisation using soft partitioning (VMware, Hyper-V) does not limit the Oracle license scope to the assigned vCPUs.

A technology license bundled with an Oracle application (e.g., Oracle Database licenced with PeopleSoft) that restricts usage to the specific application it was bundled with. Buyer implication: Running general-purpose workloads on Oracle Database licenced as a restricted-use bundle with PeopleSoft is non-compliant. Oracle's LMS scripts check for restricted-use databases running workloads outside the permitted application scope.

Oracle's annual support offering, also called Oracle Support or Oracle Premium Support. Priced at 22% of net license value per year. Includes technical support, software updates, bug fixes, and security patches. Buyer implication: SULS costs escalate permanently — if you paid $5M for licenses, you will pay $1.1M per year indefinitely unless you reduce support through negotiation or third-party support.

The unique identifier assigned to each Oracle support contract. Used to access Oracle's support portal, log service requests, and download software. Buyer implication: Each CSI is linked to specific license entitlements. If you have multiple Oracle agreements from different purchases or acquisitions, you may have multiple CSIs that need to be consolidated for accurate entitlement management.

A multi-year, multi-product Oracle agreement that consolidates licenses, support, and sometimes cloud services under a single commercial arrangement with agreed pricing across the agreement term. Buyer implication: Oracle's Oracle agreement proposals consistently over-price included products. Oracle's first Oracle agreement offer should never be accepted without independent benchmarking — the gap between Oracle's initial proposal and achievable transaction pricing is typically 30–50%.

Oracle's master contractual document that governs all transactions between Oracle and a customer. Establishes audit rights, liability caps, governing law, and general terms. Individual Order Forms attach to and are governed by the Master Agreement. Buyer implication: Oracle's standard Master Agreement includes audit rights that are broader than most customers realize. Every Master Agreement should be reviewed by counsel with Oracle licensing expertise before signing.

The transaction-specific document that defines the products, metrics, quantities, and prices for a particular Oracle purchase. Order Forms reference the Master Agreement for general terms. Buyer implication: Order Forms contain the definitive license definition for what you purchased. Discrepancies between what sales told you verbally and what the Order Form says are resolved in Oracle's favor — always read the Order Form before signing.

An unlimited license agreement with no expiry date — distinguishing it from a standard ULA which has a defined term (typically 3–5 years). Oracle rarely offers PULAs and prices them significantly higher than term ULAs. Buyer implication: A PULA eliminates the ULA certification requirement and provides permanent unlimited deployment rights. For organizations with genuinely unlimited deployment needs, a PULA may provide better long-term economics than a succession of term ULAs — but the negotiation is complex.

The document that defines the Oracle support services included in a support agreement, the support rates, and the support renewal terms. Buyer implication: Support Schedule renewal terms often include automatic escalation provisions. Customers who do not actively negotiate support renewals pay Oracle's listed renewal rate, which includes price increases that compound annually.

An Oracle license agreement specifically covering Oracle technology products (Database, Middleware) as distinct from Oracle application licenses. Buyer implication: Technology licenses purchased separately from Oracle applications carry full-use rights. Distinguishing TLA-purchased licenses from restricted-use licenses bundled with applications is essential for accurate compliance management.

A fixed-term Oracle agreement granting unlimited deployment rights for specified Oracle products within specified parameters (entity, territory, metric). At the end of the ULA term, the customer certifies deployed quantities, which become their perpetual named license entitlement. See the Oracle ULA Guide for full details. Buyer implication: ULA economics are highly favorable during the term — deploy as much Oracle software as the business needs without incremental license cost. The certification process determines the perpetual license value captured — rigorous pre-certification planning is essential.

A formal statement from a customer confirming their Oracle license position, typically requested at the end of an Oracle ULA term or during a compliance review. Buyer implication: A compliance declaration is a legal document. Submitting an inaccurate compliance declaration — even unintentionally — has contractual consequences. Declarations should only be made after independent verification of the license position.

Oracle's internal advisory team that conducts compliance reviews with customers. GLAS positions its work as advisory rather than audit — but every piece of information shared with GLAS feeds Oracle's commercial intelligence about the customer's compliance position. Buyer implication: Treat GLAS engagement exactly as you would treat an LMS audit. Do not share Oracle estate information with GLAS without independent advisers present. See our GLAS vs LMS guide.

Oracle's dedicated software license audit organization. LMS conducts formal compliance audits under the contractual audit rights in the Oracle Master Agreement. LMS auditors are trained specialists whose primary function is to identify compliance gaps and convert them into commercial claims. Buyer implication: An LMS audit notification is not a routine administrative process — it is the opening move in a commercial negotiation. Engage independent Oracle audit defense support immediately upon receiving an LMS notification.

SQL scripts provided by Oracle's LMS team to collect database configuration, feature usage, and user data from Oracle Database instances. Customers are typically asked to run these scripts during an audit and return the output to Oracle. Buyer implication: You are not obligated to run Oracle's scripts without reviewing what they collect. Independent analysis of LMS script output before submitting to Oracle frequently identifies data that should be challenged or contextualised. See our LMS scripts guide.

A simplified Oracle compliance review process — shorter in scope than a full LMS audit — often proposed by Oracle's account team as an alternative to a formal LMS audit. Buyer implication: Review Lite is not necessarily less commercially aggressive than a full LMS audit. The "lite" refers to Oracle's resource investment, not the potential financial outcome for the customer.

Oracle's primary database audit data collection tool. USMM is a set of scripts that collects CPU/core counts, database option feature usage, and user data from Oracle Database instances. USMM output is the primary evidence base for Oracle LMS audit claims against Oracle Database customers. Buyer implication: USMM collects data on every Oracle Database option feature that has been accessed — including Diagnostics Pack, Tuning Pack, and Advanced Security — regardless of whether the access was intentional. USMM output should be reviewed by an independent Oracle licensing expert before submission to Oracle.

Oracle's premium standby database feature that allows the standby database to be open for read access while receiving redo log data from the primary. Separately licensed from Oracle Database Enterprise Edition. Buyer implication: If you use your DR standby database for reporting or testing, you are using Active Data Guard — which requires an ADG option license on the standby nodes. Physical standby used purely for failover (no open-read access) does not require ADG licensing.

An Oracle Database Enterprise Edition option that includes Transparent Data Encryption (TDE), Oracle Data Masking, and other security features. Separately licensed at Processor or NUP metric. Buyer implication: Enabling TDE for GDPR, HIPAA, or PCI DSS compliance without licensing ASO is non-compliant. ASO is one of the most frequently unlicensed Oracle Database options — particularly in healthcare and financial services environments where encryption is mandated by regulation.

An Oracle Database option that implements privileged user access controls, preventing DBAs from accessing application data. Separately licensed. Buyer implication: Oracle's USMM scripts check the DV_ENABLED parameter. If Database Vault is enabled — even if not actively used — Oracle's LMS team will include it in the compliance claim.

An Oracle Database Enterprise Edition option that includes Automatic Workload Repository (AWR), Active Session History (ASH), and Oracle Enterprise Manager diagnostics features. Separately licensed. Buyer implication: Accessing AWR data, viewing ASH reports, or using Oracle Enterprise Manager's performance diagnostics without a Diagnostics Pack license is non-compliant. Oracle's USMM scripts detect AWR access — this is one of the most commonly identified compliance gaps across all sectors. See our Diagnostics Pack guide.

Physical or firmware-level partitioning of server hardware that Oracle recognises as limiting Oracle license requirements to the partitioned cores. Includes IBM LPAR (approved configurations), Oracle VM (OVMS), and Oracle Solaris Zones (approved). Buyer implication: Hard partitioning is the only virtualisation technology Oracle accepts for limiting processor license scope. VMware, Hyper-V, and KVM are soft partitioning — they do not limit Oracle license obligations. See our soft vs hard partitioning guide.

Oracle Database's in-memory column store feature, enabling analytical query acceleration within the transactional database. Separately licensed from Oracle Database Enterprise Edition. Buyer implication: Enabling the In-Memory column store without licensing the In-Memory Option is non-compliant. The parameter INMEMORY_SIZE > 0 triggers the In-Memory Option requirement that Oracle's LMS scripts detect.

Oracle Database's Container Database (CDB) architecture, allowing multiple Pluggable Databases (PDBs) to share a single set of background processes. The number of PDBs supported without an additional license varies by Oracle Database edition and version. Buyer implication: Oracle Database 19c Enterprise Edition supports up to 3 PDBs without the Multitenant option. More than 3 PDBs requires a Multitenant license. Many organizations are running more than 3 PDBs under Enterprise Edition without this license. See our Multitenant licensing guide.

Oracle Database's table and index partitioning feature, allowing large tables to be divided into manageable segments. Separately licensed from Oracle Database Enterprise Edition. Buyer implication: Partitioning is widely used in Oracle Database environments and is one of the most commonly unlicensed options. Using CREATE TABLE ... PARTITION BY or any partitioned table triggers the Partitioning Option license requirement that Oracle's LMS scripts detect.

Oracle Database's clustered database option, enabling multiple database instances on different servers to share a single database. Separately licensed at Processor metric on all nodes in the cluster. Buyer implication: RAC is one of Oracle's most expensive options and one of the most mis-licenced — particularly where organizations have added cluster nodes without purchasing additional RAC option licenses for the new nodes.

Oracle Database Standard Edition 2 — Oracle's entry-level database edition, restricted to servers with a maximum of 2 populated sockets and a maximum of 16 CPU threads. Does not include RAC, most EE Options, or advanced features. Significantly cheaper than Enterprise Edition. Buyer implication: Many Oracle Database deployments that are currently licenced as Enterprise Edition could be SE2 — eliminating the EE premium and the option licensing complexity. The SE2 option should be evaluated for every non-critical database in the Oracle estate.

Virtualisation technologies (VMware, Hyper-V, KVM, Docker) that Oracle does not recognize as limiting processor license scope. Oracle requires licenses for all physical cores on a server running Oracle software in a soft-partitioned environment, regardless of the number of virtual CPUs assigned. Buyer implication: Running Oracle Database on VMware is Oracle's biggest compliance trap. The entire physical host's processor count applies to the Oracle license requirement, not just the VM's vCPU count. VMware virtualisation is responsible for more Oracle compliance gaps than any other single technical configuration.

Oracle Database's encryption-at-rest feature, part of Oracle Advanced Security Option. Encrypts data at the tablespace or column level. Required for GDPR, HIPAA, PCI DSS, and other regulatory compliance in Oracle Database environments. Buyer implication: TDE requires ASO licensing. Many organizations enable TDE for regulatory compliance without purchasing ASO — creating an Oracle compliance gap that is detected during LMS audits and can result in multi-million-dollar back-license claims.

An Oracle Database Enterprise Edition option that includes SQL Tuning Advisor, SQL Access Advisor, and other performance tuning features within Oracle Enterprise Manager. Separately licensed. Buyer implication: Oracle's USMM scripts detect Tuning Pack feature access. Using Oracle Enterprise Manager's SQL Tuning Advisor — often done by DBAs routinely for performance analysis — without a Tuning Pack license triggers a compliance claim.

The mechanism for using existing on-premise Oracle perpetual licenses in cloud environments. Rules differ by cloud provider: OCI permits CPU-level BYOL; AWS and Azure require physical host-level licensing unless Dedicated Hosts are used. Buyer implication: Organizations migrating Oracle Database to AWS or Azure under BYOL without Dedicated Hosts are non-compliant with Oracle's licensing policy — but Oracle's account teams rarely highlight this requirement proactively.

Oracle's Infrastructure as a Service cloud platform. Competes with AWS and Azure for Oracle workloads. Offers BYOL at the OCPU level (each OCPU = 1 processor license), which is more favorable than AWS/Azure counting rules for Oracle Database workloads. Buyer implication: For Oracle Database BYOL workloads, OCI's licensing economics are genuinely more favorable than AWS or Azure. The BYOL advantage should be modelled carefully when evaluating cloud platform choices for Oracle workloads. See our BYOL to OCI guide.

Oracle Cloud Infrastructure's flexible consumption model, where a single pool of credits can be applied across all OCI services. Universal Credits contracts provide discounted OCI rates in exchange for a committed annual spend. Buyer implication: Universal Credits discounts are highly negotiable. Oracle's initial Universal Credits proposals significantly under-price the discount relative to achievable transaction rates. Our OCI Universal Credits guide covers the negotiation framework.

Oracle's program that allows OCI spend to earn credits toward Oracle on-premise support renewal costs. Enterprises spend OCI credits to reduce the 22% annual Oracle support cost on their on-premise estate. Buyer implication: Support Rewards can be a genuine cost reduction mechanism for organizations with both OCI workloads and large on-premise Oracle support costs. However, the Support Rewards program creates commercial dependency on OCI — evaluate the full commercial picture before committing to OCI primarily for Support Rewards benefits. See our Support Rewards guide.

An Oracle LMS audit finding that the customer has used Oracle software without the corresponding license, resulting in a demand to purchase the licenses retroactively — typically at Oracle's current list price without discounts. Buyer implication: Oracle's initial back-license claim after an audit is almost always overstated. Every element of the claim — the scope, the metric, the quantity, and the price — is negotiable with the right evidence and commercial approach. Our audit defense service routinely reduces Oracle's initial back-license claims by 50–80%.

Transaction pricing data from comparable Oracle deals, used to assess whether Oracle's commercial proposal for a specific customer is consistent with market pricing. Oracle prohibits customers from disclosing Oracle pricing in most contract terms — but independent advisers with access to benchmark data can negotiate from an evidence-based position. Buyer implication: Oracle's initial proposal is never the market price. Benchmark data from comparable transactions is the most powerful negotiation tool available to enterprise Oracle buyers.

The difference between the Oracle licenses a customer holds and the Oracle software usage the customer has deployed. A positive compliance gap means the customer is under-licenced (compliance risk). A negative gap means the customer is over-licenced (cost optimization opportunity). Buyer implication: Most enterprises have compliance gaps in both directions simultaneously — some products are under-licenced, others are over-licenced. Independent compliance review maps both and prioritises remediation.

The percentage reduction from Oracle's published list price (Oracle Price List / CPQ) at which licenses and support are purchased. Oracle's list prices are set substantially above market transaction pricing — discounts of 60–90% from list are normal for enterprise transactions. Buyer implication: Oracle's list price is not a meaningful anchor for commercial negotiations. The relevant comparator is Oracle's typical transaction discount for similar products, quantities, and deal structures — which independent advisers provide through benchmark data.

Access to Oracle software by end users who interact with a non-Oracle application that, in the background, queries or updates Oracle Database. Under Oracle's licensing terms, indirect users must be licensed under the Named User Plus metric. Buyer implication: Indirect access is Oracle's single largest source of audit claims in enterprise environments. ERP and business application users who never directly interact with Oracle Database may still require NUP licenses because their application accesses Oracle in the background. See our indirect access guide.

The price paid for Oracle software licenses, net of discounts. Oracle Support (22%) is calculated against NLV, not Oracle's list price. Buyer implication: Maximizing upfront license discounts reduces the annual support cost permanently. A 10% improvement in upfront license discount reduces the 22% annual support cost by 10% every year for the life of the support obligation.

A periodic reconciliation of Oracle software usage against license entitlements, used to identify and purchase licenses for any gap between deployment and entitlement. True-up processes are used in some Oracle Oracle agreement structures. Buyer implication: Unlike a ULA, a true-up agreement does not provide unlimited deployment rights — it requires payment for any overage identified in the true-up cycle. True-up agreements should be evaluated carefully before entering to ensure the commercial exposure is bounded.

See Licensing Metrics section. The metric that charges Java SE subscription costs based on total organisational employee count. Introduced in January 2023 as a replacement for the previous per-processor and per-user metrics. Buyer implication: Organizations that have not renegotiated their Java SE subscription since 2023 may be paying under the old per-processor metric while Oracle's compliance team is applying the Employee Metric to new deployments.

The open-source reference implementation of Java SE, available at no cost under the GNU General Public License. OpenJDK does not carry Oracle's Employee Metric or any license cost. Commercial distributions based on OpenJDK (Azul, Amazon Corretto, Eclipse Temurin) provide support and long-term update commitments. Buyer implication: Migrating from Oracle JDK to OpenJDK-based distributions eliminates Oracle Java SE subscription cost entirely. For most enterprise server-side Java deployments, this is technically low-risk and commercially high-value. See our OpenJDK vs Oracle JDK guide.

Oracle's commercial distribution of Java SE, requiring a subscription for production use since Oracle Java SE 8 Update 211 (April 2019). Post-2023, Oracle JDK subscriptions use the Employee Metric. Buyer implication: If your organization is running Oracle JDK in any production environment — including in vendor-supplied applications — you have a Java SE subscription obligation. The size of that obligation under the Employee Metric depends on your total employee count, not the number of JDK deployments.

Oracle's annual subscription model for Java SE, including Oracle JDK updates, security patches, and commercial support. Priced on the Employee Metric at a per-employee rate. Buyer implication: Java SE subscription pricing is negotiable. Oracle's standard Java SE subscription pricing is not the achievable market rate for enterprise buyers — particularly for organizations that can credibly demonstrate an OpenJDK migration capability as an alternative.

The process at the end of a ULA term where the customer declares the number of Oracle units deployed. The certified deployment quantity becomes the customer's perpetual license entitlement after the ULA. Buyer implication: The certification is the moment where the ULA's commercial value is crystallised. Every unit deployed and counted at certification becomes a permanently paid-for perpetual license. Pre-certification deployment maximisation and documentation are essential — poorly prepared certifications consistently under-capture the value of ULA deployments. See our ULA Certification guide.

The formal document submitted to Oracle at the end of a ULA, detailing the number and type of Oracle units deployed within the ULA scope. Oracle reviews the certification report and may challenge the deployment methodology. Buyer implication: Oracle's response to a certification report should be expected to include challenges. Every deployment claimed in the certification report requires supporting documentation — server configurations, deployment records, and technical evidence that support the claimed unit count.

The practice of deploying as much Oracle software as the business needs during a ULA term — to maximize the value of the unlimited deployment rights — before the certification period. Buyer implication: ULA deployment maximisation is legitimate and expected. The ULA's commercial value is proportional to the volume of deployments captured at certification. Customers who under-deploy during the ULA term and certify minimal quantities receive minimal value from the unlimited deployment rights they paid for.

The decision framework for what happens at the end of a ULA term — certification (converting deployments to perpetual licenses), renewal (extending the ULA for another term), or expansion (certifying and entering a new broader ULA). Buyer implication: The exit strategy decision should be made at ULA commencement, not at ULA expiry. The economics of certification vs renewal depend on deployment trajectory, future business growth, and Oracle's pricing for the renewal. Our ULA Advisory service models exit strategy options from the start of every engagement.

The products, metrics, entities, and territories covered by a ULA. Only the products, users, and deployments within the defined ULA scope are covered by the unlimited license rights. Buyer implication: ULA scope limitations are a frequent source of dispute at certification. Deployments of products not explicitly included in the ULA, or deployments by entities outside the defined ULA entity scope, do not count toward the ULA certification — and may constitute unlicensed Oracle use. See our ULA scope guide.