OceanBase

A unified distributed database ready for your transactional, analytical, and AI workloads.

Product Overview

DEPLOY YOUR WAY

OceanBase Cloud

The best way to deploy and scale OceanBase

OceanBase Enterprise

Run and manage OceanBase on your infra

TRY OPEN SOURCE

OceanBase Community Edition

The free, open-source distributed database

OceanBase seekdb

Open source AI native search database

Customer Stories

Real-world success stories from enterprises across diverse industries.

View All

BY USE CASES

Mission-Critical Transactions

Global & Multicloud Application

Elastic Scaling for Peak Traffic

Real-time Analytics

Active Geo-redundancy

Database Consolidation

Comprehensive knowledge hub for OceanBase.

Blog

Live Demos

Training & Certification

Documentation

Official technical guides, tutorials, API references, and manuals for all OceanBase products.

View All

PRODUCTS

OceanBase Cloud

OceanBase Database

Tools Connectors and Middleware

QUICK START

OceanBase Cloud OceanBase Database

BEST PRACTICES

Practical guides for utilizing OceanBase more effectively and conveniently

Learn more about OceanBase – our company, partnerships, and trust and security initiatives.

About OceanBase

Partner

Trust Center

Document Feedback

REFRESH

Last Updated：2026-05-07 11:26:25 Updated

REFRESHE is used to refresh a specified materialized view.

Applicability

This topic applies only to OceanBase Database Enterprise Edition. OceanBase Database Community Edition only provides MySQL mode.

Syntax

DBMS_MVIEW.REFRESH (
    { list                 IN     VARCHAR2
    | tab                  IN     DBMS_UTILITY.UNCL_ARRAY}
    [, method                 IN     VARCHAR2       := NULL]
    [, rollback_seg           IN     VARCHAR2       := NULL]
    [, push_deferred_rpc      IN     BOOLEAN        := true]
    [, refresh_after_errors   IN     BOOLEAN        := false]
    [, purge_option           IN     BINARY_INTEGER := 1]
    [, parallelism            IN     BINARY_INTEGER := 0]
    [, heap_size              IN     BINARY_INTEGER := 0]
    [, atomic_refresh         IN     BOOLEAN        := true]
    [, nested                 IN     BOOLEAN        := false]
    [, out_of_place           IN     BOOLEAN        := false]
    [, skip_ext_data          IN     BOOLEAN        := false]
    [, refresh_parallel       IN     BINARY_INTEGER := 0]
    [, nested_refresh_mode    IN     VARCHAR2       := NULL]
);

Parameters

Note

Non-nested materialized views do not support cascading refreshes. Specifying the nested and nested_refresh_mode parameters is therefore meaningless, and the default is to refresh the materialized view independently.

Parameter	Description
list	A list of materialized view names to be refreshed, separated by commas. Currently, only a single materialized view can be refreshed at a time. Multiple materialized views cannot be refreshed simultaneously.
tab	An array of materialized view names to be refreshed. Currently, only a single array of materialized view names can be refreshed at a time. Multiple arrays of materialized view names cannot be refreshed simultaneously.
method	Defines the refresh strategy for the materialized view. This parameter can be specified when creating the materialized view to set the default refresh strategy. Valid values: `F` or `f`: Fast refresh. `?`: Force refresh. `C` or `c`: Complete refresh. `A` or `a`: Always refresh, which is equivalent to `C`.
rollback_seg	This parameter has no effect and is retained for Oracle compatibility.
push_deferred_rpc	This parameter has no effect and is retained for Oracle compatibility.
refresh_after_errors	This parameter has no effect and is retained for Oracle compatibility.
purge_option	This parameter has no effect and is retained for Oracle compatibility.
parallelism	This parameter has no effect and is retained for Oracle compatibility.
heap_size	This parameter has no effect and is retained for Oracle compatibility.
atomic_refresh	This parameter has no effect and is retained for Oracle compatibility.
nested	Specifies the refresh mode for nested materialized views. Valid values: `FALSE`: The default value. Indicates that the nested materialized view is refreshed independently. `TRUE`: Indicates that the nested materialized view is refreshed in a cascading manner.
out_of_place	This parameter has no effect and is retained for Oracle compatibility.
skip_ext_data	This parameter has no effect and is retained for Oracle compatibility.
refresh_parallel	The concurrency level for refresh operations, i.e., the number of threads that can execute refresh operations simultaneously.
nested_refresh_mode	Specifies whether the cascading refresh of nested materialized views is consistent or inconsistent. Valid values: If the `nested` parameter is specified as `FALSE`, specifying the `nested_refresh_mode` parameter will result in an error. If the `nested` parameter is specified as `TRUE`: Valid values for the `nested_refresh_mode` parameter: `inconsistent`: Indicates an inconsistent cascading refresh. `consistent`: Indicates a consistent cascading refresh. If the `nested_refresh_mode` parameter is not specified, the default is an inconsistent cascading refresh.

Examples

Independent refresh mode:

Specify only the mv_name parameter.

obclient> CALL DBMS_MVIEW.REFRESH('mv1');

Specify the mv_name parameter and set the nested parameter to false.

obclient> CALL DBMS_MVIEW.REFRESH(
    'mv1',
    nested=> false);

Inconsistent cascading refresh mode:
- Specify the mv_name parameter, set the nested parameter to true, and do not specify the nested_refresh_mode parameter.
```
obclient> CALL DBMS_MVIEW.REFRESH(
    'mv1',
    nested=> true);
```
- Specify the mv_name parameter, set the nested parameter to true, and set the nested_refresh_mode parameter to inconsistent.
```
obclient> CALL DBMS_MVIEW.REFRESH(
    'mv1',
    nested=> true,
    nested_refresh_mode => 'inconsistent');
```
Consistent cascading refresh mode:

Specify the mv_name parameter, set the nested parameter to true, and set the nested_refresh_mode parameter to consistent.
```
obclient> CALL DBMS_MVIEW.REFRESH(
    'mv1',
    nested=> true,
    nested_refresh_mode => 'consistent');
```

The following are error scenarios:

Set the nested parameter to false and specify the nested_refresh_mode parameter. An error is returned.

obclient> CALL DBMS_MVIEW.REFRESH(
    'mv1',
    nested=> false,
    nested_refresh_mode => 'xxxx');

Do not specify the nested parameter and specify the nested_refresh_mode parameter. An error is returned.
```
obclient> CALL DBMS_MVIEW.REFRESH(
    'mv1',
    nested_refresh_mode => 'xxxx');
```

Set the nested parameter to true and set the nested_refresh_mode parameter to an invalid string. An error is returned.

obclient> CALL DBMS_MVIEW.REFRESH(
    'mv1',
    nested=> true,
    nested_refresh_mode => 'invalid string');

References

For more information about refreshing materialized views, see Refresh a materialized view.

Previous topic

PURGE_LOG

Last

Next topic

Overview of DBMS_MONITOR