I'd start with using the data out of V$SESS_IO.
[EMAIL PROTECTED]> desc v$sess_io Name Null? Type ------------------------------- -------- ---- SID NUMBER BLOCK_GETS NUMBER CONSISTENT_GETS NUMBER PHYSICAL_READS NUMBER BLOCK_CHANGES NUMBER CONSISTENT_CHANGES NUMBER I believe there is a high degree of correlation between "CHANGES" and the generation of redo logs. Once you have the SID of the culprit(s), it is easy identify the SQL involved. David Jones wrote: > > Dear Listers: > > Any way (other than LogMiner) to easily identify what sql statements running > now are generaing > archived logs ? I have suddenly a lots of archived logs generated and almost > fillup my file system. > > TIA -- Charlie Mengler Maintenance Warehouse [EMAIL PROTECTED] 10641 Scripps Summit Ct. 858-831-2229 San Diego, CA 92131 There are no stupid questions, but there are many inquisitive idiots! -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Charlie Mengler INET: [EMAIL PROTECTED] Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Lists -------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
