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_at_yahoo.com> 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
--
http://www.freelists.org/webpage/oracle-l
Received on Wed Aug 22 2007 - 07:38:01 CDT
