Oracle Licensing

Oracle Database Licensing Guide

Oracle Database Licensing Works like this

  • Editions: Multiple editions like Standard Edition 2 (SE2) and Enterprise Edition (EE).
  • Metrics: Licensed by Processor or Named User Plus.
  • Processor Licensing: Based on the number of processor cores and Oracle’s core factor table.
  • Named User Plus: Requires licensing for each user or device accessing the database.
  • Environments: Separate licenses for development, test, production, and failover environments.

Table of Contents

Introduction to Software License Agreements

Introduction to Software License Agreements

Before exploring Oracle database licensing, it’s important to understand a software license agreement.

A software license agreement is a contract between a software company and the user. It grants specific rights to use the software while allowing the developer or publisher to retain ownership.

This retained ownership is crucial for controlling future development and quality standards.

Common Licensing Methods

Licenses can be granted in various ways, with the most common methods being:

  • Written and Signed Agreement: A formal contract signed by both parties.
  • Shrinkwrap or Clickwrap Agreement: The user accepts the license terms by opening the software package (shrinkwrap) or clicking a button on a screen (clickwrap).

Oracle’s Licensing Approach

Oracle licenses its software using a combination of written agreements:

  • Oracle Master Agreement (OMA): Details the overarching license rights, ownership, restrictions, warranties, disclaimers, and confidentialities for all Oracle products and services.
  • The Ordering Document specifies the products, license types, number of users, level of support, and any discounts a customer will receive.

When you accept your Ordering Document, you also agree to the terms outlined in the OMA. Oracle’s online store uses a clickable version of the OMA and Ordering Document. For older customers with Software License and Services Agreements (SLSAs), these serve the same function as the OMA.

Rights Granted

Oracle Master Agreement (OMA) and Ordering Documents grant customers specific rights to use Oracle software and receive services. Customers’ rights are limited to those expressly granted, with all other rights reserved by Oracle.

Perpetual vs. Term License

Oracle offers both perpetual and term licenses for its products:

  • Perpetual License: A one-time fee allows continued use of the software as long as the customer complies with the terms of the license agreement.
  • Term License: This allows access and use of the software for a specific period (1 to 5 years). At the end of the term, the user must either stop using the software, extend the term, or purchase new licenses. Term licenses are a percentage of the perpetual license cost, determined by the chosen term length. Since 2021, Oracle has only offered term licenses for a limited range of products.

Summary of Licensing Options

License TypeDurationCost Structure
Perpetual LicenseUnlimitedOne-time fee
Term License1, 2, 3, 4, or 5 yearsPercentage of perpetual fee

Rights Granted by Oracle

Oracle’s Master Agreement and Ordering Documents grant customers specific rights to use Oracle software and receive services. These rights are limited to those explicitly mentioned, with all other rights reserved by Oracle.

Key Points

  • Explicit Rights: Only the rights expressly granted in the agreements are available to customers.
  • Reserved Rights: Oracle retains all other rights in the programs.

Types of Oracle Licenses

Types of Oracle Licenses

Perpetual License

A perpetual license allows the customer to use the software indefinitely, provided they comply with the terms of the agreement. This type of license involves a one-time fee.

Advantages:

  • Long-Term Use: Continued use without additional licensing costs.
  • Cost-Effective: One-time investment.

Term License

A term license permits the use of the software for a specific period, typically 1 to 5 years. After the term expires, the customer must renew the license or cease using the software.

Advantages:

  • Flexibility: Suitable for short-term projects or changing needs.
  • Lower Initial Cost: Smaller upfront investment compared to perpetual licenses.

Example:

Term LengthPercentage of Perpetual License Cost
1 Year20%
2 Years35%
3 Years50%
4 Years65%
5 Years80%

Current Trends

Since 2021, Oracle has limited 1-year term licenses to a few products, reflecting a shift towards more perpetual licensing agreements for long-term customer commitments.

Different Oracle Database Editions

Different Oracle Database Editions

Oracle offers several database editions tailored to meet various business needs. Here’s a breakdown of the key editions available:

Free Version: Oracle Database Express Edition (XE)

  • Cost: Free
  • Features: A lightweight, easy-to-use database, perfect for learning, developing, and deploying small applications.
  • Limitations: Limited to 2 GB of user data, 1 GB of RAM, and a single CPU.

Standard Edition 2 (SE2)

  • Cost: Mid-range
  • Features: Provides a full-featured database for small to mid-sized businesses.
  • Capabilities include basic features such as data replication, security, and performance tuning.
  • Limitations: Limited to 2 CPU sockets on a server, no clustering capabilities.

Enterprise Edition (EE)

  • Cost: Premium
  • Features: Comprehensive, robust, and highly scalable database solution for large enterprises.
  • Capabilities: Advanced features, including data warehousing, advanced security, high availability, and advanced performance tuning.
  • Scalability: Supports unlimited CPU sockets and includes clustering capabilities.

Summary of Editions

EditionCostKey FeaturesLimitations
Oracle Database Express Edition (XE)FreeLightweight, easy-to-use, ideal for learning and small apps2 GB user data, 1 GB RAM, 1 CPU
Standard Edition 2 (SE2)Mid-rangeFull-featured for small to mid-sized businesses2 CPU sockets, no clustering
Enterprise Edition (EE)PremiumAdvanced features for large enterprisesHigher cost

Differences Between Oracle Database Standard Edition 2 and Enterprise Edition

Differences Between Oracle Database Standard Edition 2 and Enterprise Edition

Key Differences

Understanding the differences between Oracle Database Standard Edition 2 (SE2) and Enterprise Edition (EE) is crucial for selecting the right database solution for your organization.

Standard Edition 2 (SE2)

  • CPU and Memory Limitations:
    • Limited to 2 CPU sockets on a server.
    • No support for more than 16 CPU threads.
  • Basic Features:
    • Includes essential features like data replication, data security, and basic performance tuning.
  • Clustering and High Availability:
    • No support for Oracle Real Application Clusters (RAC).
    • Limited high availability features.

Enterprise Edition (EE)

  • CPU and Memory Scalability:
    • Supports unlimited CPU sockets.
    • No restrictions on CPU threads, providing better scalability.
  • Advanced Features:
    • Advanced data warehousing, comprehensive security options, high availability, and superior performance tuning.
  • Clustering and High Availability:
    • Full support for Oracle Real Application Clusters (RAC) for high availability and load balancing.
    • Enhanced disaster recovery options.

Feature Comparison

FeatureStandard Edition 2 (SE2)Enterprise Edition (EE)
CPU SocketsLimited to 2Unlimited
CPU ThreadsLimited to 16No restrictions
Clustering (RAC)Not supportedFully supported
Data WarehousingBasic featuresAdvanced features
Data SecurityBasic securityAdvanced security options
High AvailabilityLimitedComprehensive high availability and disaster recovery
Performance TuningBasic toolsAdvanced performance tuning and optimization

Choosing Between SE2 and EE

Selecting the right edition depends on your organization’s specific needs:

  • Standard Edition 2 (SE2) is ideal for small to midsize businesses with limited CPU and high availability requirements.
  • Enterprise Edition (EE): Suitable for large enterprises needing advanced features, scalability, and comprehensive high-availability solutions.

Named User Plus Metric

Named User Plus Metric

The Named User Plus (NUP) metric is used in environments where users can be identified and counted. It includes both human users and non-human-operated devices. Here’s a detailed look at how it works:

Key Points

  • Human and Non-Human Users: All human users and non-human-operated devices accessing the program must be licensed.
  • Examples of Non-Human Devices: Non-human devices can include temperature monitoring devices. If a person operates the device, that person also needs a license.

Licensing Requirements

  • Human Users: Anyone accessing the software, directly or indirectly, must be licensed.
  • Non-Human Devices: Any device that operates without human intervention needs a license. However, if a human operates the device, both the device and the human operator must be licensed.

Example Scenario

Consider a company with 400 employees operating 30 forklifts:

  • Forklifts as Devices: Forklifts are considered human-operated devices.
  • Employee Licensing: All 400 employees must be licensed because they operate the forklifts.

Access Flexibility

A licensed Named User Plus may access the program on any instance where it is deployed, provided that the minimum user requirement on each server is met.

Illustration

Illustration #1:

  • Environment: 400 employees using 30 forklifts.
  • Licensing Requirement: All 400 employees need Named User Plus licenses.

Summary

  • Human Users: Must be licensed.
  • Non-Human Devices: Must be licensed if they operate without human intervention.
  • Human-Operated Devices: Both the device and the operator need licenses.
  • Access: Licensed users can access the program on any server, meeting the minimum user requirement.
Illustration #1:Licensing Technology Products 
oracle databaase licensing
pdf icon 1
  • The manufacturing company has 15 temperature devices to control the temperature in the warehouse. These devices update the Oracle Database.
  • 400 warehouse employees use 30 forklifts to move the contents in the warehouse
  • The forklift has a built-in transponder that updates the Oracle Database EE directly.
  • Oracle Database is running on a 6- processor server (single-core chips)
 Number of licenses required
Oracle Database EEThis product can be licensed by Processor or by Named User Plus metric. •By Processor: all processors where the database is installed and/or running must be licensed. Number of Processor licenses required: 6 •By Named User Plus: the number of licenses required is 1) the Named User Plus minimum (25 Named Users Plus per Processor) OR 2) the total number of actual users accessing the Database (= # of temperature devices + warehouse employees), whichever is greater. 25 * 6 Processors = 150 Named Users Plus15 temperature devices + 400 warehouse employees = 415 Named Users PlusNumber of Named User Plus licenses required: 415

Named User Plus Licensing with Multiplexing

Named User Plus Licensing with Multiplexing

When multiplexing hardware or software is used, the number of Named User Plus (NUP) licenses must be counted at the multiplexing front end. Multiplexing details are covered later in this section.

Minimums for Named User Plus Metric

Minimums for the NUP metric can be based on discrete quantities or the number of processors in the machine where the software will be installed and/or run.

Minimum Licensing Requirements

  • Database Enterprise Edition: Minimum of 25 Named Users Plus per processor.
  • iAS Standard Edition: Minimum of 10 Named Users Plus per processor.
  • iAS Enterprise Edition: Minimum of 10 Named Users Plus per processor.
  • Database Standard Edition: Minimum of 5 Named Users Plus.
  • Standard Edition One: Minimum of 5 Named Users Plus.

Special Considerations

For iAS SE One, SE, and EE:

  • The Named User Plus minimum does not apply if the program is installed on a single-processor machine that allows a maximum of one user per program.

Summary Table

EditionMinimum Named Users Plus per Processor
Database Enterprise Edition25
iAS Standard Edition10
iAS Enterprise Edition10
Database Standard Edition5
Standard Edition One5
iAS SE One/SE/EE (Single Processor)1 user maximum per program

Important Reminder: Oracle Database Standard Edition Licensing

Important Reminder: Oracle Database Standard Edition Licensing

Key Licensing Restrictions

  • Standard Edition 2 (SE2): Can only be licensed on servers with a maximum capacity of 2 CPU sockets.
  • Standard Edition (SE): Can only be licensed on servers with a maximum capacity of 4 CPU sockets.
  • Standard Edition One (SE1): Can only be licensed on servers with a maximum capacity of 2 CPU sockets.

Real Application Clusters (RAC) Inclusion

  • Oracle Database 10g to 18c: Starting with the release of 10g, Oracle Database Standard Edition includes the Real Application Clusters (RAC) option.
  • Oracle Database 19c and Later: The RAC option is removed from Standard Edition starting with the 19c version.
  • Pre-10g Versions: The RAC option is not included with any Standard Edition versions before 10g.

Upgrading with Software Updates License & Support

  • Eligibility: Customers with Oracle’s Software Updates License & Support for the Standard Edition Database can upgrade to the 10g version of the product for the supported licenses.
  • Clusterware Requirement: Customers must use Oracle Cluster Ready Services as the clusterware, as third-party clusterware is not supported.
  • Data Management: Automatic Storage Management (ASM) must be used to manage all data.

Summary

EditionMaximum CapacityRAC InclusionClusterware RequirementData Management Requirement
Standard Edition 22 CPU socketsIncluded from 10g to 18c, removed in 19c and laterOracle Cluster Ready ServicesAutomatic Storage Management
Standard Edition4 CPU socketsIncluded from 10g to 18c, removed in 19c and laterOracle Cluster Ready ServicesAutomatic Storage Management
Standard Edition One2 CPU socketsNot includedNot applicableNot applicable

Processor Metric

The Processor metric is primarily used in environments where identifying or counting software users is challenging, such as in internet-based applications. This metric is also chosen when it is more cost-effective than Named User Plus licenses. All processors where Oracle programs are installed and/or running must be licensed.

Licensing Calculation

To determine the number of required licenses, follow these steps:

  1. Count Total Cores: Count the total number of cores for each processor.
  2. Core Factor Application: Multiply the total number of cores by the core processor licensing factor specified in the Oracle Processor Core Factor Table.
  3. Aggregation: Aggregate all cores on all multicore chips for each licensed program.
  4. Rounding Up: Round up any fractions to the next whole number.

Special Cases

  • Standard Edition One (SE1) and Standard Edition (SE): A processor is counted as one occupied socket. For multi-chip modules, each chip is counted as one occupied socket.

Examples

Example 1: Multicore Chip Server

  • Configuration: Server with 6 cores and a core factor of 0.25.
  • Calculation:
    • 6 cores * 0.25 = 1.50.
    • Round up to the next whole number: 2 processor licenses required.

Example 2: Unspecified Hardware Platform

  • Configuration: Server with 10 cores on a platform not specified in the Oracle Processor Core Factor Table.
  • Core Factor: Default factor for “All other multicore chips” is 1.0.
  • Calculation:
    • 10 cores * 1.0 = 10 processor licenses required.

Summary Table

ScenarioCore CountCore FactorCalculationLicenses Required
Multicore chip server60.256 * 0.25 = 1.502
Unspecified hardware platform101.010 * 1.0 = 10.010

Key Points

  • All Cores Counted: All cores on all multicore chips must be aggregated before applying the core factor.
  • Fraction Rounding: Always round up fractions to the next whole number to determine the number of licenses required.
  • SE1 and SE Licensing: For these editions, a processor is equivalent to an occupied socket, and each chip in a multi-chip module counts as one socket.

Oracle Licensing Policies

Oracle Licensing Policies

Prerequisite Rules

Many software products have functional interdependencies with other software products. Sometimes, prerequisite products are made by the same company that makes the primary product, while other times they are provided by different vendors. For example, a word processing software program requires an operating system to function. Before the word processing software can be used, an operating system must be installed on the hardware. Prerequisite products are often sold separately.

Many Oracle products have functional interdependencies with other Oracle products. In some cases, prerequisite products are sold separately. In others, where the functional interdependency is more limited, customers automatically receive a free, restricted-use license for a prerequisite product or products to facilitate the use of the product they are licensing.

Environments to License

Software is always used in combination with some type of hardware and operating system. In today’s world, software is often used in combination with many different types of hardware and operating systems, which may be connected together in a complex network. Oracle’s software is developed based on open standards that allow it to be installed and used on servers, computers, and devices made by multiple manufacturers and running many operating systems.

The term “configuration” describes the combination of hardware, software, and licensed users and devices that a customer has or wants to run. For example, one possible (and very basic) configuration would be 160 Named User Plus licenses for Oracle Database Enterprise Edition running on a Sun Solaris server.

Using any Oracle software product requires a license from Oracle. To maximize the value you receive from your Oracle software, ensure you are licensed to use it in different environments such as development, test, production, and standby. See illustration #2.

Development Environment

  • Purpose: Set up, customize, and modify software.
  • License Requirements: Any person doing development work using the software must be licensed. Oracle software may be downloaded for limited development work via the Oracle Technology Network (OTN). Software downloaded from the OTN Website is governed by a special agreement called the OTN Development License, which grants the right to use the programs only in a development environment. Licenses obtained under this agreement may not be used in test, production, fail-over, or any other environments. Customers who want to use applications developed under an OTN license for internal data processing, commercial, or production purposes must secure a full-use Oracle license for any development software licensed under the OTN agreement before using the applications.
  • Alternative: Customers wanting a less restrictive license for development work may obtain Full Use licenses under a standard Oracle Master Agreement (OMA) from the Oracle Store or through their Oracle Sales Representative.

Test/Staging Environment

  • Purpose: Verify that new or customized code runs properly. This can be staged on separate servers or on the same servers used to run a development or production environment.
  • License Requirements: Any Oracle software used in a test/staging environment must be properly licensed with a Full Use license under an Oracle Master Agreement (OMA) or other appropriate Oracle (or Oracle authorized reseller) license agreement. Suppose a test/staging environment is maintained on the same server as a production or development environment, and that server is fully licensed for all relevant programs on a per Processor metric. In that case, no additional licenses are required for the test/staging environment.

Production Environment

  • Purpose: The environment used by end users for business or other operations.
  • License Requirements: All programs in the production environment must be properly licensed based on the applicable license metrics under an Oracle Master Agreement (OMA) or other appropriate Oracle (or Oracle authorized reseller) license agreement.
oracle licensing policy
Products to be licensedNumber of licenses required
Oracle Database EE (Test, Staging & Production)This product can be licensed by Processor or by Named User Plus metric: •If licensing by Processor, all processors where the database is installed and/or running must be licensed. Number of Processor licenses required: 6 •If licensing by Named User, the number of licenses required is 1) the Named User Plus minimum (25 Named Users Plus per Processor) OR 2) the total number of actual users accessing the Database (= # of traders + developers), whichever is greater: 25 * 6 Processors = 150 Named Users Plus500 traders + 10 Developers = 510 Named Users PlusNumber of Named User Plus licenses required: 510 Note : If the server is fully licensed by Processor then no additional licenses are required to install and/or run other environments that are configured on the same server.

Oracle Licensing for Backup, Failover, Standby, and Remote Mirroring

Oracle Licensing for Backup, Failover, Standby, and Remote Mirroring

Oracle differentiates between four methods of database recovery: Backup, Failover, Standby, and Remote Mirroring. Each method has specific licensing requirements.

Backup

  • Definition: A copy of the physical database structures, such as control files, redo logs, and data files.
  • Storage: Backup files can be stored on various storage devices (servers, storage arrays, disk drives, or CDs).
  • Tools: Solutions like Recovery Manager (RMAN) and Oracle Secure Backup, or operating system utilities, are used to create these backups.
  • Licensing: Oracle permits customers to store a backup copy without purchasing additional licenses. However, if the Oracle Database is installed on a recovery server during data restoration, licensing is required.

Failover

  • Definition: Nodes are arranged in a cluster, sharing one disk array. When the primary node fails, a surviving node in the cluster takes over.
  • Tools: Managed by solutions like Oracle Failsafe, Veritas, HP Service Guard, HACMP, or Linux HA (Heartbeat).
  • Licensing:
    • Licensed Oracle customers can run Technology Programs on an unlicensed spare computer for up to ten separate days per calendar year.
    • Once the primary node is repaired, you must switch back.
    • If the failover period exceeds ten days, the failover node must be licensed.
    • Only one failover node per cluster is permitted without charge for up to ten days.
    • The same license metric must be used for both production and failover nodes.
    • Options licensed on the failover environment must match those of the associated database.

Standby

  • Definition: One or more copies of a primary database are maintained on a standby server. The primary and standby databases are connected by Oracle Net Services.
  • Tools: Managed by solutions like Oracle Data Guard or customer-generated scripts.
  • Licensing:
    • Both the primary and standby databases must be fully licensed.
    • The same license metric must be used for both databases.

Remote Mirroring

  • Definition: Involves mirroring storage units or shared disk arrays. Mirrored units can be geographically dispersed but share the same disk array.
  • Tools: Managed by solutions like Veritas Volume Replicator, EMC SRDF, Legato Replistor, and EMS StoreEdge.
  • Licensing:
    • Both the primary and remote mirrored databases must be fully licensed.
    • The same license metric must be used for both databases.
    • If Oracle Database is installed on both primary and mirrored units, both must be fully licensed.
    • If the primary storage unit fails and data is accessed from the mirrored unit, both databases must still be fully licensed.

Summary of Licensing Requirements

Recovery MethodLicensing Requirements
BackupNo additional licenses for backup copies; licensing required if restored on a recovery server.
FailoverSpare computer use allowed for up to 10 days without charge; must be licensed if exceeding 10 days or using multiple nodes. Same metric required for both nodes.
StandbyBoth primary and standby databases must be fully licensed. Same metric required for both.
Remote MirroringBoth primary and mirrored databases must be fully licensed. Same metric required for both.
Oracle licensing backup
Products to be licensedNumber of licenses required
Oracle Database EE (Test, Staging & Production)This product can be licensed by Processor or by Named User Plus metric. By Processor: all processors where the database is installed and/or running must be licensed.Number of Processor licenses required: 6By Named User Plus: the number of licenses required is 1) the Named User Plus minimum (25 Named Users Plus per Processor) OR 2) the total number of actual users accessing the database (= # of traders + developers + DBA), whichever is greater.25 * 6 Processors = 150 Named Users Plus500 traders + 10 Developers + 1 DBA= 511 Named Users PlusNumber of Named User Plus licenses required: 511
oracle licensing failover
Products to be licensedNumber of licenses required
Oracle Database EEThis product can be licensed by Processor or by Named User Plus metric: •By Processor: all processors where the database is installed and/or running must be licensed. > Number of processors licenses required: 6 Included: right to run the database on node 2 for up to a total of 10 separate days in any given calendar year •By Named User Plus: the number of licenses required is 1) the Named User Plus minimum (25 Named Users Plus per Processor) OR the total number of users accessing the Database (= # of traders), whichever is greater: –1) 25 * 6 Processors = 150 Named Users Plus, –2) 1,000 traders = 1,000 Named Users Plus Number of Named User Plus licenses required: 1,000
oracle licensing standby

See the Partitioning document on https://www.oracle.com/corporate/pricing/specialtopics.html for detailed information on partitioning.

Batching, Import/Export of Flat Files, and Multiplexing

Overview

As computing environments grow in size and complexity, batching and multiplexing have become increasingly important. However, definitions of these processes can vary between vendors, leading to confusion. Understanding Oracle’s definitions and their licensing implications is crucial.

Batching

Batching allows a group of tasks occurring at different times to be processed simultaneously with minimal or no user interaction. It is typically used to transport data between computers running the database.

Methods of Batching

  1. Automatic Batch/Data Feeds:
    • No human interaction required.
    • Batching scripts automatically upload data.
    • (Illustration #7)
  2. Manual Batch/Data Feeds:
    • Requires human interaction.
    • Users manually enable the execution of batching scripts.

Licensing for Batching Environments

  • Processor Metric:
    • All processors where the Oracle Database is installed and/or running must be licensed.
  • Named User Plus Metric:
    • For automatic batching, the only automated process permitted is batching data from computer to computer where the database is running.
    • In manual batching, users performing the batch/data feeds are considered actual users and need to be licensed.
    • The number of licenses required is the greater of the licensing minimum or the total number of actual users accessing the Oracle program.

Import/Export of Flat Files

This process involves human interaction to import or export data from flat files (e.g., Excel or CSV) into the Oracle Database using import and export utilities.

Licensing for Import/Export

  • Processor Metric:
    • All processors where the Oracle Database is installed and/or running must be licensed.
  • Named User Plus Metric:
    • Users performing the import/export of flat files are considered actual users and need to be licensed.
    • The number of licenses required is the greater of the licensing minimum or the total number of actual users accessing the Oracle program.
    • (Illustration #8)

Multiplexing

Multiplexing occurs when many end users and/or devices access a system via an interface (e.g., TP monitor or web server), making the number of apparent users/devices smaller than the actual number.

Licensing for Multiplexing Environments

  • Processor Metric:
    • All processors where the Oracle Database is installed and/or running must be licensed.
  • Named User Plus Metric:
    • All users and/or devices must be licensed at the multiplexing front end.
    • The number of licenses required is the greater of the licensing minimum or the total number of actual users at the multiplexing front end accessing the Oracle program.
    • (Illustration #9)

Summary of Licensing Requirements

MethodLicensing MetricRequirements
BatchingProcessorLicense all processors where Oracle Database is installed/running.
Named User PlusLicense users performing batch/data feeds; greater of licensing minimum or total users.
Import/Export of Flat FilesProcessorLicense all processors where Oracle Database is installed/running.
Named User PlusLicense users performing import/export; greater of licensing minimum or total users.
MultiplexingProcessorLicense all processors where Oracle Database is installed/running.
Named User PlusLicense all users/devices at multiplexing front end; greater of licensing minimum or total users.
oracle licensing batching
 Number of licenses required
Oracle Database EEThis product can be licensed by Processor or by Named User Plus metric. •By Processor: all processors where the database is installed and/or running must be licensed. Number of Processor licenses required: 6 •By Named User Plus: the number of licenses required is 1) the Named User Plus minimum (25 Named Users Plus per Processor) OR 2) the total number of actual users accessing the Database (= # of traders), whichever is greater. 25 * 6 Processors = 150 Named Users Plus300 traders = 300 Named Users PlusNumber of Named User Plus licenses required: 300
oracle licensing flat files
Products to be licensedNumber of licenses required
Oracle Database EEThis product can be licensed by Processor or by Named User Plus metric: •By Processor: all processors where the database is installed and/or running must be licensed. Number of processors licenses required: 6•By Named User Plus: the number of licenses required is 1) the Named User Plus minimum (25 Named Users Plus per Processor) OR 2) the total number of users accessing the Database (= # of traders + 1 DBA), whichever is greater: –1) 25 * 6 Processors = 150 Named Users Plus, –2) 500 traders + 1 DBA= 501 Named Users Plus Number of Named User Plus licenses required: 501
oracle licensing multiplexing
Products to be licensedNumber of licenses required
Oracle Database EEThis product can be licensed by Processor or by Named User Plus metric. •By Processor: all processors where the database is installed and/or running must be licensed. Number of Processor licenses required: 6 •By Named User Plus: the number of licenses required is 1) the Named User Plus minimum (25 Named Users Plus per Processor) OR 2) the total number of actual users accessing the Database (= # of traders), whichever is greater 25 * 6 Processors = 150 Named Users Plus500 traders = 500 Named Users PlusNumber of Named User Plus licenses required: 500 Note: Given that this is a multiplexing environment, all users at the front end of multiplexing must be licensed.

If you need more help with Oracle database licensing, contact our experts to get help.

https://oraclelicensingexperts.com/wp-content/uploads/2022/12/Oracle-Database-Licensing-Guide.webp|https://oraclelicensingexperts.com/wp-content/uploads/2024/05/Introduction-to-Software-License-Agreements.webp|https://oraclelicensingexperts.com/wp-content/uploads/2024/05/Types-of-Oracle-Licenses.webp|https://oraclelicensingexperts.com/wp-content/uploads/2024/05/Different-Oracle-Database-Editions.webp|https://oraclelicensingexperts.com/wp-content/uploads/2024/05/Differences-Between-Oracle-Database-Standard-Edition-2-and-Enterprise-Edition.webp|https://oraclelicensingexperts.com/wp-content/uploads/2024/05/Named-User-Plus-Metric.webp|https://oraclelicensingexperts.com/wp-content/uploads/2024/05/Named-User-Plus-Licensing-with-Multiplexing.webp|https://oraclelicensingexperts.com/wp-content/uploads/2024/05/Important-Reminder-Oracle-Database-Standard-Edition-Licensing.webp|https://oraclelicensingexperts.com/wp-content/uploads/2024/05/Oracle-Licensing-Policies.webp|https://oraclelicensingexperts.com/wp-content/uploads/2024/05/Oracle-Licensing-for-Backup-Failover-Standby-and-Remote-Mirroring.webp Oracle Database Licensing Guide|Introduction-to-Software-License-Agreements|Types-of-Oracle-Licenses|Different-Oracle-Database-Editions|Differences-Between-Oracle-Database-Standard-Edition-2-and-Enterprise-Edition|Named-User-Plus-Metric|Named-User-Plus-Licensing-with-Multiplexing|Important-Reminder-Oracle-Database-Standard-Edition-Licensing|Oracle-Licensing-Policies|Oracle-Licensing-for-Backup-Failover-Standby-and-Remote-Mirroring ||||||||| Oracle Licensing Fredrik Filipsson Fredrik Filipsson 2022-12-27 17:35:52 oracle-database-licensing-guide

Author

  • Fredrik Filipsson

    Fredrik Filipsson brings two decades of Oracle license management experience, including a nine-year tenure at Oracle and 11 years in Oracle license consulting. His expertise extends across leading IT corporations like IBM, enriching his profile with a broad spectrum of software and cloud projects. Filipsson's proficiency encompasses IBM, SAP, Microsoft, and Salesforce platforms, alongside significant involvement in Microsoft Copilot and AI initiatives, improving organizational efficiency.

    View all posts