This content has been marked as final. Show 2 replies
2500 notebook databases ?
If the solution is to use MV Logs, I guess that they plan to implement FAST refresh's.
However, the MV Log can grow very rapidly if even a single one of those 2500 "remote" databases does not do a Refresh. Oracle will keep maintaining the MV Log "waiting" for that one lone ranger to come back -- and this means that the MV Log will grow and refresh's by the other 2,499 databases may, after some time, perform poorly.
and Oracle Support Note #1031924.6
Hemant K Chitale
Thank you very much for your answer.
According to the solution provider, the mvews will be configured with refresh force and the mview logs on the server side will be cleaned on a daily basis, so that entries older than 30 days are removed. A client that hasn't updated for more than 30 days will perform a full refresh.
Bu I have no idea nor a reference with such numbers of clients doing mviews replications. Therefore it's quite difficult to preview the impact on the times used for fast and full refreshes...