Complete Materialized View Refresh Generates Lots Of Archive Logs and Rollback/Undo Activity
Last updated on FEBRUARY 02, 2017
Applies to:Oracle Database - Enterprise Edition - Version 188.8.131.52 and later
Information in this document applies to any platform.
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).
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms