Oracle licensing on hacmp

This version is restricted to one user per database, however the license still allows a developer to use all of the features that you get with Oracle Enterprise Edition. Oracle Xpress Edition — Free, but limited to one database. May only be licensed on servers that have a maximum capacity of two processor cores. Unlimited License Agreement ULA is a time based, unlimited use rights license for a certain subset of Oracle products.

At the end of the ULA period, the user must declare usage and count the number of licenses they need. The customer is then granted the needed number of licenses for the products covered by the ULA. Oracle does not offer Processor licensing if using Personal Edition Oracle products.

The number of required licenses should be evaluated by multiplying the total number of cores of the processor by a core processor-licensing factor specified on the Oracle Processor Core Factor Table check your Oracle contract for your terms. When licensing Oracle programs with Standard Edition One or Standard Edition in the product name, processor is counted equivalent to a socket; however, in the case of multi-chip modules, each chip in the multi-chip module is counted as one occupied socket.

Product Minimums for Named User Plus licenses, minimums are per processor, are calculated after the number of processors to be licensed is determined, using the processor definition.

The actual metric may have been redefined slightly over the years to incorporate new technology or applications that Oracle buy, but the base remains constant. Oracle user based licensing is about the individuals or devices that have the ability to access the software, regardless the active usage.

This license type has been available since , and is available for the majority of Oracle products. Although the metric name is unchanged, the definition has once again been adjusted to allow for the automatic batching from computer to computer. Under NUP automatic batching of data from computer to computer is permitted. This means that if data is stored in one relational database and then batched to a datawarehouse on Oracle technology, the individuals who can use the first database are not to be considered as Named users of the datawarehouse.

The NUP license model may only be used in countable environments. Often it is used to license the employees and contractors of an organisation, or internally used applications. It is a popular license for development and test environments. Oracle previously offered a license type called Named User. However, this is no longer available to new customers, but may still be a part of existing customers Oracle License Agreement.

A named user is an individual that has been authorized by the organisations to use the Oracle software, regardless of whether the individual is actively using the applications. Individuals can be employees, contractors, but also customers who can make use of the software directly or indirectly through other applications. If there are non-human operated devices in your architecture, such as sensors, these need to be counted as a named user in addition to the individuals, if such devices can access the product.

Our previous guide alludes to Named User licensing. This seems to be simple and can often be determined by looking at the organisation, rather than the software. However in multi-tier or technical architectures it can be very hard to determine. Oracle software can be at the bottom of the infrastructure and some users might have access to Oracle software without knowing it.

Especially when batching or multiplexing is being used it can be hard to determine. Under named user licensing multiplexing software is not recognized by Oracle, so the numbers needs to be determined at the front end of the multiplexor.

Named User Plus licensing is when the licensee pays per user, but a user is defined as any end-node that receives or creates data from an Oracle database.

This can include humans or systems. Named User licensing NU is a license that limits the amount of individuals that are authorized to use Oracle on any server. Named User licensing is no longer available for new customers, but some organisations may still have this license metric within their current Oracle agreement.

There is a Network License version. It is worth noting that this type of license is no longer available, but users may still have CD license as part of their existing Oracle agreement. This type of license is a restricted license that is sold by an Oracle Solution Provider in conjunction with its third-party application package.

This license would then be application specific and cannot be used for anything else. Each release could contain functionality that was previously licensed separately. The grant you have is for the latest version of the product you are entitled to under your support agreement. The new product could include all new features and functionality that you are now entitled to use or, often when it is larger bundle, you are not allowed to use.

When in reality the new version could be the new product, with the restricted functionality of the licensed product. Often user will rely on their support invoices to understand their license grant.

This is not complete, as the support invoice does not hold all the nuances in terms and definitions. Keep a good record of your original order and OLSA. You will not be the first to add up licenses, especially buying additional licenses, which seem to be for the same product but not have the same definitions and restrictions.

Wrap up Oracle has spent many efforts in simplifying their licensing. They publish their licensing and rules on their website and the online purchasing systems like the Oracle Store. However due to their acquisitions, the number of product and flexibility in usage, it has become complex for the end-user to understand. On top of that Oracle offers lifetime support including updates on almost all products.

This has resulted in a wide number of the number of licensing definitions, rules and interpretations, all still valid today, if they are in your agreement. Overall Oracle licensing is not complex; there is just a lot of it. Mark van Wolferen , of b. Recently b. I can see why there is just a handful of specialist companies offering consulting on Oracle. I subscribed to your newsletter and now I want to download the pdf oracle quick guide. How do I do it? I figured out the answer to my question.

I just needed to click on the link in the confirmation e-. DMAK, you are right. Putting all that into a document will make it into a book.

Thanks for another side to the Oracle Licensing forest. Having Read many articles and Oracle License related information there were also a few very good points. The comment on record keeping is crucial!

Please note that this Quick Guide has now been updated and is available here If you would like further information on managing the complexity of your Oracle licensing agreement why not join us at one of our free events taking place this year? These layers are Applications Middleware Database Infrastructure The licensing associated with each product is related to their position in this infrastructure and how they are deployed.

A practical rule that helps you in finding these populations is to track; Where the requests come from Where the information comes from. This means if the machines are put in a cluster, the entire cluster needs to be licensed that have Oracle installed. For standby or remote mirroring machines this is similar.

Legacy systems, also those powered off, require licensing if Oracle software is installed. Processor Calculation; a processor license is calculated by multiplying the total number of cores of the processor by a core processor licensing factor specified on the Oracle Processor Core Factor Table which can be accessed here. All cores on all multi-core chips for each licensed program are to be aggregated before multiplying by the appropriate core processor-licensing factor and all fractions of a number are to be rounded up to the next whole number.

There are some nuances per product as well. For example when licensing Oracle Database Standard Edition a processor is counted equivalent to an occupied socket; however, in the case of multi-chip modules, each chip in the multi-chip module is counted as one occupied socket.

If partitioning methodologies, including virtualization software, is part of hard partitioning, only the partitions with Oracle software need to be licensed. Soft partitioned servers need to be completely licensed. All third party like VM Ware is considered soft partitioning and requires the full environment to be licensed.

Note: As can be deduced from the above, in the case of Standard Edition One and Standard Edition there doesn't appear to be anything that specifies whether the minimum of 5 is per customer, per server or per processor and if per processor, whether the core factor is considered despite the fact it isn't for Standard processor licensing. Named User NU licensing limits the number of individuals authorized to use Oracle on any server.

NU licensing is not available for new contracts anymore. Concurrent Device CD licenses were defined as the 'Maximum amount of input devices connecting to the designated system at any given point in time'.

There is a Network version of this license which has slightly different terms. This is a very old licensing metric and anyone using it on multi-core processors, or moving to such a license, should conduct a cost assessment.

This model is not available anymore. This license would then be application specific and cannot be used for anything else. Customer should renew the license every year in advance with Application Vendor for avail all the supports and compliance the ASFU license or can be migrated to Full Use FU license with additional cost and renew directly with Oracle or any other authorised Oracle partner. This license would then be application specific and cannot be used for anything else, should be renewed with application vendor.

An end-user may not even be aware that the software package contains Oracle technology and should not be able to access it directly as a developer or system administrator. An example of this licensing model in use may be a Point of Sale system that requires a database to log transactions.

Note that the standard Oracle License and Services Agreement only allows use of Oracle software for internal business operations. Other uses, such as a hosting service or an ASP, will require an agreement that extends the usage rights to cover such scenarios. Oracle have a validation program which provides assurance that their LMS License Management Services team will accept data from certain third party vendor as being suitable for license review purposes.

Situations may arise where options in the Oracle technology or applications stack are being used that were not paid for, or where use may be extending beyond the scope of the contractual terms. Most of these cases occur due to lack of knowledge of the Oracle licensing scheme and a failure of managers to regularly audit license usage. Typically, when your Oracle rep. It is highly advisable to conduct a yearly audit of servers with a partner that understands Oracle licensing. This section lists some scripts that can be executed to see some of the components that should be licensed:.

Please note that the information provided by this command is not trustworthy on multi-threaded, multi-core or virtual systems.