RE: redo curiosity
Date: Thu, 18 Feb 2010 14:35:22 -0700
No problem, I'm sure atomic_refresh=>false will make a big difference in performance and redo size, but just beware of the affect on read-consistency if you're refreshing multiple views and also the fact that anything that queries the MV during the refresh could get zero rows if it queries after the truncate, but before the new rows are inserted. MOS 553464.1 has more detail.
Privileged/Confidential Information may be contained in this message or attachments hereto. Please advise immediately if you or your employer do not consent to Internet email for messages of this kind. Opinions, conclusions and other information in this message that do not relate to the official business of this company shall be understood as neither given nor endorsed by it.Received on Thu Feb 18 2010 - 15:35:22 CST