Re: archived log switch - detecting who’s causing excessive redo generation
- From: Tanel Poder <tanel@xxxxxxxxxxxxxx>
- To: mdinh@xxxxxxxxx
- Date: Sat, 18 Jun 2011 22:03:28 +0300
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@xxxxxxxxx> 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 who’s 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@xxxxxxxxxxxxx [oracle-l-bounce@xxxxxxxxxxxxx] On
> Behalf Of Tim Gorman [tim@xxxxxxxxx]
> Sent: Friday, June 17, 2011 3:59 PM
> To: oracle-l@xxxxxxxxxxxxx
> Subject: Re: archived log switch
>
>
Other related posts:
