RE: Materialized views and redo

Paul,

Can't you just specify NOLOGGING for the MView?

Cheers,

Chris


Quoting Paul Vincent <Paul.Vincent@xxxxxxxxx>:


Refresh type is FORCE, refresh mode is PERIODIC. There are 3 indexes on
the MV, but setting them unusable before the refresh and rebuilding
after the refresh would be impractical, since this is an hourly refresh.


Paul Vincent
Database Administrator
Information and Communication Technology
UCE Birmingham
paul.vincent@xxxxxxxxx




                Every time the materialized view is refreshed, this
generates about 40Mb of redo activity, which means our archived logfiles
area is now growing at a rate of around 1Gb per day. For comparison,
before the materialized view was introduced, we only used to get about
50Mb of newly archived log files per day.

                Now, all this redo relates to the refreshing of an
object which can easily be regenerated by simply refreshing the view.
There's no conceivable scenario where this redo would ever be needed.
So, is there any way of completely "switching off" the generation of
redo log entries whenever the materialized view is auto-refreshed? This
would save what's becoming a bit of a disk-space headache.

                Paul




--
http://www.freelists.org/webpage/oracle-l

Other related posts: