Re: Materialized View Log - ??

Hello,
Well - that is pretty much why I am asking... :)

I have done rather extensive testing and have implemented a solution to a particular problem which required a trigger to be operating on the COMMIT operation. The triggers on the MV tables are now firing when the COMMIT occurs. I specifically did not execute any creation script for the MV log - and I have checked with both Quest Schema Manager and Quest SQL Navigator to see if the MV logs were somehow created automagically for me - behind the scenes - I do not see them.

So, I am pretty confident (although as always - I could be wrong) that: 1) My triggers on my MV tables are firing during the COMMIT and 2) I have no materialized log.

Note that I started using these MV from an example from Thomas Kyte (asktom.oracle.com) which did not include the creation of a materialized log.

So, I was wondering of what purpose the MV logs are and under what circumstances one is required to use them?

Thanks.
Tim.

"Jusung Yang" <JusungYang_at_yahoo.com> wrote in message news:130ba93a.0304151602.3822d81e_at_posting.google.com...
> "Timothy Madsen" <timothy_madsen_at_bigfoot.com> wrote in message
news:<b7hjm3$j4v$1_at_bob.news.rcn.net>...
> > Hello,
> > I am not clear on why/when one needs to use a 'materialized view log'.
> >
> > Currently, in my Oracle 8.1.7.3.0 database, I have created a few
> > materialized views (refresh fast on commit) - simply for the purpose of
> > having a 'commit trigger'.
> >
> > It seems to work fine without having the materialized view log being
> > created - so I was wondering under what circumstances the log is
required
> > and what it does?
> >
> > Thanks.
> > Tim.
>
> Are you sure? Without a materialized view log, you should not be able
> to create the MV with "REFRESH FAST" - ON COMMIT or otherwise. MV log
> is needed if you wish to fast refresh your MVs.
>
>
> - Jusung Yang
Received on Wed Apr 16 2003 - 07:42:28 CDT