RE: MView... Fresh build is much faster than Complete refresh...

The plan is to do fast refreshes on demand. There will be some change, but
not huge volumes of it.

RF

Robert G. Freeman
Oracle Consultant/DBA/Author
Principal Engineer/Team Manager
The Church of Jesus Christ of Latter-Day Saints
Father of Five, Husband of One,
Author of various geeky computer titles
from Osborne/McGraw Hill (Oracle Press)
Oracle Database 11g New Features Now Available for Pre-sales on Amazon.com!
BLOG: http://robertgfreeman.blogspot.com/
Sig V1.2

  -----Original Message-----
  From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx]On Behalf Of Dan Norris
  Sent: Wednesday, August 22, 2007 6:38 AM
  To: salem.ghassan@xxxxxxxxx
  Cc: oracle-l
  Subject: Re: MView... Fresh build is much faster than Complete refresh...


  You're doing a complete refresh, so logs on the base tables won't matter.
If you do decide to keep logs and do (or attempt) fast refreshes, consider
whether that's the best approach given the amount of change on the base
tables. If the base tables change a lot between refreshes, it may be faster
to do a complete refresh (assuming you cure the issue you're encountering
below).

  Dan


  ----- Original Message ----
  Robert,
  do you have MV logs on the base tables?, the are cleaned up upon refresh,
so if they are 'big', it may explain the result, also, how many indexes do
you have on this MView?

  rgds


  On 8/22/07, Robert Freeman <robertgfreeman@xxxxxxxxx> wrote:
    So I have this materialized view. When I execute the create materialized
view command, it takes 32.39 seconds to build. A complete refresh (exec
dbms_mview.refresh('mview_name','C'); ) from the prompt this takes almost
3-4 times longer. Does anyone have any thoughts on why this might be so just
right off hand. I've not run a 10046 on it yet,  but I thought maybe there
is something about MVIEW Full Refreshes that I'm just missing.

    RF

Other related posts: