Materialized View Refresh: Locking, Performance, Monitoring
(Doc ID 258252.1)
Last updated on SEPTEMBER 09, 2021
Applies to:Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Oracle Database Cloud Service - Version N/A and later
Oracle Database - Enterprise Edition - Version 188.8.131.52 and later
Oracle Database Cloud Schema Service - Version N/A and later
Information in this document applies to any platform.
The purpose of this article is to provide an understanding of the locking and
performance issue related to materialized view refreshes. How a refresh
process can impact and be impacted by other refresh processes and user
processes is also discussed. This article also provides some basic queries
that can be used to monitor materialized view refreshes.
This article is intended for DBA's and support analysts who are familiar with
distributed materialized view concepts. <NOTE:258021.1> How to monitor the
progress of a materialized view refresh can be reviewed along with this article
to gain a full understanding of the materialized view refresh process.
The information in this article is specific to distributed materialized views.
While much of the information is applicable to local materialized views, there
may be differences in locking and performance expectations for local
materialized views. For information specific to local materialized view
refreshes, please see the Oracle Data Warehousing Manual.
From this point on, the term 'mview' will be used in place of 'materialized
'Materialized view' and 'Snapshot' are synonymous as of 8i.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!