Refresh Options
Create OptionsWhen
MethodDemand
The materialized view will be refreshed on demand by calling one of the three DBMS_MVIEW refresh procedures.Commit
A fast refresh is to occur whenever the database commits a transaction that operates on a master table of the materialized view.Automatic
The database automatically refresh the materialized view with the automatic refresh time.Never
The materialized view will not be refreshed with any Oracle Database refresh mechanism or packaged procedure.Start OnFORCE
When a refresh occurs, Oracle Database will perform a fast refresh if one is possible or a complete refresh if fast refresh is not possible.FAST
A incremental refresh method, which performs the refresh according to the changes that have occurred to the master tables.COMPLETE
A complete refresh method, which is implemented by executing the defining query of the materialized view.
A datetime expression for the first automatic refresh time. Next
A datetime expression for calculating the interval between automatic refreshes.TypeNote: To edit the datetime, just simply click ... and choose / enter the desired data.
Rollback SegmentPrimary Key
A primary key materialized view. This is the default.Row ID
A rowid materialized view.Constraints
Master
The remote rollback segment is used at the remote master site for the individual materialized view.
Local
The remote rollback segment is used for the local refresh group that contains the materialized view. This is the default.Enforced
Oracle Database use enforced constraints during the refresh operation.Trusted
Oracle Database use dimension and constraint information that has been declared trustworthy by the database administrator but that has not been validated by the database.
No Index
Check this to suppress the creation of the default index.
Build Type
Immediate
The materialized view is to be populated immediately. This is the default.Deferred
The materialized view is to be populated by the next refresh operation.Prebuilt
To register an existing table as a preinitialized materialized view.
Materialized View Options
Reduced Precision
With
To authorize the loss of precision that will result if the precision of the table or materialized view columns do not exactly match the precision returned by subquery.Without
To require that the precision of the table or materialized view columns match exactly the precision returned by subquery, or the create operation will fail. This is the default.Compress
Data segments are compressed to reduce disk and memory use.Parallel
Choose NOPARALLEL for serial execution or PARALLEL if you want Oracle to select a degree of parallelism equal to the number of CPUs available on all participating instances times the value of the PARALLEL_THREADS_PER_CPU initialization parameter.With Degree
Set the default degree of parallelism for queries and DML on the materialized view after creation.Logging
Choose LOGGING for logging the creation of Materialized view in the redo log file. Choose NOLOGGING for no logging.Tablespace
Choose the tablespace in which the materialized view is to be created.Physical Attributes
Set the physical attributes of the materialized view.
Enable Cache
The blocks retrieved for the table are placed at the most recently used end of the least recently used (LRU) list in the buffer cache when a full table scan is performed.
For Update
Check this to allow a subquery, primary key, object, or rowid materialized view to be updated. When used in conjunction with Advanced Replication, these updates will be propagated to the master.
Enable Query Rewrite
The materialized view is used for query rewrite.
Using Index Clause
Tablespace
Choose the tablespace of the index.Physical Attributes
Set the physical attributes for the default index Oracle Database uses to maintain the materialized view data.