Out_of_place MV Refresh Is Taking Long Time and Redo Increases Significantly (Doc ID 2226720.1)

Last updated on FEBRUARY 13, 2017

Applies to:

Oracle Database - Enterprise Edition - Version 12.1.0.1 to 12.1.0.2 [Release 12.1]
Information in this document applies to any platform.

Symptoms

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.

Changes

 Upgraded to 12c.

Cause

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