2.228 ALL_MVIEWS
ALL_MVIEWS
describes all materialized views accessible to the current user.
Related Views
-
DBA_MVIEWS
describes all materialized views in the database. -
USER_MVIEWS
describes all materialized views owned by the current user.
Column | Datatype | NULL | Description |
---|---|---|---|
|
|
|
Schema in which the materialized view was created |
|
|
|
Name of the materialized view |
|
|
|
Name of the container in which the materialized view's data is held. Normally this is the same as |
|
|
|
Query that defines the materialized view |
|
|
|
Length (in bytes) of the defining query |
|
|
|
Indicates whether the materialized view is updatable ( |
|
|
|
For updatable materialized views, the filename of the update log |
|
|
|
Rollback segment for the master site or the master materialized view site |
|
|
|
Database link for the master site or the master materialized view site |
|
|
|
Indicates whether rewrite is enabled ( |
|
|
|
Indicates whether the materialized view is eligible for rewrite, and if so, what rules must be followed:
|
|
|
|
Refresh mode of the materialized view:
|
|
|
|
Default method used to refresh the materialized view (can be overridden through the API):
|
|
|
|
Indicates how the materialized view was populated during creation:
|
|
|
|
Indicates whether the materialized view is eligible for incremental (fast) refresh. Oracle Database calculates this value statically, based on the materialized view definition query:
|
|
|
|
Method used for the most recent refresh:
|
|
|
|
Date on which the materialized view was most recently refreshed (blank if not yet populated) |
|
|
|
End time of the most recent refresh on the materialized view (blank if not yet populated) |
|
|
|
Relationship between the contents of the materialized view and the contents of the materialized view's masters:
|
|
|
|
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 |
|
|
|
Indicates whether the materialized view is prebuilt ( |
|
|
|
Indicates whether the materialized view contains PL/SQL functions ( |
|
|
|
Indicates whether the materialized view contains external tables ( |
|
|
|
Indicates whether the materialized view is considered fresh ( |
|
|
|
Indicates whether the materialized view is imported ( |
|
|
|
Indicates whether the materialized view uses trusted constraints for refresh ( |
|
|
|
Validity of the materialized view with respect to the objects upon which it depends:
|
|
|
|
Indicates whether the materialized view was created using the |
|
|
|
Time from when the materialized view became stale |
|
|
|
Number of PCT detail tables |
|
|
|
Number of fresh PCT partition regions |
|
|
|
Number of stale PCT partition regions |
|
|
|
Indicates whether the materialized view was created using the SEGMENT CREATION DEFERRED clause. The value is YES if the segment for the materialized view is created and NO if it is not. |
|
|
|
Name of the edition in which editioned objects referenced in an expression column are resolved |
|
|
|
Name of the oldest edition in which the stored results of the materialized view's subquery may be used for query rewrite. In editions before the specified edition, the stored results of the materialized view's data are considered unusable. This value is NULL if no such edition is specified. |
|
|
|
Name of the oldest edition in which the stored results of the materialized view's subquery may not be used for query rewrite. The data is unusable for query rewrite in the specified edition and in any descendants of this edition. This value is NULL if no such edition is specified. |
|
|
|
Default collation for the materialized view |
|
|
|
Indicates whether the materialized view is a real-time materialized view ( |
See Also:
-
Oracle Database Data Warehousing Guide for more information on materialized views to support data warehousing