Is it because:
Dependencies related to MVs are automatically maintained to ensure correct operation. When an MV is created, the materialized view depends on the master tables referenced in its definition. Any DML operation, such as an INSERT, or DELETE, UPDATE, or DDL operation on any dependency in the materialized view will cause it to become invalid.
http://www.orafaq.com/forum/t/127268/
The above will not affect REFRESH ON COMMIT mviews as they get refreshed when the changes to the underlying table sre, ahem, committed.
HTH
Cheers,
Norm. [TeamT]
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
Dependencies related to MVs are automatically maintained to ensure correct operation. When an MV is created, the materialized view depends on the master tables referenced in its definition. Any DML operation, such as an INSERT, or DELETE, UPDATE, or DDL operation on any dependency in the materialized view will cause it to become invalid.
http://www.orafaq.com/forum/t/127268/
The above will not affect REFRESH ON COMMIT mviews as they get refreshed when the changes to the underlying table sre, ahem, committed.
HTH
Cheers,
Norm. [TeamT]
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.