Materialized View Refresh Problem [message #129097] |
Fri, 22 July 2005 00:08 |
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 #153099 is a reply to message #129097] |
Thu, 29 December 2005 01:16 |
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
|
|
|