When you issue:
Create materialized view log on "table_name";
ORACLE creates a table mlog$_"table_name" for you that makes fast refresh possible.

• What happens during DML?
• Including new values?
• Filter columns?
• Truncate MV log?

This procedure can be used to help you understand the capabilities of an MV.
Run $ORACLE_HOME\rdbms\admin\utlxmv.sql to create the capability table.

• Fast refresh with user defined function
• Fast refresh with count(*)

• Fast refresh basics
• A "fake" fast refresh
• Fast refresh after SQL*LOADER direct path load
• Fast refresh after direct load insert
• Fast refresh on lob update that works
• Fast refresh on lob update that fails

• 2 table join and ROWID
• With aggregates
• With database link?
• What happens during a ON COMMIT fast refresh?

• Inner working of a Complete Refresh
• Preserving MV during complete refresh

• Query rewrite on union view
• Query rewrite and user defined function
• Explore query rewrite with DBMS_MVIEW.EXPLAIN_REWRITE

• The basics
• Create partitioned MV with PREBUILT TABLE clause

• Create an MV on an existing table
• Trigger on MV