Yes with a physical standby you can refresh from the MV log on the DG side
after failover.
There are of course potential bugs/features sometimes if the failover happens
at the right moment as the MV initializes on the original Primary side that you
may get the ‘ORA-12034: materialized view log on ''.'' younger than last
refresh’ after failover. Just depends on how many MV logs and MVs are running
and of course the roll of the dice when the failover occurs. My experience has
been 2 such errors in 5 years over 121 database failovers for databases with
Materialized Views/Snapshots on 10g/11g. I haven’t seen it occur in 12c yet.
Matthew Parker
Chief Technologist
Dimensional DBA
425-891-7934 (cell)
D&B 047931344
CAGE 7J5S7
<mailto:Dimensional.dba@xxxxxxxxxxx> Dimensional.dba@xxxxxxxxxxx
<http://www.linkedin.com/pub/matthew-parker/6/51b/944/> View Matthew Parker's
profile on LinkedIn
<http://www.dimensionaldba.com/> www.dimensionaldba.com
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On ;
Behalf Of Sanjay Mishra (Redacted sender "smishra_97" for DMARC)
Sent: Wednesday, June 1, 2016 9:14 AM
To: Oracle-l Digest Users
Subject: MV and Dataguard
Has anyone used MV with Dataguard ?
If I had MV log on Primary and does the Standby will also have Data refreshed
in both base tables as well as MV logs ?
If MV log has the data, then Can we use it after switchover to Dataguard to
Fast refresh the Target remote Database MV's ?
TIA
Sanjay
