Out_of_place MV Refresh Is Taking Long Time and Redo Increases Significantly

(Doc ID 2226720.1)

Last updated on JANUARY 31, 2018

Applies to:

Oracle Database - Enterprise Edition - Version to [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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms