Extracting Redo Log Info/LogMiner/Shareplex

I'd like to be able to extract information about transactions from the redo logs. I've looked at LogMiner, and I know some of Quest Shareplex's capabilities. I have a variety of questions remaining:

If a row is migrated from one block to another (because it no longer fits in the original block), can LogMiner capture the original rowid? From some tests I've run, it appears not, and this prevents the capture of the original row.

Can Shareplex deal with rows which don't have a primary key; putting it another way, can Shareplex replicate updates to a row using the rowid instead of the primary key?

Is there a way, using the rowid which LogMiner returns, to select the corresponding migrated row out of the database -- "SELECT * from TABLE where ROWID = <logminer rowid>" won't work, since the logminer rowid appears to be the physical location of the row. How does Shareplex deal with this issue, if the original rowid isn't available in the redo log -- does this involve setting up some type of extraneous mapping from the original row to the new row?

Are there plans to enhance LogMiner to be more efficient for applications which need to continually process new data in the logs? Currently, LogMiner reads all the way through the log (very resource intensive), even if you only need the last 10 seconds of data.

Thanks Received on Tue Sep 25 2001 - 12:31:55 CDT