I recently consulted for a customer who was in the process of deploying a new Oracle instance for their production ERP system.
When they brought up the fact that they had an organizational directive to only deploy new solutions on their VMware Infrastructure the Oracle Sales Rep and Sales Engineer promptly said “YOU CAN’T DO THAT, Licensing will burn through your entire budget! You have to license ALL THE THINGS! (Things in this case being every core in the cluster)”
Yea, that’s not only false, it’s a downright lie. Any Oracle employee and even most resellers you come across will tell you that in order to run Oracle DB on a virtual infrastructure other than Oracle’s own, you’ll need to license every core in a cluster because Oracle cannot guarantee where the processing for a virtual machine running their software is.
In actuality, there is NOTHING in an Oracle License and Service Agreement (OLSA) that indicates you have to license their software that way.
Per Michael Webster’s blog…
Ask your Oracle contact the following and get a response in writing.
“Is the contract that we have signed for Oracle Software Legally Binding on both of us?”
“Does the contract supersede all prior agreements both verbal and written?”
“Can the contract be modified or altered in any way, other than in writing, and being agreed to and signed by both of our authorized representatives?”
“Does the contract form the complete agreement?”
“Where in the contract does it state we must license processors that are not running Oracle software?”
“Where in the contract does it state anything with regards to Hypervisor, VMware, vCenter, Cluster, Live Migration or vMotion?”
After you get your answers to these questions in writing and Oracle admits that you don’t owe them a dime more in licensing for any servers that do not and have not run Oracle software, go on about your daily business. You are now assured that there is no way Oracle can charge you for anything more than what you’re actually using. They can’t charge you a penny more for licenses other than where Oracle software is installed and/or running. There is no mention of Hypervisor, VMware, vCenter, Cluster (except referring to Oracle RAC), Live Migration or vMotion anywhere in your OLSA contract. So that simply can’t be applicable to you, as clearly, the contract and it’s explicitly referred to documents, are all that matter.
So, next time you or your customer is interested in virtualizing Oracle on non Oracle hardware / software remember you have every right to!
Here’s an announcement for all of you VDI administrators out there. VMware has recently released a new version of their awesome OS optimization tool for Horizon View.
- Windows 10 template (beta)
- Login time optimization, for Windows 7, Window 8, Windows 8.1.
- Visual effect correction, now works for both current user and new users. This change applies to Windows 7, Windows 8, Windows 8.1.
- Some items are not selected by default, for better compatibility or user experience. You can still select them on demand.
- A reference tab is added for OSOT Fling home site, as well as other optimization materials.
- Drop old product support (View 5.3).
- UI enhancement: optimize product compatibility settings.
- Issue fix: When UAC is enabled, incorrect message shows in command line mode.
- Windows 8: hide fast user switching
- Windows 8: disable welcome screen
- Windows 8: change item recommendation level: Disable Windows Update service: recommended -> Optional. Update description.
- Windows 7 & 8: Fix item: “Disable IPv6”, according to https://support.microsoft.com/en-us/kb/929852
- Windows 7 & 8: Add optional item to disable visual effects. By default these items are NOT selected.
- Windows Server 2008-2012: add item to disable Windows Update service.
Template & GUI
- Windows 7-8 template has been separated into two templates.
- Template is automatically selected based on the target OS (for both local analysis and remote analysis)
- MasterTemplate is removed
- Remove description column in history view
- Remove template content view on remote analysis panel
- Rename most of optimization items. Sort items in alphabetical order
- Simplify the GUI. Two “Set” buttons have been removed. The XML content is update on the fly with user input.
- Mandatory fields are marked with a red “*”
- Add a new field: default selected
- Add a new Save button, which is enabled for custom templates, and is disabled for built-in (readonly) templates.
- Context menu added for each step node
- Add menu item Remove for group node
- Disable Remove button for the top level
- Adjust column width for better text display
- Prevent user from removing top level group node
- Update up and down icon
- Label icon now has the same context menu as label (tree view)
- Field Step Type has been removed for group node (unnecessary)
- Title of HKCU operations has been changed according to command name (LOAD/UNLOAD), for consistency
- Missing icon on optimization result
- Add feature “product compatibility”. A dialog is added before analysis to ask user for in-use VMware products/features. The information is used to tweak optimization items. For example, if Persona Management is selected, the expected status of Volumn Shadow Copy service is AUTO, rather than the default DISABLED. Currently the configuration covers only Persona Management and View 5.3 Fixpack.
- Add template capability: default selection state (XML attribute of step node: defaultSelected). You can specify which item is not selected by default in a template.
- By default, item “Disable Windows Firewall Service” is not selected, and the severity level has been lowered from MANDATORY to RECOMMENDED. Disabling Windows Firewall prevents some software from installing correctly.
- Fix optimization items
- Customer Experience Improvement Plan (CEIPenable)
* Disable Diagnostic Service Host (WdiServiceHost)
* Interactive Services Detection (UI0Detect)
* Disable Windows Media Center Network Sharing Service (WMPNetwrokSVC)
* Fix blank items
- Add MasterTemplate back. This will fix the error message when using Remote Analysis.
- Minor model dialog tweak for progress bar dialog.
- Update manifest for OS compatibility.
- Include build version. So you can identify whether the tool you have has the correct level.
Download and play with it here : https://labs.vmware.com/flings/vmware-os-optimization-tool
Recently I was working on our lab in the office after upgrading our hosts to vSphere 6.0 and needed to change the Disk.SchedNumReqOutstanding values to 256. However this value has changed in 6.0 to NoofoutstandingIOswithcompetingworlds.
There are a lot of PowerCLI scripts out there to set this value for all of your XtremIO luns, however in 6.0 there were additional values added to storage.core.device.set.
So here’s a PowerCLI script that will connect to your vCenter server, enumerate your hosts, and modify the Disk.SchedNumReqOutstanding value to the EMC recommended 256.
Connect-VIServer -Server VCENTER_IP -User USERNAME -Password PASSWORD
$hosts = get-vmhost
foreach ($esx in $hosts)
$esxcli=get-esxcli -VMHost $esx
$devices = $esxcli.storage.core.device.list()
foreach ($device in $devices)
if ($device.Model -like "XtremApp")
$esxcli.storage.core.device.set($null, $null, $device.device, $null, $null, $null, $null, $null, $null, $null, $null, 256, $null, $null)
This afternoon while deploying the Symantec Virtual Appliance for vShield for a customer I ran into an issue after the initial deployment where the appliance could not connect to the configured network in the configuration file.
For whatever reason, the appliance is configured for the default route of the private vmservice-vshield-pg network instead of the specified Network in the config file.
In order to get the appliance talking correctly to the Symantec Endpoint Protection Manager I had to remove the gateway for ETH1.
Login to the console of the appliance with the username admin and the password you specified during deployment.
Then type sudo su – and press enter, enter your admin password again and now you’re root.
Edit the ETH1 config by typing the following command.
Cursor down to the GATEWAY=169.254.1.1 and press your D key, and then D key again.
Write out the file by pressing the following keys in order… : w q ENTER
Now it’s time to restart the networking service… enter the following command service network restart
Attempt to ping your Symantec Endpoint Protection Manager IP now and if you get a reply you’re all good.
This is only going to be an issue in the event that your SEP SVA is on a different network than your SEP Manager Server.
Let me know if this worked or didn’t for you, and I’ll be happy to research a little more.
Earlier today I was setting up vCenter Server Appliance 5.5 in the lab and ran into an issue getting Active Directory authentication working.
After joining to the appliance to the domain via the admin URL, I attempted to entitle some users to vCenter, however when clicking on the domain identity provider I received the following error…
Error: Idm client exception: Operations error
Doing some research it appears the Single Sign On service uses DNS Reverse PTR records to communicate with the domain controllers, so ensure that you have reverse DNS entries for both your vCenter Server Appliance as well as your Active Directory Domain Controllers!