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

From: Michael Dinh <mdinh_at_XIFIN.Com>
Date: Sat, 18 Jun 2011 09:26:35 -0700
Message-ID: <>

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

From: [] On Behalf Of Tim Gorman [] Sent: Friday, June 17, 2011 3:59 PM
Subject: Re: archived log switch


The only session-level redo information is the real-time information in V$SESSTAT; I don't think there is anything usable in AWR. Query V$SESSTAT (via a join from V$STATNAME for the statistic name via the column STATISTIC#) for a statistic like "redo size" in order to identify a session (or sessions) generating a lot of redo, the join back to V$SESSION and figure out to whom that session (or those sessions) belongs, what it is executing, etc.

Good luck!

Tim Gorman

consultant -> Evergreen Database Technologies, Inc.
postal     => 13087 West Cedar Drive #225, Lakewood CO 80228
website    =>
email      =><>
mobile     => +1-303-885-4526
fax        => +1-303-484-3608
Lost Data? => for info about DUDE...

On 6/17/2011 4:27 PM, Michael Dinh wrote: All of a sudden, we are experiencing 10x the number of archived logs switch

Does anyone have ideas on how to identify what is causing so many archived logs?


Michael Dinh

NOTICE OF CONFIDENTIALITY - This material is intended for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. BE FURTHER ADVISED THAT THIS EMAIL MAY CONTAIN PROTECTED HEALTH INFORMATION (PHI). BY ACCEPTING THIS MESSAGE, YOU ACKNOWLEDGE THE FOREGOING, AND AGREE AS FOLLOWS: YOU AGREE TO NOT DISCLOSE TO ANY THIRD PARTY ANY PHI CONTAINED HEREIN, EXCEPT AS EXPRESSLY PERMITTED AND ONLY TO THE EXTENT NECESSARY TO PERFORM YOUR OBLIGATIONS RELATING TO THE RECEIPT OF THIS MESSAGE. If the reader of this email (and attachments) is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. Please notify the sender of the error and delete the e-mail you received. Thank you.
-- Received on Sat Jun 18 2011 - 11:26:35 CDT

Original text of this message