An error has occurred while setup was updating partition information
If insufficient temporary space is available to rebuild the indexes, then you must explicitly drop each index or mark it About Types of Refresh for Materialized Views The refresh method can be incremental or a complete refresh.
It targets the common usage scenario in the data warehouse where both fact tables and their materialized views are partitioned in the same way or their partitions are related by a functional dependency.Both in-place refresh and out-of-place refresh achieve good performance in certain refresh scenarios.However, the out-of-place refresh enables high materialized view availability during refresh, especially when refresh statements take a long time to finish.The in-place refresh executes the refresh statements directly on the materialized view.The out-of-place refresh creates one or more outside tables and executes the refresh statements on the outside tables and then switches the materialized view or affected materialized view partitions with the outside tables.The refresh approach enables you to keep a set of tables and the materialized views defined on them to be always in sync.
In this refresh method, the user does not directly modify the contents of the base tables but must use the APIs provided by the synchronous refresh package that will apply these changes to the base tables and materialized views at the same time to ensure their consistency.
Performing a refresh operation requires temporary space to rebuild the indexes and can require additional space for performing the refresh operation itself.
Some sites might prefer not to refresh all of their materialized views at the same time: as soon as some underlying detail data has been updated, all materialized views using this data become stale.
A complete refresh may be requested at any time during the life of any materialized view.
The refresh involves reading the detail tables to compute the results for the materialized view.
The PCT refresh removes all data in the affected materialized view partitions or affected portions of data and recomputes them from scratch. If you anticipate performing insert, update or delete operations on tables referenced by a materialized view concurrently with the refresh of that materialized view, and that materialized view includes joins and aggregation, Oracle recommends you use , the materialized view is changed every time a transaction commits, thus ensuring that the materialized view always contains the latest data.