Default complete refresh mechanism for 9i is truncate/insert /*+
append*/
Default complete refresh mechanism for 10g is delete, conventional
insert although there is possinility to switch back to old mechanism
using dbms_mview.refresh with atomic_refresh = false.
So if you are using 9i then there might be some moments just after
truncate and before insert when the MV is empty. To avoid that one
possibility is to use 2 MV approach I was explained in my article
Effective search in a normalized application at
http://www.gplivna.eu/papers/mat_views_search.htm
Of course that means you are querying (possibly) stale data, but
usually full refresh means that :)
Gints Plivna
http://www.gplivna.eu
Received on Wed Aug 15 2007 - 15:30:00 CDT
