I’ve done a couple of play installations of EM12c 188.8.131.52, 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.
- The 12c repository template database is a Non-CDB architecture.
- The Weblogic installation uses Java6.
The next step is to try some upgrades from EM 184.108.40.206 (on DB 220.127.116.11) to EM 18.104.22.168, which is what I’ll need for my upgrades at work. The testing is quite time consuming and boring, but it’s got to be done before I can unleash this on the company.
PS. Remember to download from edelivery.oracle.com (in a couple of days) for your production installations. Apparently there is a difference to the license agreement.
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…
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 22.214.171.124 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…
I wasn’t going to bother with an upgrade article because Gokhan Atil wrote a good blog post about the upgrade here. Whilst going through the upgrade, there were a few things I needed to make extra notes on, since I have an terrible memory, so it ended up as a separate article.
Ultimately, you are going to need to read the upgrade docs because there are lots of caveats to think about, depending on what options you use.
Previous upgrades at work were a pain, but we had a more complicated installation with multiple management servers and a separate database. More recently we switched to running a simple configuration (DB and OMS on the same server) on an Oracle Linux VM. That makes doing a trial run of the upgrade at home a more realistic test. Whether it’s an improved Cloud Control upgrade process or the fact this is a single machine setup, the upgrade was really easy. Now that I’ve practiced the upgrade at home, I’m feeling relatively confident doing the upgrade in production. I’ll probably leave it until I get back from Bulgaria (BGOUG). It’s not really fair to change everything and then leave the country…
Funny how there is no mention of the name “Cloud Control” in the latest announcement. Does that mean we are back to calling it just Enterprise Manager again?
Anyway, the latest instalment of EM has been born. The downloads are available on OTN.
I’ve got mine downloading. The past few versions have been relatively easy to install on a clean system, but the upgrades have been a total pig. I’m hoping this one is going to be significantly easier… Sucker…
I did an EM Cloud Control 12cR2 installation at work yesterday. The database repository was 126.96.36.199 on HP-UX and the middle tier was installed on RHEL 5.8. The installation was pretty much the same as the 12cR1 version. Over the next few days I’ll be testing out some of the features to decide if we can move across to it permanently.
Today I did two run throughs of single server installations on Oracle Linux 5.8 and 6.3. There are a couple of minor differences, but nothing to worry about. You can see what I did here:
The installations are a little small, so they are not too fast, but it’s good enough to test things out.
Update: It’s been a while since I used the 12c version, so I’ve had to relearn a few simple things. I thought I might as well write the down in case it helps others.
Enterprise Manager Cloud Control 12c Release 2 was released a couple of days ago for all the major platforms. That in itself is not news any more, but the fact we are going to trial it at work as a replacement for our 11g Grid Control installation is.
It’s in my low priority task list, so I’m not sure I’ll get it all sorted before OOW12, but it is something to look forward too. I know it’s tragic, but I’m quite excited.