A-Z of Oracle Licensing – Part 4
We are carrying on with our A-Z of Oracle licensing terms, rules, metrics and general information. This time looking at J, K and L. Hopefully you are finding it helpful, but if you need more information please don’t hesitate to contact us by email to firstname.lastname@example.org or check out our online training courses at https://madora.teachable.com
J is for Java
This has been in the Oracle news recently as the licensing and support rules have changed. We provided a blog on the subject a little while ago and you can find it here on our website; http://madora.co.uk/oracle-java-support-changes
K is for 5 Key rules of Oracle Licensing
1. Counting Users; the key points here are that a user is counted (at source) regardless of whether they actively use the Oracle programs and that non-human devices are also counted.
2. Virtualisation; Probably the most popular server partitioning method is VMware, a very flexible form of partitioning and a great means of managing a datacentre. It is soft partitioning for Oracle which means that it is incredibly easy to fall foul of Oracle’s licensing rules.
How your vCenter is set up, the clusters, the VMs, the storage architecture all have an impact on Oracle licensing. VMware publish guidelines on how to license Oracle, but Oracle don’t support their view.
3. Disaster Recovery; This can be a complex area with technologies changing all the time. We highly recommend you speak to us if you have any doubts as to whether you are correctly licensed for DR architectures.
However, in general we advise that you assume you need to be licensed fully and then check to see if your scenario falls under failover and whether the 10 day rule applies.
Be aware that you cannot mix metrics. If Processor licences are used for the primary site then the backup site also needs to be licensed by Processor. A Named User Plus license can't be used for the backup site unless the primary site is using Named User Plus.
Make sure that Options and Management Packs are also licensed. These are often forgotten.
4. Development Environments; You need a valid Oracle license for development, test and any pre-production environments. Test and development must be correctly licensed. The use of OTN licenses does not necessarily mean you are licensed correctly for Development environments.
5. Database Options; This still crops up and is a very common occurrence because they have been installed as this is the default on installations or because an assumption has been made that the options have already been purchased. Most would regard them as part of the core database, but unfortunately they are still chargeable options so must be purchased separately.
L is for Licence
What is a software licence? We cover this in detail in our Foundation training courses, but as an overview; a software licence is the right to use a quantity of software based on the t's & c's offered by the vendor, in this case Oracle. "The right of a licensee to use a maximum quantity of one or more software products measured under defined metrics, for a defined business purpose, in a geographic area, for a period of time, under the licence policies of the licensor (vendor)."
If you want to learn more out the different types of licence contracts, paperwork or maintenance renewals follow the link to https://madora.teachable.com/ and select the Foundation Level.
Don’t forget we can help with licensing any of the Oracle products if you are unsure, so don’t hesitate to contact us.
Look out for our next Blog where we will include M, N and O.