Home » Server Options » Replication » Materialized View Refresh Problem
icon5.gif  Materialized View Refresh Problem [message #129097] Fri, 22 July 2005 00:08 Go to next message
Abhinav Nigam
Messages: 49
Registered: August 2004
Member
Hi All

If we use REFRESH ON COMMIT option to refresh the mat view, does Oracle refresh the mat view whenever COMMIT is issued on the database?

Does it make a check whether the data in the base tables have been changed? Also Does it make a complete refresh or an incremental refresh?

I tried referring to Oracle White Papers, I am qouting the content

"If the ON COMMIT refresh method is chosen, whenever a materialized view is
affected by changes made to the source data, the materialized view will
automatically be updated to reflect this data. However, it should be remembered
that this update to the materialized view occurs as part of the commit processing
in the transaction where the changes to the base table are made. Therefore, the
commit will take slightly longer, because changes are being made to both the
original table and then any materialized view whose definition includes that table.
"

I could not find answers to my questions in the white paper.

Plz Help.

Regards
Abhinav
Re: Materialized View Refresh Problem [message #129149 is a reply to message #129097] Fri, 22 July 2005 03:35 Go to previous messageGo to next message
bonker
Messages: 402
Registered: July 2005
Senior Member
Read Documentation guide on Materialized View
http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96520.pdf
Re: Materialized View Refresh Problem [message #129251 is a reply to message #129097] Fri, 22 July 2005 14:51 Go to previous messageGo to next message
smartin
Messages: 1803
Registered: March 2005
Location: Jacksonville, Florida
Senior Member
Fires only when commit of transactions involving the table(s) that is used to populate the MV. But this should be easy to test and prove for yourself.
Re: Materialized View Refresh Problem [message #153099 is a reply to message #129097] Thu, 29 December 2005 01:16 Go to previous message
mila82
Messages: 4
Registered: December 2005
Location: Down Under
Junior Member
well i think that if you have an

refresh fast on commit
-> incremental refresh when one of the master/base tables change/commit

refresh complete on commit
-> complete refresh when one of the master/base tables change/commit
Previous Topic: materialized view logs
Next Topic: Improve Materialized View Refresh
Goto Forum:
  


Current Time: Sun Jun 20 07:56:10 CDT 2021