Assistance with Oracle Licensing
With multiple licensing models and types of licenses; additional licensing options and different metrics depending on the type of CPUs in your database servers - It can certainly be a complex affair to ensure that your company has adequate licenses for your Oracle applications and will not be exposed as a result of an Oracle audit.
Our team of experts can help remove this complexity and calculate the most cost effective means to meet the requirements of licensing your Oracle software. What's more we will provide this service completely free of charge and, as Oracle partners, will provide you with a no obligation quote for providing the relevant Oracle licenses at discounted prices.
Contact us now for more information.
Oracle Licensing FAQ
This metric is used in environments where the total possible number of users (not concurrent) can be identified and counted.Named User Plus includes both humans and non-human operated devices. All human users and non-human operated devices that are accessing the program must be licensed. A non-human operated device can be many things, such as, a temperature monitoring device. It is important to note that if the device is operated by a person, then this person must be licensed. For example, 400 employees who are operating 30 forklifts must be licensed because the forklift is not a “non-human operated device”.
A licensed Named User Plus may access the program on any instances where it is deployed, provided that the minimum on each server is met:
Minimum NUP users
25 (per CPU Unit)
Standard Edition One
With respect to the following programs: Load Testing, Load Testing Developer Edition, Load Testing Accelerator for Web Services, Load Testing Accelerator for Oracle Database, and Load Testing Accelerator Application Development Framework Applications, each emulated human user and non human operated device shall be considered as a virtual user and shall be counted for the purposes of determining the number of Named User Plus licenses required.
In this metric the server is licensed by the number of CPU units installed. There is no limit for the number of application users or number of installed databases for processor licenses. Therefore this metric is more applicable to environments where the total number of users cannot be identified and counted (e.g. such as an application which is accessible to users over the internet). A processor license will also be more applicable where the cost of licensing the total possible number of users via NUP licensing would exceed the cost of a licensing via the number of processors.
There is no licensing limit to the number of CPUs that can be installed for Oracle Enterprise Edition. However, Oracle’s licensing costs for the number of cores installed differ depending on the type of CPUs installed.
Vendor and Processor
Core License Processor Factor
Sun and Fujitsu UltraSPARC T1 processor (1.0 or 1.2 GHz)
Only named servers including:
Sun Fire T1000 Server, SPARC Enterprise T1000 Server, with 6 or 8-core
1.0 GHz UltraSPARC T1 processor
Sun Fire T2000 Server, SPARC Enterprise T2000 Server, with 4, 6, or 8-
core 1.0 GHz, or 8 core 1.2 GHz UltraSPARC T1 processor
Sun Netra T2000, 1.0 or 1.2 GHz UltraSPARC T1 processor
SPARC T3 processor
Sun and Fujitsu UltraSPARC T1 1.4 GHz
Only named servers including:
Sun Fire T2000 Server and SPARC Enterprise T2000 Server, with 8-core,
1.4 GHz UltraSPARC T1 processor
Sun T6300, 1.4 GHz UltraSPARC T1 processor
AMD Opteron Models 13XX, 23XX, 24XX, 41XX, 61XX, 83XX, 84XX or
earlier Multicore chips
Intel Xeon Series 56XX, Series 65XX, Series 75XX, Series E7-28XX, Series
E7-48XX, Series E7-88XX or earlier Multicore chips
Intel Itanium Series 93XX or earlier Multicore chips (For servers purchased prior to Dec 1st, 2010)
Intel or AMD Desktop, Laptop/Notebook, or Netbook Multicore chips
Sun UltraSPARC T2+
Sun and Fujitsu SPARC64 VI, VII
Sun UltraSPARC IV, IV+, or earlier Multicore chips
Sun UltraSPARC T2
IBM POWER5+ or earlier Multicore chips
All Single Core Chips
Intel Itanium Series 93XX (For servers purchased on or after Dec 1st, 2010)
IBM System z (z10 and earlier)
All Other Multicore chips
For example to calculate the required CPU units for an AMD Quad core processor with a 0.5 core licensing processor factor would be calculated as follows:
4 Cores x 0.5 = 2 CPU Units
The latest Oracle Multi Core Factor Table can be found here:
Oracle Standard Edition can be deployed on servers with a maximum capacity of 4 CPU sockets. Oracle does not take the number of CPU cores into consideration when licensing Oracle Standard Edition, thus a single CPU counts as a CPU Unit regardless of the number of cores it owns. For example, if you have a server with a maximum capacity of 4 CPU sockets and each socket has a Quad Core CPU installed (4 x Quad Core CPUs); then this would still qualify for Oracle Standard Edition.
From 10g, Oracle Real Application Clusters (RAC) is also included in Oracle Standard Edition at no additional cost as long as the total capacity of the cluster is 4 CPU sockets (e.g. a two node cluster with each server having a maximum of 2 CPU sockets).
Oracle Standard Edition One can be deployed on servers with a maximum capacity of 2 CPU sockets. Oracle does not take the number of CPU cores into consideration when licensing Oracle Standard Edition One, thus a single CPU counts as a CPU Unit regardless of the number of cores it owns. For example, if you have a server with a maximum capacity of 2 CPU sockets and each socket has a Quad Core CPU installed (2 x Quad Core CPUs); then this would still qualify for Oracle Standard Edition.
Oracle Standard Edition One is available from 10g onwards. It does not differ in regards to functionality to Standard Edition except by the CPU socket limit. Oracle Real Application Clusters (RAC) is not available on Standard Edition One.
Oracle classes virtualisation under two types of Partitioning Hard and Soft.
“Partitioning” occurs when the CPUs (processors) on a server are separated into individual sections where each section acts as a separate system. Sometimes this is also called “segmenting”.
Soft partitioning segments the operating system using OS resource managers. The operating system limits the number of CPUs where an Oracle database is running by creating areas where CPU resources are allocated to applications within the same operating system. The database administrator can set the number of CPUs to the number of licensed CPUs. This is a flexible way of managing data processing resources since the CPU capacity can be changed fairly easily, as additional resource is needed.
Examples of such partitioning type include: and Solaris 9 Resource Containers, AIX Workload Manager, HP Process Resource Manager, Affinity Management, Oracle VM, VMware, etc.
Soft Partitioning is not permitted by Oracle as a means of reducing the number of licenses required for a given server and licensing must be based on the physical hardware rather than the number of CPUs available to the individual virtual server.
Hard partitioning physically segments a server, by taking a single large server and separating it into distinct smaller systems. Each separated system acts as a physically independent, self-contained server, typically with its own CPUs, operating system, separate boot area, memory, input/output subsystem and network resources.
Oracle allows certain approved hard partitioning technologies as a valid means to reduce the number of licenses required for a given server. Thus only the number of CPUs which are able to be used within the hard partition containing the Oracle Software need to be licensed.
Examples of approved hard partitioning technologies include: Dynamic Reconfiguration (DR), Solaris 10 Containers (capped Containers only), LPAR (adds DLPAR with AIX 5.2), Micro-Partitions (capped partitions only), vPar, nPar, Integrity Virtual Machine (capped partitions only), Secure Resource Partitions (capped partitions only), Static Hard Partitioning, Fujitsu’s PPAR.
More information on licensing Server/ Hardware partitioning is available here: http://www.oracle.com/us/corporate/pricing/partitioning-070609.pdf
ASFU licenses can be provided, at typically larger discounted levels than standard full use licenses, where the database and data contained within it will only be used by a specific application.Databases required for separate purposes cannot coexist on the same database server licensed on an ASFU basis.
ASFU licenses can only be provided by the third-party application provider under an agreement with Oracle.
Licensing Data Recovery Environments
Data Recovery methods include four types of environments: Backup, Failover, Standby, and Remote Mirroring.
• Backup: In this method, a copy of the physical database structures of the database is made. When the original data is lost, the backup files can be used to reconstruct the lost information that constitutes the Oracle Database. This backup copy includes important parts of the database’s physical structures such as control files, redo logs and data files. These physical files can be stored on a server, storage array, disk drive, or Compact Disc.
• Failover: In this method, nodes are configured in “clusters” with the first installed node acting as a primary node. If the primary node fails, one of the surviving nodes in the cluster acts as the primary node. In this type of environment, Oracle permits its licensed Technology customers to run the Technology on an unlicensed spare computer for up to a total of ten separate days in any given calendar year. The above right only applies when a number of machines are arranged in a cluster and share one disk array. Once the primary node is repaired, you must switch back to the primary node. Only one failover node per clustered environment is at no charge for up to ten separate days even if multiple nodes are configured as failover nodes. When licensing options on a failover environment, the options must match the number of licenses of the associated database. Additionally, when licensing by Named User Plus, the user minimums are waived on one failover node only. Any use beyond the right granted in this section must be licensed separately. In a failover environment, the same license metric must be used for the production and failover nodes when licensing a given clustered configuration.
• Standby: One or more copies of the primary database are maintained on a separate server(s) at all times. The sites in a standby configuration may be dispersed geographically and are connected by Oracle Net Services. As the primary database is modified, log information generated by the changes are sent to the standby database(s) and subsequently applied to the standby database. If the primary database fails, a standby database can be activated to be the new primary database. In this environment, the primary and the standby databases must be fully licensed. Additionally, the same metric must be used when licensing the databases in a standby environment. If any Option or Management Pack (except RAC) is licensed on the primary server, then it must also be licensed on the Standby server. If RAC is on the primary server but not on the standby server, then licensing it is not required.
• Remote Mirroring: This method involves the mirroring of the storage unit or shared disks arrays. To setup a remote mirroring environment, the Oracle data files, executables, binaries and DLLs are replicated to the mirrored storage unit. In this environment, Oracle must be fully licensed at the primary site, and if it is installed and/or run at the secondary site, it must also be fully licensed there. Additionally, the same metric must be used to license both databases. If any Option or Management Pack (except RAC) is licensed on the primary server, then it must also be licensed on the mirrored server. If RAC is on the primary server, but not on the mirrored server, then licensing RAC is not required on the mirrored server.