RE: 12c grid control
- From: Peter Sharman <pete.sharman@xxxxxxxxxx>
- To: Oracle-L Freelists <oracle-l@xxxxxxxxxxxxx>
- Date: Tue, 2 Jul 2013 08:54:16 -0700 (PDT)
Man, you guys! I take a couple of days off outta here to handle
DB12c/EM12.1.0.3 release stuff and you go crazy on me! :)
OK, let me try to summarize a lot of what's gone on here in a single email in
no particular order of relevance.
1. DB12c is clearly out, and there is some confusion out there about which was
which (DB12c or EM12c) in these various emails. So let's be 100% clear - EM12c
has been out for a couple of years - clearly DB12c has not. ;) The EM12.1.0.3
release which has also just come out does indeed have support for DB12c built
into it already. That is one of the main advantages of the re-architecture of
the agent we did way back when in the first Production release. All targets
are now managed as plugins and the agent only installs the plugins it needs for
managing the targets on the host the agent runs on. EM12.1.0.3 is available
for download from OTN
(http://www.oracle.com/technetwork/oem/enterprise-manager/downloads/index.html)
and presumably will be added to edelivery.oracle.com sometime soon.
2. There are a number of sites that are now treating EM12c as their primary
monitoring tool, and in fact, treating it as a system that needs to be as
available as their Production sites (after all, if your primary monitoring tool
is down, how the heck do you know when the Production sites are down?) For an
increasing number of sites, that means people are using RAC, Data Guard,
multiple OMS's and Site Guard. Note that one of the changes in 12.1.0.3 is a
different approach to disaster recovery (look for a new whitepaper on OTN on
that today if I get the damn updates done).
3. Just to clarify my position, Nuno hasn't got it quite right (<grin>) - I am
ONE of the product managers for the EM12c product suite (there are about 70 of
us in total). I have USED the product since its 0.76 beta release, but have
only been a product manager for it for the past couple of years - since 12c
came out actually. The whole reason I became a PM at that stage is because 12c
is (to me, YMMV, RTFM etc. etc.) a damn fine product that I can happily talk
about.
4. The remainder of my comments are on the 12.1.0.3 release since there seems
to be some interest in that. Firstly, I manage one of our internal sites that
has two OMS's fronting the repository, around 1500 targets being monitored and
I upgraded that environment to 12.1.0.3 a few weeks back. The reason it had to
wait until then is simply that this site has a lot of history that we have to
keep, so I can't just throw it away (as many of you may know, there is rarely
an upgrade path from one pre-Production release to another - normally you have
to just reinstall). For such a configuration, I had to wait until close to
Production as I have to patch it to Production code, rather than just throw it
away and start with a clean installation. I would say that it was a
relatively straightforward upgrade. In fact, most of the time taken for the
upgrade was in taking backups (and moving them off the machine so I had a
recoverable scenario if I lost the hosts). One thing to be aware of - the
12.1.0.3 release requires 11.1.1.6 of BI Publisher (earlier releases required
11.1.1.5, so there is an upgrade here as well). Having said that, it took me
all of about an hour to do that installation and upgrade our earlier reports,
and a fair chunk of that time was downloading the new version.
5. The following upgrade paths to 12.1.0.3 are supported:
a) 10.2.0.5 to 12.1.0.3
b) 11.1.0.1 to 12.1.0.3
c) 12.1.0.1 BP1 to 12.1.0.3 (note BP1 is mandatory so no upgrade from base to
12.1.0.3)
d) 12.1.0.2 to 12.1.0.3
6. The 12.1.0.3 OMS can support all earlier 12c agents so you can upgrade the
agents at a time that suits you. Having said that, obviously there are
enhancements and so forth that make it worthwhile upgrading the agents as well.
7. All platforms were released on the same date for 12.1.0.3, so there is no
need to wait for the platform releases.
8. If your repository is on 11.1.0.7 or 11.2.0.1, there are mandatory patches
that have to be installed to the databases PRIOR to upgrade. Check MOS for
those patch numbers. Let me know if you can't find them.
Hans, I'd be interested to hear if your specific issue on ASM has been
addressed once you go to 12.1.0.3 which has the right version of the DB plugin
to manage DB12c.
Enough rambling from me. :)
Pete
Pete Sharman
Principal Product Manager
Enterprise Manager Product Suite
33 Benson Crescent CALWELL ACT 2905 AUSTRALIA
Phone: +61262924095 | | Fax: +61262925183 | | Mobile: +61414443449
"Controlling developers is like herding cats."
Kevin Loney, Oracle DBA Handbook
"Oh no, it's not, it's much harder than that!"
Bruce Pihlamae, long term Oracle DBA
-----Original Message-----
From: Steve Harville [mailto:steve.harville@xxxxxxxxx]
Sent: Monday, July 1, 2013 11:41 PM
To: tim@xxxxxxxxxxxxxxx
Cc: dbvision@xxxxxxxxxxxx; Oracle-L Freelists
Subject: Re: 12c grid control
*>>>Resilience is a good point, which can potentially stop cloud control being
a free product.* *>>>We will soon replace this by installing a single VM with
both DB and management server. We will use VMware to provide resilience here.*
Hi Tim,
We are doing the same thing except we are using an Oracle VM on Exalogic.
We may move it to VMware in the future. The OEM/RMAN repository is the only
Oracle DB running on the hardware so no extra licensing costs are involved.
Steve Harville
http://SteveHarville.com
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
Other related posts: