Updatable materialized view replication site

1. Even if you are disconnected from the primary site or the primary materialized view site, you can query and update datasets that have been copied to the local site (dataset ). 2. Requirements for replication over multiple master sites

1. Even if you are disconnected from the primary site or the primary materialized view site, you can query and update the data set that has been copied to the local site ). 2. Requirements for replication over multiple master sites

Updatable materialized view description
1. updatable materialized views must belong to a materialized view group.
2. the updatable materialized view is always based on a single table, although multiple tables can be referenced in a subquery.
3. updatable materialized views can be refreshed quickly.
4. Oracle can update music videos to remote master tables or materialized views. Changes to remote master tables will also be transmitted to all replication sites.
5. When creating updatable materialized views, do not use column alias (column aliases). Otherwise, an error occurs when you add the materialized views to the materialized view group using CREATE_MVIEW_REPOBJECT.
6. updatable materialized views do not automatically use the default values of the primary table or primary materialized view columns.

Benefits of updatable materialized views
1. Even if you are disconnected from the primary site or the primary materialized view site, you can query and update the data set that has been copied to the local site ).
2. Replication of multiple primary sites requires less resources, but still supports data update operations.
3. compared with the replication of multiple primary sites, this reduces the pressure on network resources, because materialized views can be refreshed as needed (refreshed on demand ), the replication of multiple primary sites transmits changes at regular intervals (regular intervals.

Updatable materialized view site structure

This image shows that client applications can query and update an updatable materialized view at the materialized view site. these applications can also update data at the master. when the materialized view refreshes, the materialized view is updated with the changes at the master and the master is updated with the changes at the materialized view.

Update materialized view site steps
Note:
Before you build materialized view environments, you must set up your master site, create a master group, and set up your intended materialized view sites. Also, If conflicts are possible at the master site due to activity at the materialized view sites you are creating, then configure conflict resolution for the master tables of the materialized views before you create the materialized view group.
1. Setting Up Master Sites

2. Setting Up Materialized View Sites

3. Create a Master Group

4. Create Materialized View Group

For detailed operation steps, refer:
Advanced Replication Management API Reference

Master group replication and silent Processes
SUSPEND_MASTER_ACTIVITY Procedure
This procedure suspends replication activity for a master group. You use this procedure Quiesce the master group. You must call this procedure from the master definition site.
DBMS_REPCAT.SUSPEND_MASTER_ACTIVITY (
Gname IN VARCHAR2 );

RESUME_MASTER_ACTIVITY Procedure
This procedure Resumes normal replication activity after quiescing a replication environment.
DBMS_REPCAT.RESUME_MASTER_ACTIVITY (
Gname IN VARCHAR2,
Override in boolean: = false );

Refer:
Overview of Updatable Materialized Views

Updatable Materialized Views