At several companies I worked for, there was a lot of confusion about the licensing model of Oracle. The general feeling was that they paid too much for their use of Oracle products, and they were not certain of their compliancy. This post will try to give some clarity about this issue.
Oracle Enterprise Manager 13C has been introduced as a ‘single pane of glass’. Managing and monitoring all the assets, in or out of the public cloud.
But when creating an RDS- database instance in Amazon’s cloud, it is monitored by Cloudwatch, and it’s not possible to install a so-called Oracle Hybrid Cloud Agent to connect directly to the Oracle Management Service of OEM13c. Luckily there’s a plugin to connect with Cloudwatch. This article will cover the installation of this plugin and connection of OEM13 to the RDS database instance.
At the start of the each year, I always take the time to look back on the year we left behind. Last year, one of my most memorable experiences was Oracle OpenWorld in San Francisco. The event has always been an overwhelming experience, but this year it seemed even more so. I have never experienced such an amount of announcements and innovations, varying in importance and readiness, and all more or less related to the cloud.
A massive technology push to the cloud, a ‘cloud overload’. That could be the management summary of Oracle Open World 2015 (OOW15).
Oracle as software vendor is evolving to a cloud service provider. The force is strong….
Wouldn’t be nice to get regularly informed how (in)compliant you are with Oracle licenses in an easy – centralized – way, and therefore not have to worry about visits of Oracle’s LMS – License Management Services? I think that would be nice for the most of us. Running LMS-scripts on the target databases, hosts and middleware is for now the most thorough way to get informed about possible incompliancy. Or in some cased, using some clever – but informal and mostly incomplete – scripting on the OEM-repository.
But… Oracle is making serious attempts to make this easier, by integrating the LMS-information in the repository of Oracle Enterprise Manager and make this available through a couple of (BI Publisher) reports:
- Database Usage Tracking Report
- Database Usage Tracking Summary Report
When running these reports (Enterprise –> Reports -> BI Publisher Reports) with OEM 18.104.22.168 out of the box, unfortunately no data will be shown. There are some manual configuration and upgrades to be done. In the rest of the post I’ll explain some hurdles you have to overcome to get this working.
By the way, it’s not unthinkable that LMS will accept the outcome of these reports as a valid source for counting the (in)compliancy on a relative short notice.
Suppose the number of Oracle licenses you acquired in the past, is in line with the use. That is, you’re compliant with all the licensing rules Oracle come up with. The license form you use is the so called ‘Full use’ license, this is the most common license form. Everybody happy. But will this change when moving servers, databases or middleware to the public cloud?
Well , ‘It depends…’ :
1. Is the chosen cloud provider an ‘authorized cloud’ by Oracle
2. Are you going to use your own licenses (BYOL = ‘Bring Your Own License’) or is this included in the cloud solution
3. Is the use of the software the same as it ever was
I’ll try to explain this in chapters below.
This post is intended to be a dummy guide, best practices, or whatever you call it… about setting up a network while working with virtual boxes on a desk- or laptop. I was setting up a virtual box environment with several Virtual Boxes on my laptop, and as I’m not a network – specialist, I came across a few annoying things, challenges if you like. And when I was googling around, it appeared to be I’m not the only one, so I felt the urge to share some experiences.
Already published this post on the amis-blog by the way, a long time ago. Decided to publish it also on my own blog.
What I want is the following environment and some elements smells like a subset of the real life:
1. Connect from my laptop to my virtual box through ssh and sqlplus, with fixed ip-address.
2. Simulate a private network, a network between the virtual boxes, also with fixed ip-addresses.
3. Occasionally connect to the internet from within the virtual boxes. To performs a ‘yum update’ and that kind of stuff.
This post has already been published in the past on the AMIS-blog.
To build an Oracle 12C RAC database – on Virtual Boxes – there’s at least shared storage needed for ASM, and a DNS-server for the SCAN-addresses. Several methods can be used for this, but for the storage in my private project I chose Openfiler, an open source management storage tool, on a separate Virtual Box. It’s like a SAN in real life (the complete system will be three Virtual Boxes: two RAC-nodes and 1 storage Virtual Box). Version Openfiler: 2.99.
But what I want is a separate DNS-server, just as in real life. The perfect candidate is to use the separate Openfiler Virtual Box
This post has already been published in the past on the AMIS technology blog.
Once in a while a company wants to know if her Oracle development- and test- environments needs to be licensed. And in a lot of cases this question simply can be answered as: yes, these environments must be licensed. The cases in which these licenses are not needed, are quite rare and a company should verify this with her Oracle representative or an intermediary.
Recently I bumped into such a lucky company, and I thought it’s a good reason to write about this. And as always when talking about licenses please take notice of the disclaimer in this article.
In this post I will first shortly point out why development- and test-environments need to be licensed according to Oracle, try to explain the ‘OTN Development license’ , describe the case of the lucky company and point out some consideration to make the costs of the environments maybe more bearable.