Why is a FAST Refresh of Remote Materialized View Doing Updates While There Are Inserts ONLY on the Primary Table
(Doc ID 2272257.1)
Last updated on JULY 22, 2021
Applies to:Oracle Database - Enterprise Edition - Version 184.108.40.206 and later
Oracle Database Cloud Schema Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
You have a materialized view which selects from a table across a dblink to a primary database. The FAST refresh of the materialized view is running for a very long time. The session running the refresh is spending most of it's time running an update statement. It shouldn't be doing any updates because the materialized view log contains only inserts. The updates appear to be doing nothing for the most part.
Eventually after wasting most of its time on millions of updates, it does the inserts and finishes successfully after several hours. How do you prevent it from doing the updates in the first place? It should only be inserting new rows.
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