'fast' refresh of several remote MViews ...
we have a Master DB and replicate via MViews to several remote slave DB in a 'fast refresh' mode on demand.
After successfull replication, the relevant rows in the MView-Log will be deleted.
How does Master DB know when to delete rows in MView-Log?
Where is the information stored which slave DB has already got a refresh and which hasn't?
Thanks & best regards
hob