OWNER |
VARCHAR2(30) |
NOT NULL |
Schema in which the materialized view was created |
MVIEW_NAME |
VARCHAR2(30) |
NOT NULL |
Name of the materialized view |
CONTAINER_NAME |
VARCHAR2(30) |
NOT NULL |
Name of the container in which the materialized view's data is held. Normally this is the same as MVIEW_NAME . For materialized views created in releases before 8.1 (or under pre-8.1 compatibility mode), Oracle attaches the 6-byte prefix SNAP$_ . If MVIEW_NAME has more than 19 bytes, Oracle truncates the name to 19 bytes and may add a 4-byte sequence number as a suffix to produce a nonambiguous CONTAINER_NAME . |
QUERY |
LONG |
|
The query that defines the materialized view |
QUERY_LEN |
NUMBER(38) |
|
Length in bytes of the defining query |
UPDATABLE |
VARCHAR2(1) |
|
Whether the materialized view is updatable (Y | N ) |
UPDATE_LOG |
VARCHAR2(30) |
|
For updatable materialized views, the filename of the update log |
MASTER_ROLLBACK_SEG |
VARCHAR2(30) |
|
Rollback segment for the master site or master materialized view site |
MASTER_LINK |
VARCHAR2(128) |
|
Database link for the master site or master materialized view site |
REWRITE_ENABLED |
VARCHAR2(1) |
|
Whether rewrite is enabled (Y | N ) |
REWRITE_CAPABILITY |
VARCHAR2(9) |
|
Whether the materialized view is eligible for rewrite, and if so, what rules must be followed:
NONE : The materialized view cannot be used for rewrite, because rewrite is disallowed or prevented.
TEXTMATCH : The defining query of the materialized view contained restrictions on the use of query rewrite.
GENERAL : The defining query of the materialized view contained no restrictions on the use of query rewrite, so Oracle can apply any rewrite rule that is supported.
|
REFRESH_MODE |
VARCHAR2(6) |
|
Refresh mode of the materialized view:
DEMAND : Oracle refreshes this materialized view whenever an appropriate refresh procedure is called.
COMMIT : Oracle refreshes this materialized view when a transaction on one of the materialized view's masters commits.
NEVER : Oracle never refreshes this materialized view.
|
REFRESH_METHOD |
VARCHAR2(8) |
|
Default method used to refresh the materialized view. (Can be overridden through the API.)
COMPLETE (C ): The materialized view is completely refreshed from the masters.
FORCE (? ): Oracle performs a fast refresh if possible, otherwise a complete refresh.
FAST (F ): Oracle performs an incremental refresh applying changes that correspond to changes in the masters since the last refresh.
NEVER (N ): The user specified that Oracle should not refresh this materialized view.
|
BUILD_MODE |
VARCHAR2(9) |
|
How the materialized view was populated during creation:
IMMEDIATE : Populated from the masters during creation.
DEFERRED : Not populated during creation. Must be explicitly populated later by the user.
PREBUILT : Populated with an existing table during creation. The relationship of the contents of this prebuilt table to the materialized view's masters is unknown to Oracle.
|
FAST_REFRESHABLE |
VARCHAR2(18) |
|
Whether or not the materialized view is eligible for incremental (fast) refresh. Oracle calculates this value statically, based on the materialized view definition query.
NO : The materialized view is not fast refreshable, and hence is complex.
DIRLOAD : Fast refresh is supported only for direct loads.
DML : Fast refresh is supported only for DML operations.
DIRLOAD_DML : Fast refresh is supported for both direct loads and DML operations.
DIRLOAD_LIMITEDDML : Fast refresh is supported for direct loads and a subset of DML operations.
|
LAST_REFRESH_TYPE |
VARCHAR2(8) |
|
The method used for the most recent refresh:
COMPLETE : The most recent refresh was complete.
FAST : The most recent refresh was fast (incremental).
NA : the materialized view has not yet been refreshed (for example, if it was created DEFERRED ).
|
LAST_REFRESH_DATE |
DATE |
|
Date on which the materialized view was most recently refreshed. Blank if not yet populated. |
STALENESS |
VARCHAR2(9) |
|
The relationship between the contents of the materialized view and the contents of the materialized view's masters.
FRESH : The materialized view is a read-consistent view of the current state of its masters.
STALE : The materialized view is out of date because one or more of its masters has changed. If the materialized view was FRESH before it became STALE , it is a read-consistent view of a former state of its masters.
UNUSABLE : The materialized view is not a read-consistent view of its masters from any point in time.
UNKNOWN : Oracle does not know whether the materialized view is in a read-consistent view of its masters from any point in time. (This is the case for materialized views created on prebuilt tables.)
UNDEFINED : The materialized view has remote masters. The concept of staleness is not defined for such materialized views.
|
AFTER_FAST_REFRESH |
VARCHAR2(9) |
|
Specifies the staleness value that will occur if a fast refresh is applied to this materialized view. Its values are the same as for the STALENESS column, plus the value NA , which is used when fast refresh is not applicable to this materialized view. |
COMPILE_STATE |
VARCHAR2(13) |
|
Validity of the materialized view with respect to the objects upon which it depends:
VALID : The materialized view has been validated without error, and no object upon which it depends has changed since the last validation.
NEEDS_COMPILE : Some object upon which the materialized view depends has changed (other than normal DML changes). An ALTER MATERIALIZED VIEW...COMPILE statement is required to validate this materialized view.
ERROR : The materialized view has been validated with one or more errors.
|
USE_NO_INDEX |
VARCHAR2(1) |
|
Y if the materialized view was created using the USING NO INDEX clause, which suppresses the creation of the default index.
N if the materialized view was created with the default index. |