It appears that dump marker pertains only to database subscriptions.

We are using table subscriptions. How do I not lose data accrued during dump
and load from primary to target, if new records are being created in the
process of replication refresh?

On 6/1/10 00:41 , Tester wrote:
modify repdefs to replicate all columns

suspend connection to yout replicate db.

dump

load

modify repdefs to use autocorrection

resume connection

wait until queues are drained

disable use of autocorrection on repdefs

modify repdefs to replicate minimal columns

Yes, it looks like this is a viable option.
However, I discovered that the REP 12.6 MSA configuration allows to
replicate tables the same way, but skipping the rep. definitions part (if
you deal with databases that look the same). You can still select which
tables to replicate and it works faster.
And then you can use the dump marker as well. The only bug here is - when
using "define subscription ... use dump marker", the replication server sa
(or id you're creating defs under) needs to have the same password as the
source (but not the target) database, otherwise it bombs out with the "Login
failed" error. Weird, but at least it works.


"species8472" <species8472 (AT) ergens (DOT) op.het.net> wrote

You can also use autocorrection on top of MSA, just need to recreate the
table defs for those tables you're planning to activate it.


"Tester" <tester22 (AT) tester (DOT) cc> wrote



--- news://freenews.netfront.net/ - complaints: news (AT) netfront (DOT) net ---