Last updated on AUGUST 08, 2011
Applies to:Oracle Server - Enterprise Edition - Version: 220.127.116.11 to 18.104.22.168 - Release: 8.0.6 to 11.2
Information in this document applies to any platform.
The goal intended on this note is complement to <
Testing has been done on a 11.2 database, but most of the queries are quite similar in older and newer releases.
Because materialized view refresh is set-based, if you require that two or more materialized views be refreshed to a single point in time, a materialized view refresh group will need to be created.
Oracle guarantees that data integrity will be kept once the group refresh is completed, but we can't guarantee the order on what the mviews will be refreshed.
For example, to preserve a master-detail relationship between a pair of materialized views, place the related materialized views in the same refresh group.
Creating constraints to preserve the integrity is not recommended, as that may cause errors to be raised if detail mview is refreshed before master.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms