I admit, I’m a bit of a fan of the Oracle Database Appliance. And I also admit there are some characteristics of the X5-2 ODA’s which made it sometimes a bit hard to fit in the needs of the customer. I’ll come to that later in this post. With the introduction of the two entry-level ODA’s I wrote about in a former blogpost , the ODA X6-2S and the ODA X6-2M, Oracle has made an effort to reach out to the smaller business to fill in their needs. But will it be a succes? This blogpost is about the kind of customer-challenges the ODA (at least one of the series) could be a solution for.
Oracle introduced the ODA X6-2S and ODA X6-2M. And no, they are not the successor of the quite popular ODA X5-2, which we installed and configured quite a number of times lately. These 2 new machines are the in-between ODA’s, entry level machines for small business. Single node with flash storage, also suitable for Oracle Database Standard Edition 2. But…. commodity hardware is also single node and suitable for all Oracle database Editions, so what’s the gap Oracle is filling between commodity hardware and an ODA X5-2? This post will handle the characteristics of the new ODA X6-2 machines and the differences between commodity hardware and the range of Oracle Database Appliances.
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.
Since Oracle Enterprise Manager 12C it is possible to allocate the costs of IT resources to the people of organizations who consume them. This is done through the use of the plugin ‘Consolidation Planning and Chargeback’ .
Pete Sharman wrote an excellent blog about configuring this plugin in Enterprise Manager 12c, and it’s not my intention to copy his work, so I’d like to focus on complementary stuff regarding Oracle Enterprise Manager 13c.
In this article a short note about how simple it is to install the plugin in OEM13c and of course some important new features within the plugin
Be aware that by using this plugin you need the Cloud Management Pack – license!
Developing a solid business case for going to a conference is not always easy. Most of the time the company culture dictates the succes-rate of your attempt.
The necessity for your own development is of great importance to you but is most of the time not the prevailing factor for the company. So how to convince your manager that it is of vital importance for the company that you will attend the conference ?
I never realized in depth the difference between a Linux subscription and a license. Linux is open source, so the software itself is for free. No license to use it is required. But when you buy a Linux support subscription, you are legally entitled to download the ISO images of the binary distribution, download bug fixes, raise bugs and get support from a distributor. Hmm… that sounds pretty much the same as a license. But… with a subscription you can switch to another, cheaper support provider for the same product. It’s quite the same as switching your energy-supplier to another company.
So why not change the subscription of Red Hat Linux to Oracle – without changing a bit of RHEL and no downtime involved. And save money, because the subscription of Oracle looks cheaper (!). The distribution of Oracle Linux is binary compatible with Red Hat Linux, and will provide the same updates and errata.
Is it really that simple to save money? Or are there important pitfalls? Is it worth investigating for Red Hat based datacenters? And … is a Red Hat Linux, maintained by Oracle still a Red Hat Linux, or do you call it Oracle Linux with RHEL compatible kernel? Lots of questions. Let’s take a closer look.
Modifying BI Publisher reports in Oracle Enterprise Manager 13c, e.g. ‘Database Usage Tracking Summary’;
Recently I bumped into an annoying bug in the code of a report, wrote about it a while ago, notified Oracle. And they has confirmed that a new version of this specific report is in development phase.
But.. a report can be modified, so if it’s not that hard, why wait for a patch when you want to use a report you need in the meantime? It is is not advisable to modify a standard report, because undoubtedly there will be other changes in a patch to come (e.g. the datamodel), but as long you are aware of this…..
So I chose to modify my favourite report ‘Database Usage Tracking Summary’ for this blog. And it turned out to be surprisingly simple.
I always thought I could address the main differences between private and public cloud. Oracle announced the ‘Oracle Private Cloud Machine’ at Oracle Open World 2015 which runs locally, offering a private cloud for an organization. Then Oracle decided to rename it to ‘Oracle Public Cloud Machine’.
And I think a public cloud has two important aspects: (1) resources are shared by multiple organizations and (2) services are available through a public network.
Does this new name make any sense? Where does this machine fit in? Is Oracle trying to change the definition of ‘public cloud’? They already renamed the ‘Oracle Virtual Compute Appliance’ to ‘Oracle Private Cloud Appliance’. This post is just a short reflection of my land of confusion.
Still loving the idea to use Oracle Enterprise Manager as a ‘kind of ‘ Software Asset Management Tool, and get regular centralized reports that tells me what Oracle software is running and if there are changes in use of licenses over time. The necessary data is already there in the OEM repository, so there should be standard report facilities to get me informed (other then my own sql-reports from the repository). And guess what, these reports are available.
The Usage Tracking Reports, including the two reports which are important for monitoring the use of licensing, were already present in OEM 12C (wrote about it a while ago) , and I was curious if the usability and functionality improved in OEM 13C (as told me at the demogrounds of OOW2015..).