Re: archived log switch - detecting whos causing excessive redo generation

From: Tanel Poder <tanel_at_tanelpoder.com>
Date: Sat, 18 Jun 2011 22:03:28 +0300
Message-ID: <BANLkTimaKrwuyPT8SbwpweuasOOSCz4Cdw_at_mail.gmail.com>



Yeah, V$SESSTAT / Snapper sure beat logminer and other approaches if you want to troubleshoot fast!

On Sat, Jun 18, 2011 at 7:26 PM, Michael Dinh <mdinh_at_xifin.com> wrote:

> Even though the problem has been resolved, I am still researching for
> methods to better identify and came across this.
>
> Oracle Troubleshooting with Snapper detecting whos causing excessive
> redo generation
>
>
> http://blog.tanelpoder.com/2008/05/30/oracle-troubleshooting-with-snapper-detecting-whos-causing-excessive-redo-generation/
> ________________________________________
> From: oracle-l-bounce_at_freelists.org [oracle-l-bounce_at_freelists.org] On
> Behalf Of Tim Gorman [tim_at_evdbt.com]
> Sent: Friday, June 17, 2011 3:59 PM
> To: oracle-l_at_freelists.org
> Subject: Re: archived log switch
>
>

--
http://www.freelists.org/webpage/oracle-l
Received on Sat Jun 18 2011 - 14:03:28 CDT

Original text of this message