Re: Materialized View Question
- From: jkstill@xxxxxxxxx
- Date: 9 Sep 2005 09:34:42 -0700
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
.
- Follow-Ups:
- Re: Materialized View Question
- From: Umberto
- Re: Materialized View Question
- References:
- Materialized View Question
- From: artmt
- Materialized View Question
- Prev by Date: Re: TIMEOUT ON CONTROL FILE ENQUEUE
- Next by Date: Re: Single vs. Multiple Sequences
- Previous by thread: Materialized View Question
- Next by thread: Re: Materialized View Question
- Index(es):
Relevant Pages
|