This content has been marked as final. Show 4 replies
user12360077 wrote:When you want to use FAST REFRESH of MView.
Now, I have the following questions
1. Why I do setup the materialized view log and it works?
2. What is the purpose of materialized view log (CREATE MATERIALIZED VIEW LOG ON ......)? Where I have to apply (master or destination site)?It contains records about all MViews which refer to master table, those records contains info about if MView got changed row or not.
MView Log is created for a table at master site.
A Materialized View Log ("MV Log") is on the source table. It captures information of all DML that is executed against the table.
The Materialized View ("MV") Refresh can be executed as a FAST refresh by reading the MV Log and identifying rows that have undergone since the last DML and then replicating only those selected rows -- instead of doing a Full Scan of the source table and replicating all the rows of the source table each time.
Hemant K Chitale
Hi Hemant K Chitale,
Thanks for your explaination. Now I am facing the problem of resource exhaustion in destination size. The case is when the master listener stop, the resource of destination site will be exhausted that lead destination listener cannot function at all. The master site is now using 11.2.0. and destination site is running Windows server with 220.127.116.11.0. Any idea? How can I check the materialized view status when no log generate (force update)? Thx!
I want to continue in this thread which is related to mview refresh.
Current Situation:: I have a table 'Tbl_Voicechat' on Destination site. M-view Log already on Table A and also there is an index on SNAPTIME$$. A mview TBL_VOICECHAT_NEW1 is running on table using the db link.
When I am recreating all this things it is refreshing fine for few refreshes. But After 1-2 Days its is being like hangs.
Can you please tell me, what to do in which area for this refreshment problems.
Thanks in Advance