A materialized view is a stored view query result. The data on which the view is defined is referred to as the master table or tables. The materialized view is stored in its own table, which is refreshed based on changes to the master table or tables. Oracle supports the following types of materialized views:
Read-only – content is based entirely on the master table or tables.
Writable – content can be changed temporarily, but changes are overwritten when the table containing the materialized view is refreshed.
Updateable – updates are also made to the corresponding master table or tables. Updates to the master tables are still reflected in the materialized view upon refresh, so updates can be made in two ways. Additionally, changes to the master table or tables are also reflected in any remote updateable materialized view upon refresh. Here, remote means that the materialized view is defined in a database other than that containing the master table or tables.
For a complete description of materialized view architecture and behavior, see the Oracle documentation.
Instead of replicating the table containing a materialized view, Replication Agent replicates only the master table or tables on which the view query is defined. The materialized view table is subsequently refreshed according to the contents of the replicated master tables. Replication Agent does not support direct replication of the table containing a materialized view. Do not attempt to replicate such a table.
If you are using replication for disaster recovery,
and your primary database contains the master table or tables for
a remote materialized view, and you fail over to the standby database,
the database containing the remote materialized view must be redirected
to point to the standby database before a refresh of the remote
materialized view occurs. Otherwise, the refresh fails.
