oceanbase.DBA_MVIEWS|V4.3.5| docs|Distributed Database

oceanbase.DBA_MVIEWS

Last Updated：2026-02-05 05:53:37 Updated

Note

This view is available starting with V4.3.0.

Purpose

The DBA_MVIEWS view displays information about all materialized views.

Columns

Column	Type	Nullable?	Description
OWNER	varchar(128)	NO	The name of the materialized view owner.
MVIEW_NAME	varchar(128)	NO	The name of the materialized view.
CONTAINER_NAME	varchar(128)	NO	The name of the container table of the materialized view.
QUERY	longtext	NO	The query that defines the materialized view.
QUERY_LEN	bigint(20)	NO	The length of the query, in bytes.
UPDATABLE	varchar(1)	NO	Indicates whether the materialized view is updatable. Y N Note This column is compatible only and defaults to N.
UPDATE_LOG	varchar(128)	NO	The name of the update log file for updatable materialized views. Note This column is compatible only and defaults to NULL.
MASTER_ROLLBACK_SEG	varchar(128)	NO	The rollback segment of the master site or the master materialized view site. Note This column is compatible only and defaults to NULL.
MASTER_LINK	varchar(128)	NO	The database link of the master site or the master materialized view site. Note This column is compatible only and defaults to NULL.
REWRITE_ENABLED	varchar(1)	NO	Indicates whether query rewrite is enabled. Y N
REWRITE_CAPABILITY	varchar(9)	NO	Indicates whether the materialized view is eligible for query rewrite. If it is eligible, it must follow the following rules: NONE: The materialized view cannot be used for query rewrite because query rewrite is not allowed or prevented. TEXTMATCH: The query of the materialized view has restrictions on query rewrite. GENERAL: The query of the materialized view does not have restrictions on query rewrite. Note This column is compatible only and defaults to NULL.
REFRESH_MODE	varchar(6)	NO	The refresh mode of the materialized view. DEMAND: The materialized view is refreshed when the refresh process is called. NEVER: The materialized view is never refreshed.
REFRESH_METHOD	varchar(8)	NO	The default method for refreshing the materialized view (which can be overridden by an API). COMPLETE: A full refresh is performed. FORCE: An incremental refresh is attempted first. If an incremental refresh is not possible, a full refresh is performed. FAST: An incremental refresh is performed. NEVER: The materialized view is never refreshed.
BUILD_MODE	varchar(9)	NO	The method for populating the materialized view during creation. IMMEDIATE: The materialized view is populated immediately during creation. DEFERRED: The materialized view is not populated during creation. PREBUILT: The materialized view is populated with an existing table during creation.
FAST_REFRESHABLE	varchar(18)	NO	Indicates whether the materialized view is suitable for incremental (fast) refreshes. NO: The materialized view cannot be fast-refreshed and is therefore complex. DML: Only DML operations support fast refreshes. Note This column is compatible only and defaults to NULL.
LAST_REFRESH_TYPE	varchar(8)	NO	The method used for the last refresh. COMPLETE: A full refresh was performed. FAST: An incremental refresh was performed. NA: The materialized view has not been refreshed yet (for example, during deferred creation).
LAST_REFRESH_DATE	datetime	YES	The date when the materialized view was last refreshed.
LAST_REFRESH_END_TIME	datetime	NO	The end time of the last refresh of the materialized view.
STALENESS	varchar(19)	NO	The relationship between the content of the materialized view and the content of the materialized view master. FRESH: The materialized view is a read-consistent view of its master object at the current time. IMPORT: The materialized view was imported from another database (the value of the UNKNOWN_IMPORT column is Y). Therefore, it is unknown whether the materialized view is a read-consistent view of its master view at any point in time. After a full refresh, the STALENESS value of this view changes to FRESH. NEEDS_COMPILE: Some objects that the materialized view depends on have been modified. You must execute the ALTER MATERIALIZED VIEW...COMPILE statement to verify the materialized view and calculate its staleness. STALE: The materialized view is outdated because one or more of its master objects have been modified. If the materialized view was FRESH before it became STALE, it is a read-consistent view of the previous state of its master objects. UNDEFINED: The materialized view has a remote master. The concept of staleness is not defined for such materialized views. UNKNOWN: Whether the materialized view is a read-consistent view of its master view at any point in time. UNUSABLE: The materialized view is not a read-consistent view of its master view at any point in time. Note This column is compatible only and defaults to NULL.
AFTER_FAST_REFRESH	varchar(19)	NO	The STALENESS value that appears after a fast refresh is applied to this materialized view. It can take the same values as the STALENESS column. If the value is NA, it indicates that this value is used when a fast refresh is not applicable to the materialized view. Note This column is compatible only and defaults to NULL.
UNKNOWN_PREBUILT	varchar(1)	NO	Indicates whether the materialized view is prebuilt. Y N Note This column is compatible only and defaults to N.
UNKNOWN_PLSQL_FUNC	varchar(1)	NO	Indicates whether the materialized view contains a PL/SQL function. Y N Note This column is compatible only and defaults to N.
UNKNOWN_EXTERNAL_TABLE	varchar(1)	NO	Indicates whether the materialized view contains an external table. Y N Note This column is compatible only and defaults to N.
UNKNOWN_CONSIDER_FRESH	varchar(1)	NO	Indicates whether the materialized view is considered fresh. Y N Note This column is compatible only and defaults to N.
UNKNOWN_IMPORT	varchar(1)	NO	Indicates whether the materialized view is imported. Y N Note This column is compatible only and defaults to N.
UNKNOWN_TRUSTED_FD	varchar(1)	NO	Indicates whether the materialized view is refreshed using trusted constraints. Y N Note This column is compatible only and defaults to N.
COMPILE_STATE	varchar(19)	NO	Indicates the validity of the materialized view relative to the objects it depends on. VALID: The materialized view has been validated, has no errors, and the objects it depends on have not changed since the last validation. NEEDS_COMPILE: Some objects that the materialized view depends on have changed. Use the ALTER MATERIALIZED VIEW...COMPILE statement to validate this materialized view. ERROR: The materialized view has been validated but has one or more errors. Note This column is compatible only and defaults to NULL.
USE_NO_INDEX	varchar(1)	NO	Indicates whether the materialized view was created using the USING NO INDEX clause (Y) or using the default index (N). The USING NO INDEX clause prevents the creation of the default index. Y N Note This column is compatible only and defaults to Y.
STALE_SINCE	datetime	NO	The start time when the materialized view became stale. Note This column is compatible only and defaults to NULL.
NUM_PCT_TABLES	bigint(0)	NO	The number of PCT base tables. Note This column is compatible only and defaults to NULL.
NUM_FRESH_PCT_REGIONS	bigint(0)	NO	The number of fresh PCT partition regions. Note This column is compatible only and defaults to NULL.
NUM_STALE_PCT_REGIONS	bigint(0)	NO	The number of stale PCT partition regions. Note This column is compatible only and defaults to NULL.
SEGMENT_CREATED	varchar(3)	NO	Indicates whether the materialized view was created using the SEGMENT CREATION DEFERRED clause. YES NO Note This column is compatible only and defaults to NO.
EVALUATION_EDITION	varchar(128)	NO	The version name of the version object referenced in the expression column. Note This column is compatible only and defaults to NULL.
UNUSABLE_BEFORE	varchar(128)	NO	The name of the oldest version where the stored results of the materialized view subquery can be used for query rewriting. The stored results of the materialized view data are considered unavailable in versions earlier than the specified version. If no such version is specified, this value is NULL. Note This column is compatible only and defaults to NULL.
UNUSABLE_BEGINNING	varchar(128)	NO	The name of the oldest version where the stored results of the materialized view subquery cannot be used for query rewriting. In the specified version and any of its descendants, the data cannot be used for query rewriting. If no such version is specified, this value is NULL. Note This column is compatible only and defaults to NULL.
DEFAULT_COLLATION	varchar(100)	NO	The default collation of the materialized view. Note This column is compatible only and defaults to NULL.
ON_QUERY_COMPUTATION	varchar(1)	NO	Indicates whether the materialized view is a real-time materialized view. Y N
REFRESH_DOP	bigint(20)	NO	The parallelism of the background refresh of the materialized view. The default value is 0. Note When you create a materialized view, you can specify this value by using the `PARALLEL` attribute. You can also modify this value by using the `ALTER MATERIALIZED VIEW` statement. If you do not explicitly set `PARALLEL` (the default value of `REFRESH_DOP` is 0), the background refresh parallelism depends on the value of the global system variable `mview_refresh_dop`. This column is available starting with V4.3.5 BP1 of OceanBase Database V4.3.5.
DATA_SYNC_SCN	bigint(20) unsigned	NO	The data point of the materialized view. Note This column is available starting with V4.3.5 BP2 of OceanBase Database V4.3.5.
DATA_SYNC_DELAY	varchar(128)	NO	The data synchronization delay of the materialized view, in seconds. Note This column is available starting with V4.3.5 BP2 of OceanBase Database V4.3.5.

Sample query

obclient [(none)]> SELECT * FROM oceanbase.DBA_MVIEWS LIMIT 1\G

The query result is as follows:

*************************** 1. row ***************************
                 OWNER: test
            MVIEW_NAME: mv1_tbl3_tbl4
        CONTAINER_NAME: mv1_tbl3_tbl4
                 QUERY: select `test`.`tbl3`.`id` AS `id1`,`test`.`tbl4`.`id` AS `id2`,`test`.`tbl3`.`name` AS `name`,`test`.`tbl4`.`age` AS `age` from `test`.`tbl3`,`test`.`tbl4` where (`test`.`tbl3`.`id` = `test`.`tbl4`.`id`)
             QUERY_LEN: 203
             UPDATABLE: N
            UPDATE_LOG: NULL
   MASTER_ROLLBACK_SEG: NULL
           MASTER_LINK: NULL
       REWRITE_ENABLED: N
    REWRITE_CAPABILITY: NULL
          REFRESH_MODE: DEMAND
        REFRESH_METHOD: COMPLETE
            BUILD_MODE: IMMEDIATE
      FAST_REFRESHABLE: NULL
     LAST_REFRESH_TYPE: COMPLETE
     LAST_REFRESH_DATE: 2025-04-22 17:39:46
 LAST_REFRESH_END_TIME: 2025-04-22 17:39:46
             STALENESS: NULL
    AFTER_FAST_REFRESH: NULL
      UNKNOWN_PREBUILT: N
    UNKNOWN_PLSQL_FUNC: N
UNKNOWN_EXTERNAL_TABLE: N
UNKNOWN_CONSIDER_FRESH: N
        UNKNOWN_IMPORT: N
    UNKNOWN_TRUSTED_FD: N
         COMPILE_STATE: NULL
          USE_NO_INDEX: Y
           STALE_SINCE: NULL
        NUM_PCT_TABLES: NULL
 NUM_FRESH_PCT_REGIONS: NULL
 NUM_STALE_PCT_REGIONS: NULL
       SEGMENT_CREATED: NO
    EVALUATION_EDITION: NULL
       UNUSABLE_BEFORE: NULL
    UNUSABLE_BEGINNING: NULL
     DEFAULT_COLLATION: NULL
  ON_QUERY_COMPUTATION: N
           REFRESH_DOP: 0
         DATA_SYNC_SCN: 1745314785636035000
       DATA_SYNC_DELAY: 61626
1 row in set