Yes, that is what I was saying, however large rows or tables with a lot of indexes would also be prone to generate more redo, that is why I suggest joining DBA_TAB_MODIFICATIONS to DBA_TABLES to get avg_row_len and DBA_IND_COLUMNS to get the total # of columns indexes on the table, the thought being the more columns the more likley updates, inserts and deletes will cause index generated redo. See my other post for the solution (SQL) I came up with.
- Ethan -----Original Message----- Sent: Friday, February 21, 2003 10:44 AM To: Multiple recipients of list ORACLE-L It might work to turn on monitoring on the tables. alter table xyz monitoring; Then periodically check dba_tab_modifications. -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Post, Ethan INET: [EMAIL PROTECTED] Fat City Network Services -- 858-538-5051 http://www.fatcity.com San Diego, California -- Mailing list and web hosting services --------------------------------------------------------------------- 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).
