Out_of_place MV Refresh Is Taking Long Time and Redo Increases Significantly
Last updated on JANUARY 31, 2018
Applies to:Oracle Database - Enterprise Edition - Version 126.96.36.199 to 188.8.131.52 [Release 12.1]
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.
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