I suppose I should, for the sake of completeness, say that a replicated
database isn't quite the same as a standby database. If the primary blows
up, then you will only have data in secondary up to the point that that last
replication cycle ran. But I figured you already knew that. If you try to
replicate "too often" (like every ten seconds), you'll probably kill
performance. You don't want to set the time between replication cycles to
be too long either since the MLOG$ tables can grow which (I think, but not
absolutely positive) slows down replication because your updates scan the
MLOG$ tables up to the high water mark. If for some reason, you can't
replicate for a while, and your MLOG$ tables get huge, I've had success
rebuilding them online.
Please see the official ORACLE-L FAQ:
http://www.orafaq.com
To unsubscribe send email to: oracle-l-request_at_freelists.org
put 'unsubscribe' in the subject line.
--
Archives are at
http://www.freelists.org/archives/oracle-l/
FAQ is at
http://www.freelists.org/help/fom-serve/cache/1.html
Received on Wed May 26 2004 - 17:17:17 CDT
