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 NOVEMBER 07, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 10.2.0.5 and laterInformation 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
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
Symptoms |
Changes |
Cause |
Solution |
References |