I didn’t think there would be quite so many posts about this journey, but we finally have Cloud Control 13cR2 in production, monitoring all our Oracle Database and WebLogic servers, and scheduling all our database backups.
Here are some of the posts that came out when I thought we would be using 13cR1.
And here is what I posted since 13cR2 was released.
All my 13c articles are here.
As I mentioned in some of the previous posts, we’ve gone for a slash & burn approach. We were running 12cR5 across the board. We built a new 13cR1 server, which subsequently got upgraded to 13cR2. Some of the early 12cR5 to 13cR1 agent upgrades didn’t go so well, so instead we removed the old agents and installed new ones. I used EMCLI to export some of the config, like backups definitions, so the transfer was pretty easy.
Remember, we are a pretty small company and we mainly use Cloud Control for monitoring and backups, so this replacement approach was relatively easy for us. If you are monitoring thousands of servers and use more of the Cloud Control features you may not want to take this approach. 🙂
Anyway, yesterday we got the 13cR2 agents installed on the last group of production servers, so we have completed the move!
I’m hoping there will be some time before 13cR3 is released. 🙂
I delayed our upgrade from Cloud Control 13cR1 to 13cR2 until I finished all my travelling. It’s not really fair to make a major change then swan off round the world. 🙂
Yesterday was the day. I got in and started the upgrade, following the process I documented here and it worked. 🙂
I guess I shouldn’t be surprised. I had tested it all at home anyway.
We now have Cloud Control 13cR2 monitoring all out Dev and Test systems. For the next few days we’ll be kicking the tyres before continuing to roll it out to production, which is still currently monitored by Cloud Control 12cR5.
You can read my notes about this stuff here.
There are some related blog posts on this subject here.
Oracle Enterprise Manager Cloud Control 13c Release 2 (13cR2) was released a couple of weeks ago. In a previous post I mentioned we were going to stop our rollout of 13cR1 agents to production and upgrade from 13cR1 to 13cR2 before we resumed.
I don’t like doing anything at work that I haven’t already tried at home, so the first step in that process was for me to do some clean installs and practice upgrades. After a busy weekend and a late night last night I think I’m happy with the process. That resulted in these articles.
If you’ve done a 13cR1 installation, the clean 13cR2 installation will come as no surprise. They now have multitenant and non-CDB repository templates to choose from. I used the multitenant template in this example. The installation was fine on both OL6 and OL7, so nothing out of the ordinary to report there.
The upgrade process was similar to previous point release upgrades too. We used the non-CDB template, the only one available at the time, to build our 13cR1 installation, so not surprisingly I practised the upgrade using that as a starting point. The upgrade process went fine, but I got a lot of warning messages during the process. It was all working fine at the end though…
I guess we will start rolling this bad-boy out once I get back from the APAC Tour and Bulgaria (BGOUG).
We’ve finished the rollout of 13cR1 agents to all dev and test environments, but haven’t started the production rollout. Good job really as 13cR2 has now been released.
The announcements are here.
The downloads and documents are here.
My plan is now:
- Stop the rollout of 13cR1 to production.
- Test the clean install of 13cR2 and the upgrade of 13cR1 to 13cR2 at home. Articles will be coming soon.
- Play about with it until I’m happy.
- Upgrade the existing 13cR1 to 13cR2 and upgrade all the existing dev/test agents.
- Gain some confidence in the new installation.
- Roll it out to production.
Let’s hope I get this done before 13cR3. 🙂