1 person found this helpful
First off - only Oracle License Management Services can make a binding statement what has to be licensed.
But there is some guidance, namely the "Oracle Partitioning Policy" document (https://www.oracle.com/assets/partitioning-070609.pdf ) which describes what is a "hard partition" (i.e. a license boundary). This document says that Solaris Zones are recognized as a license boundary as long as some prerequisites are met, which are described in detail in another document (http://www.oracle.com/technetwork/server-storage/solaris11/technologies/os-zones-hard- partitioning-2347187.pdf)
Many thanks Andris - I am familiar with both documents referenced, but neither detail what is required for DR, and if "Asymmetric" licensing for DR is allowed.
I understand LMS are the "definitive source" - but there seems no way to contact them directly about a small query like this...
From a license perspective, it does not matter if the system is "Production" or "DR" or whatever. If there is Oracle software running, you have to license it (There is one exception, also known as the "10 day rule", but this does only apply to failover systems, not standby databases). How large you size your DR system is up to you.
PS: Here's the link that explains licensing in "Data Recovery" environments: https://www.oracle.com/assets/data-recovery-licensing-070587.pdf
Many Thanks for the document - that answers my question - we are looking at implementing a mirrored DR environment, so according to the document, "Licensing metrics and program options on Production and Data Recovery/Secondary servers must match" - so we cannot have "asymmetric" licencing on the two servers - they must be duplicates of each other. Ah, Well.. it was worth a try... ;-)
IMHO your conclusion is not correct. You can have "asymmetric" licensing regarding the quantity of licenses. But you can't have e.g. Processor based on the primary and Named Users Plus on the standby ("Licensing metrics"), and you will have to license the same options ("program options") on the standby as on the primary.
Many thanks for correcting my misunderstanding - I have re-read the document again, and you appear to be correct - there is nothing there appears to make the following example non-compliant:
Server 1 - configured for 1 zone with 6 cores
Server 2 - configured for 1 zone with 2 cores
Licences held - 8 cores
Server 1 is "Live"
Server 2 is "DR"
Servers are mirrored, not clustered
If server 1 fails, then server 2 takes over (zone is manually configured for 6 cores)
Licence is still compliant, as core count has not been exceeded, while "live" is offline.
Please let me know you opinion.
Now we are entering a grey area (at least for me). For your scenario to work, you'd have to make absolutely sure that you never have both zones active with 6 cores each. You can only resize "DR", when "Live" is shut down completely (or shrunk to 2 cores). Likewise, when "Live" is started up while "DR" has 6 active cores, then "Live" must only start with 2 active cores.
I know that in the past we have proposed such setups to customers. But I can't tell if we had to get special approval and how "license compliance" was ensured.
Andris - indeed, a "grey" area - if the solution gets approval, and we move to the procurement stage, I will contact Oracle, and update this post ;-)
Many thanks for your help.