Complete Materialized View Refresh Generates Lots Of Archive Logs and Rollback/Undo Activity
(Doc ID 413188.1)
Last updated on FEBRUARY 22, 2024
Applies to:
Oracle Database Cloud Schema Service - Version N/A and laterGen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
The issue here is that the database is producing a large amount of UNDO and REDO. This is evident from the archive log generation and the amount of rollback segment usage.
On closer inspection of the database usage over this time it was noticed that a materialized view and/or materialized view group refresh was occurring.
The MVIEW refresh method in both cases above has been defined as the COMPLETE refresh with the ATOMIC_REFRESH option being default value (TRUE).
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |