FAQ
Hi,

I'm installing a new infrastructure with EM 11g. My past infrastructure was based on EM 10g and was monitoring few solaris clusters with veritas as clustering software. Every database had a private inventory, dedicated ip for listener and for other services and of course a dedicated emagent listening on database ip.

New infrastracture are almost based under linux. CRS is 11.2, scan listener and central inventory are in use, but for some compatibilty problem every database will continue to use a dedicated ip address and agent. Problem is that even installing dedicated agent listening only on database IP, the agent always try to monitor every target available in central inventory and as the 11g agent knows well crs features, try for each target to monitor che whole cluster.

This could not be a problem but IMHO is not really nice. Which is your experience? Have a similar (that should not be so uncommon) structure? How do you manage EM agents?

Just for brainstorming and sharing ideas.

Thanks
Stefano

--
http://www.stefanocislaghi.eu

Sent by BlackBerry® Bold 9700†Ûiÿü0ÁúÞzX¬¶Ê+ƒün– {ú+iÉ^

Search Discussions

  • Dennis Williams at May 11, 2011 at 6:32 pm
    Stefano,

    Perhaps you can describe more clearly the compatibility issue that is
    requiring you to continue dedicated ip addresses?

    Just a thought - perhaps you should consider operating two EM - a legacy EM
    10g to monitor those databases requiring dedicated ip addresses, and a EM
    11g for the databases that have overcome that legacy issue.

    Dennis Williams
    On Thu, May 5, 2011 at 1:40 PM, Stefano wrote:

    Hi,

    I'm installing a new infrastructure with EM 11g. My past infrastructure was
    based on EM 10g and was monitoring few solaris clusters with veritas as
    clustering software. Every database had a private inventory, dedicated ip
    for listener and for other services and of course a dedicated emagent
    listening on database ip.

    New infrastracture are almost based under linux. CRS is 11.2, scan listener
    and central inventory are in use, but for some compatibilty problem every
    database will continue to use a dedicated ip address and agent. Problem is
    that even installing dedicated agent listening only on database IP, the
    agent always try to monitor every target available in central inventory and
    as the 11g agent knows well crs features, try for each target to monitor che
    whole cluster.

    This could not be a problem but IMHO is not really nice. Which is your
    experience? Have a similar (that should not be so uncommon) structure? How
    do you manage EM agents?

    Just for brainstorming and sharing ideas.

    Thanks
    Stefano

    --
    http://www.stefanocislaghi.eu

    Sent by BlackBerry® Bold 9700
    --
    http://www.freelists.org/webpage/oracle-l
  • Jared Still at May 11, 2011 at 7:36 pm

    On Thu, May 5, 2011 at 11:40 AM, Stefano wrote:

    How do you manage EM agents?
    By killing them as soon as they appear.

    Jared Still
    Certifiable Oracle DBA and Part Time Perl Evangelist
    Oracle Blog: http://jkstill.blogspot.com
    Home Page: http://jaredstill.com
  • Don Granaman at May 12, 2011 at 2:06 pm
    My preferred solution also!

    Don Granaman | Phone: 402-361-3073 | Cell: 402-960-6955 | Fax: 402-361-3173 | Solutionary | Relevant . Intelligent . Security

    From: oracle-l-bounce_at_freelists.org On Behalf Of Jared Still
    Sent: Wednesday, May 11, 2011 2:37 PM
    To: Oracle-L Freelists
    Subject: Re: Advice for Enterprise Manager

    On Thu, May 5, 2011 at 11:40 AM, Stefano > wrote:
    How do you manage EM agents?

    By killing them as soon as they appear.

    Jared Still
    Certifiable Oracle DBA and Part Time Perl Evangelist
    Oracle Blog: http://jkstill.blogspot.com
    Home Page: http://jaredstill.com

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
grouporacle-l @
categoriesoracle
postedMay 5, '11 at 6:40p
activeMay 12, '11 at 2:06p
posts4
users4
websiteoracle.com

People

Translate

site design / logo © 2022 Grokbase