After Dropping/Recreating a Materialized View, Data is Not in Sync with Other Mviews in the Same Refresh Group (Doc ID 2045350.1)

Last updated on AUGUST 25, 2015

Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.5 and later
Information in this document applies to any platform.

Symptoms

Replication mviews (those without joins or aggregations) in a refresh group don't seem to be consistent among themselves when refreshed. A subsequent refresh will put the "missing" data into the mview.

Changes

 A materialized view that was created in an RDBMS version < 10.2.0.5 was dropped and recreated.

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