Home » Server Options » Replication » Understanding MV refresh concept
Understanding MV refresh concept [message #673718] Thu, 06 December 2018 05:44 Go to previous message
purnima1
Messages: 79
Registered: June 2014
Member
Hi All,

I have one scenario and want to discuss . If any one can give me hint how should I proceed and what next step should I follow.

We have two database D1 and d2 . Table S_ORG_***** is present in d1 and in d2 we have prepared MV with same name S_ORG_***** to bring the data from remote database d1 using db link.

We have one job that refreshes MVs at 12:00 AM EST. When I check in all_mviwes I am getting it last refresh end time as 12/6/2018 12:26:45 AM for above mentioned MV

Refresh method is script is written as force but in all_mview I can find it as FAST.

So as per my understanding we have received all the data from d1.S_ORG_***** into d2.S_ORG_***** by 12/6/2018 12:26:45 AM .

Assuming all row are coming for first time when I am running below mentioned query in d2.s_org_**** ( running on MV table)


SELECT SCN_TO_TIMESTAMP(ORA_ROWSCN), row_id FROM D2.s_org_*****


I am getting timestamp after refresh end time. As per my understanding, this means rows have entered in MV table after refresh time .

my question how this could be possible ?
What should I check further to check whether refresh is running again and again but all_mvies is not displaying this information


Please suggest what should I do next in order to analyse this issue
 
Read Message
Read Message
Read Message
Read Message
Previous Topic: Replication solution between two readable/writable databases
Next Topic: still error OGG-01896 is raised after dropping identity feature
Goto Forum:
  


Current Time: Mon Sep 21 02:37:34 CDT 2020