Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Mailing Lists -> Oracle-L -> [oracle-l] Re: MVs

[oracle-l] Re: MVs

From: Vladimir Begun <Vladimir.Begun_at_oracle.com>
Date: Fri, 23 Jan 2004 16:45:10 -0800
Message-ID: <4011C016.8010109@oracle.com>


Oracle9i Data Warehousing Guide Release 2 (9.2) 8 Materialized Views

If you specify REFRESH FAST, Oracle performs further verification of the query definition to ensure that fast refresh can be performed if any of the detail tables change. These additional checks are:

If some of these restrictions are not met, you can create the materialized view as REFRESH FORCE to take advantage of fast refresh when it is possible. If one of the tables did not meet all of the criteria, but the other tables did, the materialized view would still be fast refreshable with respect to the other tables for which all the criteria are met.

A materialized view log should contain the rowid of the master table. It is not necessary to add other columns.

To speed up refresh, you should create indexes on the materialized view's columns that store the rowids of the fact table.

-- 
Vladimir Begun
The statements and opinions expressed here are my own and
do not necessarily represent those of Oracle Corporation.

Ramón Estevez wrote:

> I checked metalink and the documentation either is not clear or I don't
> understand, choose that one, but just are two tables with a single join.
Received on Fri Jan 23 2004 - 18:45:10 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US