@Pete thanks for that info. Are there any plans in the future release of OEM for the funcanality ? As i am sure there are a lot of sites out there running on unsupported version... @Tim/Maaz Thanks for that info on Metric Extentions. I am going to make use of that for now. I guess it would just be nice to have everything under one umbrella. As we make use of the "Performance tab" a lot and other things. On Mon, May 5, 2014 at 5:31 AM, Maaz Anjum <maazanjum@xxxxxxxxx> wrote: > Max, > > I have had to use two OEM's before for the same reason as yours at a > customer site. > > However, there were still a few unsupported (by em12c) database versions > on certified host platforms where I used Metric > Extensions<http://maazanjum.com/2013/12/09/a-useful-metric-extension-in-em12c-for-unsupported-oracle-database-versions/>from > a host perspective to monitor their status and tablespace usage. You > "could" modify the script in my post that checks the instance status via a > tnsnames alias instead of a local connection. Looking back at the > customer's configuration, I ended up installing the 12c agent on the 11.11 > platform and deployed the aforementioned Metric Extension. Though, I don't > think this is supported. > > Likewise, you could set up a "ping" and "df" Metric Extension to the 11.11 > host from, let's say, the EM host target. > > I think Tim is correct, and that I have heard the same from someone else > as well. Sadly, I do not have any documentation for it :( > > Cheers, > Maaz > > > On Mon, May 5, 2014 at 3:53 AM, Tim Hall <tim@xxxxxxxxxxxxxxx> wrote: > >> I just read that back and what I was saying was unclear. >> >> So we had a 12c agent on box A monitoring an instance on box B... >> >> As I said, long time ago and I didn't write down what I did, so it >> officially does not exist. :) >> >> Cheers >> >> Tim... >> >> >> On Mon, May 5, 2014 at 8:42 AM, Tim Hall <tim@xxxxxxxxxxxxxxx> wrote: >> >>> Correct me if I'm wrong, but isn't it possible for an agent to monitor >>> some aspects of a remote system? I'm sure we did this under 12c once for an >>> old system that had not been upgraded yet. It was a while ago and they >>> system has been upgraded now, so I don't have anything to refer back to, so >>> my memory could be failing me... :) >>> >>> Cheers >>> >>> Tim... >>> >>> >>> On Mon, May 5, 2014 at 8:12 AM, Peter Sharman >>> <pete.sharman@xxxxxxxxxx>wrote: >>> >>>> No it will not work. Pre-12c agents cannot communicate with a 12c >>>> OMS. >>>> >>>> >>>> >>>> Pete >>>> >>>> [image: Oracle logo] >>>> >>>> Pete Sharman >>>> Principal Product Manager >>>> Enterprise Manager Product Suite >>>> 33 Benson Crescent CALWELL ACT 2905 AUSTRALIA >>>> >>>> Phone: +61262924095 | | Fax: +61262925183 | | Mobile: *+61414443449 >>>> <%2B61414443449>* >>>> ------------------------------ >>>> >>>> "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 >>>> ------------------------------ >>>> >>>> >>>> >>>> *From:* max scalf [mailto:oracle.blog3@xxxxxxxxx] >>>> *Sent:* Sunday, May 4, 2014 6:17 AM >>>> *To:* oracle-l@xxxxxxxxxxxxx >>>> *Subject:* oem 12c on hp-ux pa-risc 11.11 >>>> >>>> >>>> >>>> Hello List, >>>> >>>> >>>> >>>> I have a question and maybe some of you guys are already doing this(or >>>> not). We have some old HP-UX PA Risc(11.11) and i want them monitored with >>>> our new OEM 12c(12.1.0.3). Looking at the certification matrix looks like >>>> 11.11 is not supported with the 12c agent. >>>> >>>> >>>> >>>> I have one thing i have done in the past, where i wanted to monitor our >>>> old pa-risc(11.11) box from Grid control version 11.1.0.7. I was unable to >>>> deploy 11g agent as well(due to support issue, pa-risc 11g agent only >>>> supported pa-risc 11.23 and 11.31). So as a worked around I deployed >>>> 10.2.0.5 agent on that old pa-risc 11.11 box and got it connected to 11g >>>> grid control. >>>> >>>> >>>> >>>> Most of these old box run DB version 10.2.0.4 or 10.2.0.5. I am not >>>> sure if i can still do this with OEM 12c? where i can either re-deploy(or >>>> point them to 12c OEM) 10.2.0.5 agent on these old 11.11 box. Obviously i >>>> am sure you guys are probably asking why are you asking here, why not just >>>> try it and find out yourself as you have already done this before. >>>> >>>> >>>> >>>> That's were i am stuck. Our team/Management do not want me to do that >>>> and they are okay with using 2 different OEM(11g grid of all these old box >>>> and 12c for newer version). I think if we can make this work, then we do >>>> not have to deal with 2 different OEM versions and everything will be under >>>> one umbrella. >>>> >>>> >>>> >>>> I just wanted to post this out here and see what people have to say, so >>>> at the least i can point our team/management to right direction. >>>> >>>> >>>> >>>> Is anyone monitoring there old hp-ux pa-risc 11.11 box with OEM 12c, if >>>> so what are you doing? >>>> >>>> >>>> >>>> Any pointers would be appreciated. >>>> >>> >>> >> > > > -- > A life yet to be lived... >