Re: Fast refresh takes eternity

Note:209571.1 from metalink clarifies things a little bit:

• Fast refreshes are more efficient than complete refreshes WHEN there are few changes to the master table(s) because the participating server and network replicate a smaller amount of data.
• The processing time of a fast snapshot refresh versus a complete snapshot refresh: "The amount of data adjusted (inserted, updated, deleted) could cause the execution time of fast refresh to be the same as a full refresh. If this is the case, submit a full refresh."
• MLOG$ Size: Should you find the MLOG$ row count extremely high, truncate the MLOG$ and submit a full refresh.... Please submit a FAST refresh after truncating the MLOG$.