About the author

Related Articles

4 Comments

  1. Pingback: APP-BCA1751 – Virtualizing Oracle: Caging the Licensing Dragon | UP2V

  2. Pingback: Save money by virtualizing Oracle « Dirty Cache

  3. 3

    Roger

    Hello Viktor and thank you for your insight around this topic.
    As you pointed out, the OLSA states you have to license all processors where the Oracle programs are installed and/or running on. It’s that simple. I’m afraid it still isn’t really that simple, well at least not for me…. as I’m trying to get the following something clear and haven’t been able finding any blog around the topic of Oracle licensing as it relates to an Active/Passive Microsoft failover cluster deployment and subsequently having this whole concept virtualized on vSphere.
    Taking into account a 2-node dual/quad CPU machine setup following OLSA statement would make me believe I require 2* (8*0.5) = 8 CPU Licenses.

    Now my Oracle rep is telling me that in a Microsoft Failover cluster one does not need to pay CPU licenses on the standby node thus a 4 CPU license requirement suffice instead of 8 licenses as OLSA rule would dictate? Please advise, thanks!

    Reply
  4. 4

    viktorious

    Hi Roger. Of course I cannot make any official statement, but I would say your Oracle rep is right.

    There’s a thing called the 10 day rule: http://www.viktorious.nl/2012/03/30/licensing-oracle-or-sql-server-on-vmware/ which might be applicable in this case…although we can discuss the validity of this statement because it’s in a document which also contains the disclaimer mentioned in this article. Nevertheless as long you’re running an active/passive scenario (and you can prove this), you should be right. The virtual machines should be pinned to one vSphere host, and not be vMotioned…

    If you want to be 100% sure…just ask Oracle:)

    Reply

Leave a Reply to Roger Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.