Welcome to Datavail’s Blog, where you can read the latest insights, tips and opinions of our experts on all things data and technology.
Last week when we talked about how to implement a fast refresh materialized view with a MAX aggregate function. This week we will tackle another restriction on fast refresh materialized views. We will work through an example on how to modify a materialized view that includes a COUNT(DISTINCT) in order to get it to fast refresh.
With a very simple materialized view that contains an aggregate function like MAX, Oracle can perform a fast refresh of the materialized view. However, once we start adding some complexity to the materialized view query, Oracle starts to either error out on the fast refresh, or will disallow the creation of the fast refresh materialized view in the first place.