Re: Materialized View Question

From: <jkstill_at_gmail.com>
Date: 9 Sep 2005 09:34:42 -0700
Message-ID: <1126283682.796571.44340@g49g2000cwa.googlegroups.com>

A MV uses an internal table MLOG_$<source_table_name> to log changes.

This table is populated by an internal trigger when changes are made to the source table.

This table is in turn used to populate the target table. That is done when a dbms_mview.refresh is requested, either manually or via dbms_job.

When applying archive logs in a database recovery, the database is not open.

The source table will change, but I do not believe the MLOG_$ table will be updated (database is not open). The changes will not then propogate to the target table when a refresh is requested.

I would think that a complete refresh would be required in this case.

The caveat is that I have never tried this particular scenario.

Perhaps you should set up a test to see exactly what happens.

HTH Jared Received on Fri Sep 09 2005 - 11:34:42 CDT