In the last post, we endeavored to explain how to go about an Oracle Licensing Audit effectively by meticulously collecting all artifacts needed for the audit.

We recommend as artifacts, Proof of Compute Enclosure , Audit Trail entries and Closing the loop by tying these artifacts to the OLSA , as part of the lists of artifact to collect and store for at least 2-3 audit cycles.

We also concluded that Oracle Licensing Audit should not be taken lightly just as you would for any other software vendor but not special and one does not have to fear it.

This post endeavors to highlight the typical questions customers might have in their minds after reading articles on internet or talking to other colleagues or questions they might have encountered talking to licensing auditors.




Oracle Licensing Journey


During the course of my career as an Oracle DBA and Architect working on Oracle technologies, Oracle licensing was one of the facets of a DBA life I had to go through and really , nothing has changed much.

Working as the Oracle Technologies pre-sales Lead in VMware since 2012 and being the lead Oracle pre-sales field guy, talking to customers and clarifying their questions about Oracle licensing on VMware SDDC is one of my charters.


Let’s start with the most frequently heard questions from customers and we will work our way down.


1) We have been told we will have to license all ESXi servers in Cluster in local site because
a. Oracle counts VMware as a soft partition technology
b. VMware DRS might migrate Oracle VM/s to all nodes in the cluster


This question has been clarified in the first blog post

To summarize, two things to keep in mind about the “Oracle Partitioning Policy”

  • “Oracle Partitioning Policy” is NOT referenced in any way in the OLSA/OMA and hence is not an artifact in any Oracle Licensing discussion
  • Read the disclaimer in the document “This document is for educational purposes only and provides guidelines regarding Oracle’s policies in effect as of April 5, 2016. It may not be incorporated into any contract and does not constitute a contract or a commitment to any specific terms



2) Oracle licensing requires licensing every server in every Site connected to the Primary site where the Oracle workloads primarily resides, starting from vSphere 6.0 because of the cross vCenter vMotion capability.

This question has been clarified in the first blog post

As we already know, there are only 3 documents which are contractual and relevant for any Oracle licensing discussion and contractual:

  • Technical Support Policy
  • Processor Core Factor Table
  • Oracle License and Service Agreement (OLSA)  / Oracle Master Agreement(OMA)
    o    The OLSA/OMA defines Processor as “Processor: shall be defined as all processors where the Oracle programs are installed and/or running.

Notice the use of the word “are, running ”, they are all in the present tense and indicates current usage, not future usage or proposed usage. The above line does not contain words like ‘could, would, might, may’ or any future probable sense.

What this tell us is that we only need pay for current usage, not what can be used!! So just because we have a cross vCenter vMotion capability does not mean we will go ahead and start vMotioning the Oracle VM’s all days long between sites.

The 2nd series of this blog post talks about creating a “Compute Enclosure” i.e. dedicated vSphere Cluster for Oracle workloads which will prevent vMotion events outside the vSphere Cluster.


An interesting anecdote

I suggested to a customer to ask his Oracle Sales Rep this question:

Scenario : Suppose you want into a datacenter which has 100 physical servers, sucking power and dust , all bare metal with OS installed with NO Oracle installed.  You then whip out the Oracle install dvd-rom and install Oracle software on 1 physical server.

The question is , how many servers are liable for Oracle licensing ? 1 ? 99 ? 100

and …prompt came the answer back from the Sales Rep as reported by the customer , the answer is 1.

Really ? Why not 100 ? Maybe the Oracle bits by , magnetic induction , can fly from one server to another to another and hence you may have to pay for all 100 servers ? “That’s a ridiculous statement” was the Sales rep answer.

if the above statement is ridiculous, truly the part where you have to license each and every server in the cluster regardless of whether its running Oracle or not is equally ridiculous 🙂 !!!



To summarize, if this were true in the wildest dreams, it would require us to license EVERY existing vSphere host in EVERY datacenter and cloud , be that yours or a company down the street as vCenter’ s and SSO domains are not an obstacle to vMotion. And by this faulty logic we would need to license every host in the galaxy, good luck with that!!



3) Oracle does not certify Oracle workloads on VMware vSphere / vSAN and doing so will result in a non-certifiable environment

Keep in mind, Oracle Does Not Certify Infrastructure. Oracle does not certify anything below the operating system, Oracle only certifies Oracle Products to the Operating System for e.g RHEL, OEL, SUSE etc

Check the Oracle My Support Compatibility matrix



VMware ESXi is an Enterprise-Class, Type-1 non-Para virtualized hypervisor

To be s/w compliant across the whole stack, ensure that we run

  • A Certified Oracle version on a certified O/S certified for that product (Certification Matrix on Oracle My Support)
  • the Same certified Guest O/S on a certified ESXi version (VMware Compatibility Matrix)

This way, you are complaint and certified by both the software vendors, Oracle and VMware.

Further Oracle has released the “Hardware Certification List for Oracle Linux” which includes support for OEL 7.x/ 6.x on ESXI platform



4) What Audit data do I need to capture for an Oracle Licensing audit and how long should I keep the audit data for?

Here are some of the important artifacts which are useful for an Oracle Licensing audit defense

  • Proof of Compute Enclosure via creating a dedicated vSphere Cluster for Oracle or using Affinity rules to bind Oracle VM‘s to a set of ESXi servers dedicated for Oracle workloads
  • Audit Trail entries which are log file entries for every Oracle VM which shows the Power on /off and vMotion to / from operations.
  • Tie the results of the above audit findings to the Oracle License and Service Agreement (OLSA)

More information can be found in the below blog url:



5a) what if Oracle refuses to open a Service Request (SR) for my case?

Oracle cannot refuse to open a SR for any Oracle on VMware SDDC issue because

  • The customer has signed the Technical Support Policy document with Oracle in which Software Technical Support Policies apply to technical support for all Oracle software product lines.

  • Oracle along with many other companies including VMware, EMC, Cisco are members of this organization “TSANET.ORG”.  Originally established in 1993, TSANet was founded as a vendor neutral global support alliance where companies work together to support mutual customers more effectively. Membership doesn’t simply lower costs and assist with customer support – it improves your customer retention.


Oracle and VMware along with many other companies are members of the star alliance.



5b) Well that’s all good, what if they open a SR but refuse to help with the SR citing FUD reasons?

Oracle Technical Support has been traditionally known to be very professional and has been engaged with VMware Global Support Services (GSS) at all levels to ensure swift resolution for all customer related issues.

In addition to that VMware is committed to the “Oracle Total Ownership Policy”.

VMware Oracle Support provides customers the following new advantages as part of the existing support and Subscription contract at no additional charge:

  • Total ownership of Oracle Database technical issues reported to VMware Support
  • Access to a team of Oracle DBA resources within VMware Support to troubleshoot issues related to Oracle Databases used as a data store or running within a VM
  • Performance tuning and best practices related to Oracle Database used as a data store or running within a VM

Faster resolution of technical issues in VMware environments via a TSANet collaborative support arrangement between VMware Support and Oracle Support.

Details can be found in the below VMware link:


Total Ownership

VMware Support will accept accountability for any Oracle-related issue reported by a customer. By being accountable, VMware Support will drive the issue to resolution regardless of which vendor (VMware, Oracle, or others) is responsible for the resolution. In most cases, reported issues can be resolved via configuration changes, bug fixes, or feature enhancements by one of the involved vendors.

What the above means is, if in any case Oracle Support were to refuse assistance after opening an SR, no need to panic, simply call to open a ticket or open a ticket online with VMware GSS and make sure that the ticket is earmarked for “Oracle DBA team” within the GSS organization.

Oracle My Support Note 249212.1 “Support Position for Oracle Products Running on VMWare Virtualized Environments (Doc ID 249212.1)” also states that for Oracle RAC,  Oracle will only accept Service Requests as described in this note on Oracle RAC and later Releases.



5c) Hmm, ok, how about this ? After an SR number is generated by Oracle TSE and they state the usual FUD, we reach out to VMware GSS and engage them, after both the parties (VMware GSS and Oracle TSE) are involved, will the customers be treated as a ping-pong ball shuttling between both parties for problem resolution with finger pointing?

NO, absolutely not. Apart from the reasons stated in point 5b above , VMware GSS acts as an extension of your IT team , acting on your behalf and resolving this case.



6) What if Oracle asks us to replicate an Oracle on VMware issue on a physical platform?

Oracle reserves the right to require reproduction of the problem on either physical  or virtual environments.

Even in the case of bare metal servers environment , if Oracle support suspects issue is caused by the underlying hardware , then they can request to reproduce the same issue on another physical host with the exact same hardware specifications.

The real reason for the above request is because Oracle has no visibility into the hardware stack i.e. BIOS, Firmware, Drivers, and HBA etc and the fact that Oracle products are only certified to O/S , not hardware, so this is only way they can eliminate hardware related issues.

This is no different from the stance on virtualization with VMware. As stated earlier, to be s/w compliant across the whole stack, ensure that we run

  • A certified Oracle version on a certified O/S certified for that product (Certification Matrix on Oracle MySupport )
  • The same certified Guest O/S on a certified ESXi version (VMware Compatibility Matrix)

This way, you are complaint and certified by both the software vendors, Oracle and VMware.



7) What can you tell me about VMware GSS team?

VMware Global Support Services (GSS) Team is a World Class Support organization with follow-the-Sun Support with warm “hand-offs” and 24×7 Support comprised of All Senior Support Engineers who are former Oracle DBAs.

VMware Global Support Services Overview

The Support process and VMware GSS – Oracle Technical Support engagement process can be depicted by the workflow below


7) What are the things I need not do to be Oracle License complaint ?

Keep in mind the below listed controls demanded by licensing zealots is completely un-necessary and non-contractual.

-Not needed to create Network Segmentation to separate and dedicate a network segment for the vSphere Cluster for Oracle workloads

-Not needed to create Storage Segmentation to zone, map and mask Oracle specific storage LUNS to only the ESXI servers  in the dedicated vSphere Cluster for Oracle



8) Do I need to run any PowerCLI scripts that Oracle LMS asks me to ?

Do not run PowerCLI scripts / commands against the vCenter database which shows all the ESXI servers connected to the vCenter regardless of whether they are part of the vSphere dedicated cluster for Oracle or not.

If you have to run it to gather information about the ESXi servers in the Oracle vSphere Cluster, login as the user who has access to only the Oracle cluster so that way it reduces the scope of discovery to only the Oracle Cluster

This is the document which is handed out to Customers which has information how to gather information about the ESXi servers connected to the Virtual Center , it does not specify running the script against the Oracle vSphere Cluster.



A key point to keep in mind is if this document is really contractual , why is this NOT public facing ?

-Do not give access to any auditor the keys of the kingdom i.e. vCenter username and password

Really, what’s next? Separate the vSphere Cluster for Oracle in its own cage in the data center and ensure no one goes near it!! Throw a black cloth around the cage so that no one can see what’s in it?

Both of the above steps are completely un-necessary as we have well established beyond any reasonable doubt in the previous blog post that Oracle licensing is not Memory, Storage, Cluster, vCenter or Network based, it’s either User based (Named User Plus) or Processor(Socket in case of SE2 or cores in case of EE edition).




In conclusion, there are no issues running Oracle software / products on VMware SDDC as VMware ESXi is an Enterprise-Class, Type-1 non-Para virtualized hypervisor and does not trap x86 binary instructions coming down the stack for purpose of simulation / emulation unlike any other para-virtualized hypervisors.

Further there are no support or certification issues when it comes to running Oracle products n VMware SDDC as explained above.


Need Further Help?

For any additional Oracle Licensing on VMware clarification or help, please reach out to your respective VMware Account teams who can get our team involved in a discussion (Internal VMware folks can reach directly to us at the Tier1-Apps-Sales-Support team mailing list) and we can definitely help guide you and connect you to some of our Premier specialist partners for further discussions.

Oracle on VMware SDDC Collateral
All Oracle on vSphere white papers including Oracle licensing on vSphere/vSAN, Oracle best practices, RAC deployment guides, and workload characterization guide can be found in the url below

Oracle on VMware Collateral – One Stop Shop [Customer]