I have a very complex Oracle view based on other materialized views, regular views as well as some tables (I can't "fast refresh" it). Most of the time, existing records in this view are based on a date and are "stable", with new record sets having new dates.
Occasionally, I receive back-dates. I know what those are and how to deal with them if I were maintaining a table, but I would like to keep this a "view". A complete refresh would take around 30 minutes, but it only takes 25 seconds for any given date.
Can I specify that only a portion of a materialized view should be updated (i.e. the affected dates)?
Do I have to scrap the view and use a table and a procedure to populate or refresh a given date in that table?
After more reading and judging by the lack of answers to this question, I come come to the conclusion that it is not possible to refresh a single partition of a materialized view.
If you can give a syntax example that proves otherwise, I will happily mark your answer the accepted one.
To others who might find this questions useful in the future: you might also want to know that in Oracle 10g, refreshing a partition (or any mview) will cause Oracle to issue
DELETE
, followed byINSERT
.If this is giving you performance problems (like me), there is an option to use
atomic_refresh => false
, which willTRUNCATE
, thenINSERT /*+APPEND*/
.Partition by date as in answer 3 (skaffman).
You could just do the refresh of a normal mv(
table_refreshed
below) and than use the exchange keyword i.e.I have been able to refresh a single partition of a materialized view with partition change tracking.
It seems to require that the view is created with
REFRESH FAST WITH ROWID
option andDBMS_MVIEW.REFRESH
is called with'P'
method.You can partition materialized views just as you can with normal tables. Partition your mview by date, and then you can refresh only the required partition.