...as asked in title.

asked 21 Jul '16, 14:41

Breck%20Carter's gravatar image

Breck Carter
27.0k444614889
accept rate: 21%


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?

permanent link

answered 21 Jul '16, 15:32

Nick%20Elson%20SAP%20SQL%20Anywhere's gravatar image

Nick Elson S...
7.3k35107
accept rate: 31%

1

No pattern difference or other problem, other than me not being even one page ahead of the client in reading the Help :)

(21 Jul '16, 15:49) Breck Carter
Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×20

question asked: 21 Jul '16, 14:41

question was seen: 289 times

last updated: 21 Jul '16, 15:49