COMPLETE - All rows deletes and replaced.
FAST - Only changes in base table are transfered to the MVIEW, rather than replacing all the rows.
FORCE - A FAST is performed, if this cannot be done a COMPLETE is done.
You'll need to define material view logs to use a fast refresh and there are a number of restrictions.
Updatable is used if you want the MVIEW to be updatable, and the changes to be refleacted in the base table.
Query rewrite is necessary if you want Oracle to rewrite SQL statements to take advantage of available MViews if they would improve performance.
One of the objects is the materialized view definition itself. The other is the actual table that holds all the rows. I'm not sure why your version does not list this properly. I'm using 9.2 and I get:
SQL> select object_name, object_type from user_objects;
quote
-----------
One of the objects is the materialized view definition itself. The other is the actual table that holds all the rows. I'm not sure why your version does not list this properly. I'm using 9.2 and I get:
-------------
there is lot of difference between 8i Materialized views and 9i materialised views
some of the features which i noticed is
8i does not support automatic refresh on its own . where as 9i does support . we need to do manual refresh in 8i .
i think in 8i it is a concept of snapshot which is called materialized views in 9i . ofcourse even in snapshots it creates materialized views.
Bookmarks