How To Setup Refresh Ggroup and Collect Information About It
(Doc ID 1346461.1)
Last updated on AUGUST 26, 2021
Applies to:Oracle Database Backup Service - Version N/A and later
Oracle Database Cloud Service - Version N/A and later
Oracle Database - Enterprise Edition - Version 188.8.131.52 to 184.108.40.206 [Release 8.0.6 to 11.2]
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
The goal intended on this note is complement to <Note 1010610.6> (Creating Materialized View Refresh Groups) with examples and queries to monitorize refresh groups in a database.
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 primary-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 primary.
<Note 67424.1> explains that suggestion in more detail.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document