Out_of_place MV Refresh Is Taking Long Time and Redo Increases Significantly
(Doc ID 2226720.1)
Last updated on MARCH 11, 2020
Applies to:Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database - Enterprise Edition - Version 184.108.40.206 to 220.127.116.11 [Release 12.1]
Oracle Database Exadata Express Cloud Service - Version N/A and later
Gen 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
Information in this document applies to any platform.
An Out-of-Place (OOP) refresh is taking more than twice the time of a regular complete MV refresh. Additionally, you may see a large increase in redo activity, even if the mview itself has the NOLOGGING attribute.
Upgraded to 12c.
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