A master table can have only one materialized view log defined on it.Oracle Database can use this materialized view log to perform fast refreshes for all fast-refreshable materialized views based on the master table.You can make a good case that's a good thing, because it lets you optimize the process around your needs..... Hmm I think a materialized view you have to update yourself is called a "table"..but after dealing with the nightmare that is Oracle 11g, I think it'd be much more fun going that route with triggers and everything.If PCT refresh is possible, it will occur automatically and no user intervention is required in order for it to occur.When updating an existing record, is it deleted from a materialized view and then re-inserted?Timestamp-based materialized view logs use timestamps and require some setup operations when preparing to refresh the materialized view.
A materialized view log is located in the master database in the same schema as the master table.
The fact that only some partitions have changed, due to a DML or a partition maintenance operation, is useful for: Partitioning and Query Rewrite When a certain partition of the detail table is updated, only specific sections of the materialized view are marked stale.
The materialized view must have information that can identify the partition of the table corresponding to a particular row or group of the materialized view.
There is much seeded functionality around monitoring tables which the materialized view is dependent on using materialized view log files (explicitly designed for this purpose).
For instance, I have a log file for my Oracle Apps table,inv.mtl_system_items_b.