RE: redo curiosity

From: Stephens, Chris <>
Date: Thu, 18 Feb 2010 15:27:30 -0600
Message-ID: <>

It probably doesn't need to be said but just to be sure:

Atomic refreshes are there for a reason. Make sure you understand the repercussions of using that parameter. I don't believe you stated the additional redo as a problem; only that it was different from previous versions. Atom refreshes ensure that you don't end up with empty materialized views.


-----Original Message-----
From: [] On Behalf Of Maureen English Sent: Thursday, February 18, 2010 3:22 PM To: Allen, Brandon
Subject: Re: redo curiosity

Thanks! That's definitely worth a try. I'll add this to our large refreshes to see what difference it makes tonight.

  • Maureen

Allen, Brandon wrote:
> The solution/workaround is to set atomic_refresh=>false so it will truncate the mview table instead of doing a delete. Just search for "atomic_refresh" on MOS and you'll see the relevant notes about this (e.g. 365157.1).
> Regards,
> Brandon


        This message is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable law.  If the reader of this message is not the intended recipient or the employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited.  If you have received this communication in error, please notify us immediately by email reply.

Received on Thu Feb 18 2010 - 15:27:30 CST

Original text of this message