In this post I will illustrate the algorithm used by Oracle (in 220.127.116.11) to fast refresh a materialized view (MV) containing only the SUM aggregate function:
create materialized view test_mv build immediate refresh fast on demand with rowid as select gby as mv_gby, count(*) as mv_cnt_star, sum (dat) as mv_sum_dat, count(dat) as mv_cnt_dat from test_master where whe = 0 group by gby ;
Note that count(dat) is specified - you could avoid that if column dat is constrained to be not-null (as stated in the documentation), but I'm not covering that corner case here.
The MV log is configured to "log everything":
create materialized view log on test_master with rowid ( whe, gby, dat ), sequence including new values;
In the general introduction to aggregate-only MVs we have seen how the refresh engine first marks the log rows, then inspects TMPDLT (loading its rows into the result cache at the same time) to classify its content as insert-only (if it contains only new values), delete-only (if it contains only old values) or general (if it contains a mix of new/old values). Here we illustrate the refreshing SQL in all three scenarios, extracted from the supporting test case.
refresh for insert-only TMPDLT
The refresh is made using this single merge statement:
/* MV_REFRESH (MRG) */ merge into test_mv using ( with tmpdlt$_test_master as ( -- check introduction post for statement ) select gby, sum( 1 ) as cnt_star, sum( 1 * decode(dat, null, 0, 1) ) as cnt_dat, nvl( sum( 1 * dat), 0 ) as sum_dat from (select gby, whe, dat from tmpdlt$_test_master ) as of snapshot(:b_scn) where whe = 0 group by gby ) deltas on ( sys_op_map_nonnull(test_mv.mv_gby) = sys_op_map_nonnull(deltas.gby) ) when matched then update set test_mv.mv_cnt_star = test_mv.mv_cnt_star + deltas.cnt_star, test_mv.mv_cnt_dat = test_mv.mv_cnt_dat + deltas.cnt_dat, test_mv.mv_sum_dat = decode( test_mv.mv_cnt_dat + deltas.cnt_dat, 0, null, nvl(test_mv.mv_sum_dat,0) + deltas.sum_dat ) when not matched then insert ( test_mv.mv_gby, test_mv.mv_cnt_dat, test_mv.mv_sum_dat, test_mv.mv_cnt_star ) values ( deltas.gby, deltas.cnt_dat, decode (deltas.cnt_dat, 0, null, deltas.sum_dat), deltas.cnt_star)
It simply calculates the delta values to be propagated by grouping-and-summing the new values contained in TMPDLT that satisfy the where-clause (essentially, it executes the MV statement on the mv log without redundant values), and then looks for matches over the grouped-by expression (using the null-aware function sys_op_map_nonnull, more on this later). It then applies the deltas to the MV, or simply inserts them if no match is found.
Note that mv_sum_dat (that materializes sum(dat)) is set to null if, and only if, (the updated value of) mv_cnt_dat (that materializes count(dat)) is zero (signaling that for this value of mv_gby, all values of dat in the master table are null). This is done in all three scenarios of the algorithm.
The matching function sys_op_map_nonnull() is there to match null values with null values, since aggregating by null is perfectly legal, yet you cannot match null with null in a merge/join. This function returns a raw value that is never null, and set to 0xFF when the input is null and to the binary representation of the input postfixed with 0x00 for other input values. Note that a function-based index, named I_SNAP$_TEST_MV in our case, is automatically created on sys_op_map_nonnull(mv_gby) to give the CBO the opportunity to optimize the match (unless the MV is created specifying USING NO INDEX, which is probably almost never a good idea when you need to fast refresh).
Note also that the master table, test_master, is not accessed at all, as it is always the case for SUM (but not necessarily for MAX, as we will see in the next post). This elegant decoupling (possible thanks to the mathematical properties of the addition, of course) of the master table from the MV greatly improves performance and also simplifies performance tuning.
refresh for delete-only TMPDLT
The refresh is made in two steps, the first being this update statement:
/* MV_REFRESH (UPD) */ update /*+ bypass_ujvc */ ( select test_mv.mv_cnt_dat, deltas .cnt_dat, test_mv.mv_sum_dat, deltas .sum_dat, test_mv.mv_cnt_star, deltas .cnt_star from test_mv, ( with tmpdlt$_test_master as ( -- check introduction post for statement ) select gby, sum( -1 ) as cnt_star sum( -1 * decode(dat, null, 0, 1) ) as cnt_dat, nvl( sum(-1 * dat), 0) as sum_dat from (select gby, whe, dat from tmpdlt$_test_master mas$ ) as of snapshot(:b_scn) where whe = 0 group by gby ) deltas where sys_op_map_nonnull(test_mv.mv_gby) = sys_op_map_nonnull(deltas.gby) ) set mv_cnt_star = mv_cnt_star + cnt_star, mv_cnt_dat = mv_cnt_dat + cnt_dat, mv_sum_dat = decode(mv_cnt_dat + cnt_dat, 0, null, nvl(mv_sum_dat,0) + sum_dat)
this calculates the same deltas as the insert-only case, just with signs reversed since, of course, we are propagating deletes instead of inserts; it then applies them using an updatable join in-line view instead of a merge.
Then, this delete statement is issued:
/* MV_REFRESH (DEL) */ delete from test_mv where mv_cnt_star = 0;
this is because, when mv_cnt_star (that materializes count(*)) is zero after the deltas application, it means that all the rows belonging to that value of mv_gby have been deleted in the master table, and hence that value must be removed from the MV as well.
Note that an index on mv_cnt_star is NOT automatically created (as of 18.104.22.168) - it might be a very good idea to create it, to avoid a full scan of the MV at every refresh, which is O(mv size) and not O(modifications) as the other steps (thus rendering the whole refresh process O(mv size)).
refresh for mixed-DML TMPDLT
The refresh is accomplished using a single merge statement, which is an augmented version of the insert-only statement plus a delete clause that implements the last part of the delete-only refresh:
/* MV_REFRESH (MRG) */ merge into test_mv using ( select gby, sum( decode(dml$$, 'I', 1, -1) ) as cnt_star, sum( decode(dml$$, 'I', 1, -1) * decode(dat, null, 0, 1)) as cnt_dat, nvl( sum(decode(dml$$, 'I', 1, -1) * dat), 0) as sum_dat from (select chartorowid(m_row$$) rid$, gby, whe, dat, decode(old_new$$, 'N', 'I', 'D') as dml$$, dmltype$$ from mlog$_test_master where snaptime$$ > :b_st0 ) as of snapshot(:b_scn) where whe = 0 group by gby ) deltas on ( sys_op_map_nonnull(test_mv.mv_gby) = sys_op_map_nonnull(deltas.gby) ) when matched then update set test_mv.mv_cnt_star = test_mv.mv_cnt_star + deltas.cnt_star, test_mv.mv_cnt_dat = test_mv.mv_cnt_dat + deltas.cnt_dat, test_mv.mv_sum_dat = decode( test_mv.mv_cnt_dat + deltas.cnt_dat, 0, null, nvl(test_mv.mv_sum_dat,0) + deltas.sum_dat ), delete where ( test_mv.mv_cnt_star = 0 ) when not matched then insert ( test_mv.mv_gby, test_mv.mv_cnt_dat, test_mv.mv_sum_dat, test_mv.mv_cnt_star ) values ( deltas.gby, deltas.cnt_dat, decode (deltas.cnt_dat, 0, null, deltas.sum_dat), deltas.cnt_star) where (deltas.cnt_star > 0)
Here the deltas are calculated by reversing the sign of "old" values (dml$$ not equal to 'I', which is the same as old_new$$ not equal to 'N'; note in passing that it does not distinguish between old_new$$ equal to 'O' or 'U', as stated in the introduction post), of course adjusting cnt_star and cnt_dat accordingly.
The removal of rows that get their mv_cnt_star set to zero is performed as a side case of the update, which is very nice since it does not call for an index on that column.
Surprisingly, this statement does not use TMPDLT, but reads straight from the log; I don't know the reason behind this, and whether this is always the case or if TMPDLT is sometimes used, depending, perhaps, on some heuristic decision. Surely, while using TMPDLT is mandatory in the other two cases (since the statements work only if their input is insert/delete only, and that is checked over TMPDLT only), it is just a possible optimization choice here.
Knowing the "internal" workings presented here makes it vastly easier (I hope) to optimize the refresh process and avoid pitfalls; it is of course unfeasible to cover all possible real-life scenarios, but I can offer some general high-level considerations.
Obviously, fast refreshing is better than complete refreshing only when the number of modifications stored in the MV log is "small" compared to the MV size. In this scenario the usual optimal values propagation plan reads from the log, computes TMPDLT (when used), and joins the MV using NESTED LOOPS using the (automatically created) index on sys_op_map_nonnull(mv_gby) - or possibly using HASH JOIN, or SORT MERGE JOIN, again using the same index.
Hence the only optimization worth making is to create the index on mv_cnt_star, unless you can be absolutely sure that you will never be in the delete-only scenario, or unless you don't care about the resulting full MV scan.
Since the master table is never read during the refresh, it can be left alone. This is great.
The best access method for the log is usually a full table scan, since all rows are normally read, and hence usually nothing has to be done on the log. I can imagine that in rare cases one might consider optimizing the log by e.g. creating an index - for example a covering index on all the referenced columns; or one to speed up the analytic functions computations of TMPDLT avoiding the sort; or one prefixed by snaptime$$ if other MVs read from the log and refreshes at different times, etc.
Maybe, sometimes, it might prove beneficial to disable TMPDLT, as discussed in the introduction post.