● How should the materialized view be refreshed? Choose how the materialized view is synchronized with respect to the base tables it was created from. The query defining the materialized view determines which refresh method can be used; the materialized view can always be rebuilt from scratch but it may not always be possible to perform a fast refresh on it. For more information, see Requirements for the Fast Refresh Method.
• Complete: Build from scratch.
• Fast: Apply only the changes.
• Force: Perform a fast refresh if possible, if not possible perform a complete refresh.
• Never: Do not refresh the view automatically.
● Choose a refresh mechanism: Choose when the materialized view is refreshed.
• ON DEMAND: If selected, you can run a build-in Oracle procedure to refresh the materialized view such as DBMS_MVIEW.REFRESH (refreshes specific materialized view), DBMS_MVIEW.REFRESH_DEPENDENT (refreshes materialized views associated with specific base tables) or DBMS_MVIEW.REFRESH_ALL_MVIEWS (refreshes all materialized views).
• ON COMMIT: If selected, the materialized view is refreshed when a transaction is committed that updates tables referenced in the materialized view.
• Automatically: If selected, Oracle refreshes the materialized view at the specified date and time or the specified frequency.
● Select a refresh method: If this materialized view is based on the Primary Key, it allows the master tables of the view to be reorganized without affecting the eligibility of the view for fast refresh. In this case the master table must contain a primary key constraint. Select Rowid if the materialized view is organized based on the Rowid, which is useful if the view does not include all primary key columns of the master tables.
● Primary key: If selected, the materialized view master tables can be reorganized without affecting its ability to be refreshed using the Fast refresh method. Select this method only if the master table contains an enabled primary key constraint