This "complete log scan" is referring to the normal type of scan that happens when you initially launch dbmlsync; to differentiate it from what happens when it is 'hovering'.
If you see this entry right after the hovering entry, then there was some contributing factor to force it drop out of 'hovering mode;. A number of different conditions could cause this including those listed in the DCX article on Synchronization schedules (after the paragraph on "Hovering") and include forced conditions, internal memory conditions and settable thresholds for that.
You may not be used to seeing this if your designs only include a single publication/synchronizaton and/or if you never using the scheduling feature of dbmlsync.
Is there a specific pattern you are seeing that seems different from the above information?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.