Re: Tools/monitoring question

From: Sidney Chen <huanshengchen_at_gmail.com>
Date: Fri, 19 Jul 2013 13:09:10 +0800
Message-ID: <CAM_ddu9-T99v5pP4Mxz8-4DrzexmJLKKAyT25bBhQEzdShJezg_at_mail.gmail.com>



ASH output from snapper.sql across the RAC is good enough for me. _at__at_snapper ash=inst_id+sid+username+machine+service_name+sql_id+event 5 1 all_at_*

On Fri, Jul 19, 2013 at 1:43 AM, <Christopher.Taylor2_at_parallon.com> wrote:

> Wow - Mumbai is really well done (minus a couple of bugs). Adding to
> toolbox.
>
> Thanks Noons!
>
> Chris
>
>
> -----Original Message-----
> From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org]
> On Behalf Of Nuno Souto
> Sent: Thursday, July 18, 2013 3:08 AM
> To: oracle-l_at_freelists.org
> Subject: Re: Tools/monitoring question
>
> On 18/07/2013 12:57 AM, Christopher.Taylor2_at_Parallon.com wrote:
> > I have come to the realization I've become a little too dependent
> > upon Grid Control for giving me a "quick overview" of system >
> performance. Those colorful graphs are like DBA crack ;) So let's > say
> Grid is down or I'm in an environment where Grid is not > available. I'm
> pretty good with SQL but I still like that overview > that Grid gives me
> where I can quickly identify "blips" related to > performance.
> >
> > I'm curious what tools/scripts you guys have in your toolboxes to >
> give you a quick overview when your favorite tool is unavailable. I > have
> several tools in my toolbox as well, but nothing quite as good > as Grid
> when it comes to giving me that "big picture" view to quickly > see issues
> that are impacting users.
>
> I use Statspack and AWR, with Mumbai as the monitoring tool.
> Mumbai is free and can do its own monitoring, as well as look at SP data,
> AWR data and even ASH.
> (Yes, I *am FULLY aware* that AWR is separately licensed: that is not the
> subject here!) And of course one can run our own home-brew script of choice.
> I sample SP twice a day to give me long-term data for capacity planning.
> Basically, it accumulates forever.
> AWR is sampled every hour and is kept for a week, or in some cases 1 month.
> After that, I let it clean itself out.
> In some dbs, I use EM. Mostly because developers might need access to its
> nice graphics.
> Mumbai does graphics as well, but they are less glitzy and more on the
> practical side.
> Soon to be replaced by EM12c monitoring but that's a subject for the last
> third of this year.
>
>
>
> -- Cheers Nuno Souto dbvision_at_iinet.net.au
>
> --
> http://www.freelists.org/webpage/oracle-l
>
>
>

-- 
Regards
Sidney Chen


--
http://www.freelists.org/webpage/oracle-l
Received on Fri Jul 19 2013 - 07:09:10 CEST

Original text of this message