EM Cloud Control 12c : The 24 Hour DBA


I think I’ve lived through all the ages of Enterprise Manager. I used the Java console version back in the days when admitting you used it got you excommunicated from the church of DBA. I lived through the difficult birth of the web-based Grid Control. I’ve been there since the start of Cloud Control. I’ll no doubt be there when it is renamed to Big Data Cloud Pixie Dust Manager (As A Service).

I was walking from the pool to work this morning, checking my emails on my phone and it struck me (not for the first time) that I’m pretty much a 24 hour DBA these days. I’m not paid to be on call, I’m just a 9-5 guy, but all my Cloud Control notifications come through to my phone and tablet. I know when backups have completed (or failed). I know when a Tnsping takes too long. I know when we have storage issues. I know all this because Cloud Control tells me.

Now you might look on this as a bad thing, but being the control freak I am, I prefer to get a message on a Sunday telling me something is broken, hop on the computer and fix it there and then, rather than coming in on Monday to a complete sh*t-storm of users complaining. I’m not paid to do it, but that’s the way I roll.

While walking down memory lane I was thinking about all the scripting I used to do to check all this stuff. Endless amounts of shell scripts to check services and backups etc. I don’t do hardly any of that these days. Cloud Control handles all that.

We are a pretty small Oracle shop, but I think life would be a whole lot more difficult without Cloud Control. I’ve mentioned this a number of times, but it’s worth saying again… If you have more than a handful of Oracle databases, you really should be using Cloud Control these days. It’s as simple as that.

Just in case you are wondering, this is how our infrastructure looks this morning… 🙂




Author: Tim...

DBA, Developer, Author, Trainer.

3 thoughts on “EM Cloud Control 12c : The 24 Hour DBA”

  1. Wow, it’s hard to believe that it’s possible to achieve this 100% infrastructure health. How many databases do you have registered there ?

  2. stee1rat: We have a little over 400 targets, which includes databases and application servers. The app servers register a few targets per server, so it’s a pretty small shop.

    As I mentioned on Twitter, the upgrade to solved a number of our false “Unknown” and “Down” targets. Since the upgrade it has reported correct for everything… So far… 🙂



  3. I’ve been relying more and more on grid control 12c.
    The MSSQL plugin is still horrendous, compared to what M$ own products do. But I’d rather have everything under the same ceiling, so to speak, than chase up different products.
    The Oracle side is OK-ish, although there are some aspects of it I just don’t hate.
    The whole setup and menu structure is horribly kludgy and obviously thought out by folks who have never had to run it to manage their own centres, in a flexible and evolving environment.
    For example: change a dns name for a server and enjoy the pain of having to drop all info from the previous agent config and create a whole new one.
    Why on earth is this not a simple option in a menu somewhere?
    What, changing a dns name for a server never happens in IT?
    What, simplifying work isn’t a target of OEM?
    It’s simple, day-to-day things like this that still let it down. But I’m persevering and making it more and more part of our integrated monitoring. It’s got some very useful screens.
    And I’d hate to have to cope with Pete Sharman’s yapping if we dropped it! 😉

Comments are closed.