I’ve continued to play around with Cloud Control 13c and I’m generally getting a nice vibe from it.
One of the things I really hated about Grid Control 10g and 11g was the navigation. It felt like you had to click on 50 links to get to the thing you wanted. When Cloud Control 12c came along and had a main menu it was a massive improvement. Even so, it was still a little annoying as the menu was split, with some bits on the left and some bits on the top-right.
In Cloud Control 13c, these menus have been brought together into the top-right of the screen.
Oracle Enterprise Manager Cloud Control 13c Release 1 (220.127.116.11.0) was released a few days ago. Does that have the acronym “oemcc13cr1”?
As usual, my first steps are to do some basic installations. The approach is pretty similar to the 12c installations, but it’s a little greedier now.
Since the upgrade to Cloud Control 18.104.22.168, we’ve been having a couple of issues, mostly around EMCLI.
Some of our databases use Service Guard, so you don’t know which node they are running on. Rather than having an agent per package, we have one on each node. One of my colleagues wrote a little script to check which node the instance is running on, and relocate it if it has moved. This is done using EMCLI and was working fine before the move to 22.214.171.124. Since the upgrade it’s been rather erratic. It would work for a while, then fail. After watching for a while I noticed a couple of things.
I mentioned a couple of months ago I was planning to upgrade our production Enterprise Manager Cloud Control installation from 126.96.36.199 to 188.8.131.52. Well, today was the day. I held back a while because I knew I would be out of the country for a while on the Latin America tour and I didn’t want to make a big change before I ran away.
A couple of weeks ago I wrote a post about doing a Cloud Control 12cR5 installation and said I would be testing the upgrade from 12cR4. I’ve now done that.
I’ve done a couple of play installations of EM12c 184.108.40.206, just to get a feel for it. You can see the result of that here.
From an installation perspective, everything was pretty similar to the previous releases. I tried the installation on both OL5 and OL6, in both cases using 12c as the database repository. No dramas there.
A couple of things of note.
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.
I’ve already written about the 12cR3 to 12cR4 upgrade here. I did a few run through’s at home to practice it and it all seemed good.
Setting The Scene
Just to set the scene, for our production environment we run Cloud Control in a VMware virtual machine, using Oracle Linux 6.5 as the quest OS. With that setup, we can use a simple installation (DB and OMS on the same VM) and use VMware to provide our failover, rather than having to worry about multiple OMS installations and any DB failover technology etc. If there’s one thing I’ve learned about Cloud Control, it’s Keep It Simple Stupid (KISS)! As far as our managed servers go, most of our databases and all our middle tier stuff runs on VMware and Oracle Linux too. We have a handful of things still hanging around on HP-UX and Solaris, which will hopefully be migrated soon…
I’ve started to play around with Enterprise Manager Cloud Control 12R4. The clean installations on Oracle Linux 5 and Oracle Linux 6 were really easy. You can see how I did them here.
I used 220.127.116.11 as the database repository. I’ll probably have a go with a 12c database in future, which is now supported, but my main focus this time was to check out something similar to what I have at work. Forgive my caution, but I’ll not be using 12c database for my EM repository for a while yet. Cloud Control is too important to risk…