bencio schreef:
> Hallo all !!
>
> i created two materialized views joing 2 tables with fast refreshing
> scheduling every hour.
>
> It works very well with 4 milions of data in each table whit 30000 new
> rows every month (like 50 new rows every hour).
> So the refreshing time was like 2 or 3 minutes.
>
> Last week i made an update in all records and now i'm waiting for the
> end of the refreshing of the materialized views.
> I populated a field with a string (100 characters long) in each row.
> Now every refresh session is 14 hours long.
>
> I notice that the two materialized view logs now contains 7 milions of
> rows.
>
> So i would like to ask you:
>
> 1) where can i see if the session that is running now is the real last
> refresh session that purges the logs due to refresh only the new data?
> 2) i discover a system view that contains all the attributes of the
> materilized views (next refreshing date, master tables, query) and i
> notice that there is a field called 'STATUS' with a number. Every
> materialized views have the STATUS '2'. Only one has the STATUS '6'.
> What does it means ?
> 3) it could be better to refresh complete the materialized views and
> recreate new logs?
>
> Thanks a lot!
> Excuse me for my bad english.
>
> Gianni Benciolini
> Web Master
> Bologna, Italy
>
In your current position, I'd just drop, and recreate the logs
(before your create the MV's, of course...) as well as recreate
the MV's
--
Regards,
Frank van Bortel
Top-posting is one way to shut me up...
Received on Wed Nov 29 2006 - 00:42:58 CST
