Re: alter system dump...

> Why do you want to go thru the redo logs to find out about chained
> rows ? Check dba_tables for the column chain_cnt to see which tables
> have chained rows in them. Check v$sysstat (or run utlbstat/utlestat)
> for the statistic "table fetch continued rows" to see if chained rows
> are even a performance issue. Finally, if they are an issue, the do
> "analyze table tablename list chained rows;", delete these rows from
> the original table and reinsert them. If this eliminates the chained
> rows, then they were not chained (only migrated). If you still find
> chain_cnt for that table, then you cannot do anything other than
> increase the block size by rebuiling your database. You will not gain
> anything from identifying statements that are accessing chained rows
> until you fix the chained rows problem itself.
>

Actually, that's not this problem that I want to solve. Transactions that affects chained rows can't be displayed by logminer so I was just wondering if it's possible to get information about this transactions by looking directly in the redo log files. Received on Fri Jun 01 2001 - 05:23:29 CDT