

So, the answer is: because the materialized view is a static table-like object dependent on the data set it is selecting that's why to prevent the inconsistencies materialized view references the real object. If you simply drop and re-create the materialized view, the synonyms will automatically point at the newly. There is no requirement that the object pointed to by the synonym exists at all. That's why I would say it is the only way to prevent the errors: reference the real target instead of synonym for creating materialized view. There is probably no need to touch either synonym in the script. From the Wikipedia article on Mode: In statistics, the mode is the value that occurs most frequently in a data set or a probability distribution. The underground table must be recreated then. occur synonym What is a synonym for 'most frequently occurring' - English.

it has totally different amount/data types of columns), the previous structure is invalid then and not working anymore. Using materialized views against remote tables is the simplest way to achieve replication of data between sites.
+Definition%3A+To+become+visible+and+known+Synonyms%3A.jpg)
I cannot find anything useful in Oracle documentation but just enable the logic:
