Purpose
This statement is used to create a materialized view log.
A materialized view log (mlog) is used to record incremental updates of the base table to support the fast refresh feature of materialized views. An mlog is a record table that tracks changes in the base table and applies these changes to the corresponding materialized view to enable fast refresh.
Note
In OceanBase Database, the mlog does not support specifying a partition. The partition of the mlog is bound to the partition of the base table.
Privilege requirements
To create a materialized view log, you must have the CREATE TABLE and SELECT privileges on the base table. For more information about privileges in OceanBase Database, see Privilege types in Oracle mode.
Syntax
CREATE [OR REPLACE] MATERIALIZED VIEW LOG ON [schema.] table
[parallel_clause]
[with_clause]
[mv_log_purge_clause];
parallel_clause:
NOPARALLEL
| PARALLEL integer
with_clause:
WITH [ {PRIMARY KEY | ROWID | SEQUENCE}
[ { , PRIMARY KEY | , ROWID | , SEQUENCE }]... ]
(column_name [, column_name]...)
[new_values_clause]
new_values_clause:
{INCLUDING | EXCLUDING} NEW VALUES
mv_log_purge_clause:
PURGE {IMMEDIATE [ SYNCHRONOUS ]
| START WITH datetime_expr [NEXT datetime_expr]
| [START WITH datetime_expr] NEXT datetime_expr
}
Parameters
| Parameter | Description |
|---|---|
| OR REPLACE | Optional. Specifies OR REPLACE to indicate that if the corresponding mlog already exists, a new mlog will be created based on the definition and replace the existing mlog. The process of recreating the mlog will not affect the normal read and write operations of the materialized view and base table. |
| schema. | Optional. Specifies the schema where the base table of the materialized view log is located. If you omit schema., the base table will be assumed to be in your own schema. |
| table | Specifies the name of the base table corresponding to the materialized view log. |
| parallel_clause | Optional. Specifies the degree of parallelism (dop) for creating the materialized view log. For more information, see parallel_clause below. |
| with_clause | Optional. Specifies the auxiliary columns included in the materialized view log. It indicates whether to record the primary key (PRIMARY KEY) and row identifier (ROWID) of the base table when it changes, and can also be used to add a sequence (SEQUENCE) to provide additional sorting information for the materialized view log. For more information, see with_clause below. |
| column_name | Optional. Specifies the name of the column whose value will be recorded in the materialized view log for all modified rows. |
| new_values_clause | Optional. Specifies whether to record both the old and new values in the materialized view log for update operations. For more information, see new_values_clause below. |
| mv_log_purge_clause | Optional. Specifies the time when data in the materialized view log will be purged. For more information, see mv_log_purge_clause below. |
parallel_clause
NOPARALLEL: The default configuration with a parallel degree of1.PARALLEL integer: Specifies the parallel degree, whereintegermust be greater than or equal to1.
with_clause
PRIMARY KEY: Indicates that the materialized view log records the primary key columns of the base table. This option only takes effect for tables with a primary key. If not specified, the system will automatically add this attribute to the materialized view log, meaning the materialized view log will default to including the primary key columns.ROWID: Indicates that the materialized view log records the row identifier (ROWID) of the base table. If not specified, the system will automatically add this attribute to the materialized view log, meaning the materialized view log will default to including theM_ROW$$column.SEQUENCE: Indicates that the materialized view log records the sequence number (seq_no) of multiple-row updates within a transaction. The system will automatically add this attribute to the materialized view log, meaning the materialized view log will default to including theSEQUENCE$$column.
new_values_clause
INCLUDING: The default setting, indicating that both old and new values can be recorded in the materialized view log. If you want the materialized view to support fast refresh, you must specifyINCLUDING NEW VALUES.EXCLUDING: Indicates that new values will not be recorded in the materialized view log. Do not useEXCLUDING NEW VALUES, or an error will occur.
mv_log_purge_clause
Notice
The data in the materialized view log will only be purged after the materialized view has been successfully refreshed.
IMMEDIATE: Indicates that the materialized view log will be purged immediately after each refresh. The default value isSYNCHRONOUS.SYNCHRONOUS: Optional. Indicates that the purge will be executed synchronously.
START WITH datetime_expr [NEXT datetime_expr]:START WITH datetime_expr: Specifies the initial purge time for the materialized view log.[NEXT datetime_expr]: Optional. Specifies the next purge time for the materialized view log. Used to set the next purge time.
[START WITH datetime_expr] NEXT datetime_expr: If you specify only theNEXT datetime_exprparameter without theSTART WITH datetime_exprparameter, the initial purge time for the materialized view log will be set to the value of theNEXT datetime_exprparameter.
Notice
Make sure that the START WITH datetime_expr and NEXT datetime_expr expressions are set to future dates and times, otherwise an error will occur.
It is recommended to use current_date to represent the current time in the current time zone. Here are some examples of time expressions:
Purge expired materialized view log records every 10 seconds starting from the current time (
current_date).START WITH current_date NEXT current_date + INTERVAL '10' SECONDPurge expired materialized view log records every 10 hours starting from the current time (
current_date).START WITH current_date NEXT current_date + INTERVAL '10' HOURPurge expired materialized view log records every 1 day starting from the current time (
current_date).START WITH current_date NEXT current_date + 1
Examples
Create a table named
test_tbl1.obclient> CREATE TABLE test_tbl1 (col1 NUMBER PRIMARY KEY, col2 VARCHAR2(20), col3 NUMBER);Create a materialized view log on the
test_tbl1table. Specify the parallel degree for processing the materialized view log as5, and record changes to thecol2column, including both the old and new values. Configure the materialized view log to start from the current date and to clean up expired records every1day.obclient> CREATE MATERIALIZED VIEW LOG ON test_tbl1 PARALLEL 5 WITH SEQUENCE(col2) INCLUDING NEW VALUES PURGE START WITH current_date NEXT current_date + 1;View the information about the materialized view log on the
test_tbl1table.obclient> DESC mlog$_test_tbl1;The result set is as follows:
+------------+--------------+------+------+---------+-------+ | FIELD | TYPE | NULL | KEY | DEFAULT | EXTRA | +------------+--------------+------+------+---------+-------+ | COL1 | NUMBER | NO | PRI | NULL | NULL | | COL2 | VARCHAR2(20) | YES | NULL | NULL | NULL | | SEQUENCE$$ | BIGINT(20) | NO | PRI | NULL | NULL | | DMLTYPE$$ | VARCHAR2(1 ) | YES | NULL | NULL | NULL | | OLD_NEW$$ | VARCHAR2(1 ) | YES | NULL | NULL | NULL | +------------+--------------+------+------+---------+-------+ 5 rows in setChange the materialized view log on the
test_tbl1table to record changes to thecol2andcol3columns.obclient> CREATE OR REPLACE MATERIALIZED VIEW LOG ON test_tbl1 PARALLEL 5 WITH SEQUENCE(col2, col3) INCLUDING NEW VALUES PURGE START WITH current_date NEXT current_date + 1;View the information about the materialized view log on the
test_tbl1table.obclient> DESC mlog$_test_tbl1;The result set is as follows:
+------------+--------------+------+------+---------+-------+ | FIELD | TYPE | NULL | KEY | DEFAULT | EXTRA | +------------+--------------+------+------+---------+-------+ | COL1 | NUMBER | NO | PRI | NULL | NULL | | COL2 | VARCHAR2(20) | YES | NULL | NULL | NULL | | COL3 | NUMBER | YES | NULL | NULL | NULL | | SEQUENCE$$ | BIGINT(20) | NO | PRI | NULL | NULL | | DMLTYPE$$ | VARCHAR2(1 ) | YES | NULL | NULL | NULL | | OLD_NEW$$ | VARCHAR2(1 ) | YES | NULL | NULL | NULL | +------------+--------------+------+------+---------+-------+ 6 rows in set
