Re: 12c grid control
- From: Nuno Souto <dbvision@xxxxxxxxxxxx>
- To: oracle-l@xxxxxxxxxxxxx
- Date: Tue, 02 Jul 2013 21:24:02 +1000
On 2/07/2013 12:25 PM, Hans Forbrich wrote:
> On 30/06/2013 5:54 AM, Nuno Souto wrote:
>> Reasons? Already explained in other replies from Hans.
> Nuno,
>
> What are you talking about?
I don't know what the above quote and comment is for. I don't usually
comment on quotes of individual paragraphs taken out of context and
commented independently. Sorry, but there is a thing called context.
Above, it doesn't exist.
> I was talking about the 12c Cloud Control monitoring software, not
> the 12c Database. And I was referring to the 12.1.0.2 Cloud Control
> software trying to access the 12.1.0.1 Clusterware (including ASM)
> install.
Yeah, I understood that. For ease of understanding and given that Cloud
Control is actually mostly called EM12c, let's call it that way here as
well? Enough with confusion already.
> There is currently nothing that I have detected wrong with the
> clusterware.
Good. I assume you are referring to the one that comes with DB12c.
>
> There was NO incompatibility between the OLD Cloud Control (12.1.0.2)
> and the pre-release 12c Database.
And between EM12.1.0.1 and the said db? You see: the problem is levels
of compatibility in point releases.
Oracle advertises EM12c as "working with all Oracle dbs", they don't
make any specific recommendations about specific levels of releases.
But we all know it's not like that, as the following demonstrates:
> There appears to be a monitoring incompatibility between the OLD
> Cloud Control and the NEW clusterware ASM listener, so tomorrow I
> will be upgrading to the NEW Cloud Control (12.1.0.3) to see if that
> resolves it.
Good, thanks for noting that. And that proves that EM12c and DB12c are
completely compatible, exactly how? Note: EM12c has been out for 2 years
now - about time it was compatible with everything? Yes, I know DB12c
is new - please read through.
Let me see: EM12c can, according to Oracle - it was the first thing I
checked when I heard of it - manage mixed release levels of database
servers, all from one single control source. Yet here we see that -
right now, not in 2 years time! - 12.1.0.1 EM12c can't handle the latest
clusterware. 12.1.0.3 might, and I sincerely hope so.
This brings me back to the point: the combo of EM12c and DB12c is not
ready for widespread use and it is still very much a work in progress in
as much as we still see some incompatibilities and very likely there
will be more uncovered as time goes by. And I'm not throwing in other
DB releases, although my guess is that we'll hear of those as well.
Nothing wrong with that: both are new products.
But it is *my choice* to not waste my time finding those incompatibilities.
First, because I firmly believe they are transient incidents.
Second, because it is a waste of time for me to familiarize with a
product that is still changing - I prefer to learn with a final,
relatively stable release combo.
And I believe - based on past experience since the 90s - that will be
the case 2 years from now.
One would think that this is obvious. But it appears to be the norm in
some quarters to on every new release of whatever, engage in the usual
"disparage the non-immediate-upgrader", or the "non-beta-tester".
Hey, like someone said: it has never worked, it won't ever work. Why
persist the insanity?
> But I am not sure that you are referring the right combination when
> you accuse me of providing 'those' replies.
I don't "accuse" anyone of anything. "Accuse" might be an interesting
term in religious discussions but it is completely out of context in
technical ones.
--
Cheers
Nuno Souto
dbvision@xxxxxxxxxxxx
--
//www.freelists.org/webpage/oracle-l
Other related posts:
