|
|
|
date: Mon, 21 Jan 2008 10:12:22 +1030,
group: microsoft.public.access.replication
back
Re: Modified records not synchronizing, no errors given
Hi David,
Thanks, this seems to have worked, though I'm still comparing tables to make
sure all changes have sync'd.
Do you have any idea what causes this problem? And any way to quickly
identify it has occurred? It looks like i'll have to pay more attention to
the sync process other than just checking for conflicts!
Thanks,
Mark
"David W. Fenton" <XXXusenet@dfenton.com.invalid> wrote in message
news:Xns9A2CB66B6C832f99a49ed1d0c49c5bbb2@64.209.0.91...
> "Mark" <nospam@nospam.nospam> wrote in
> news:OmNxD57WIHA.1208@TK2MSFTNGP05.phx.gbl:
>
>> I have a replica farm on a server managed with Replication Manager
>> 4.0. This farm direct syncs to a few unmanaged replicas on our
>> LAN.
>>
>> One of the unmanaged replicas on the LAN has updates to existing
>> records in a table that aren't being synchronized to the server
>> farm and other replicas.
>>
>> There are no errors or conflicts in any of the database back ends,
>> and even after compact/repair on all database back ends, the
>> modified records aren't being replicated to the server farm.
>
> One way to "wake up" a replica like this is to create a new replica
> from it and then try to synch that back to the main replica set. If
> that works, then you can try to synch back to the problematic
> replica and see if it works again. If it does, delete the newly
> created replica. If it doesn't, delete the bad replica and use
> MoveReplica to put the new one in place of the old. Then you'll want
> to alter your synch schedule accordingly to reflect the new replica.
>
> --
> David W. Fenton http://www.dfenton.com/
> usenet at dfenton dot com http://www.dfenton.com/DFA/
date: Tue, 22 Jan 2008 10:58:18 +1030
author: Mark am
Re: Modified records not synchronizing, no errors given
"Mark" <nospam@nospam.nospam> wrote in
news:Oa5l$4VXIHA.484@TK2MSFTNGP06.phx.gbl:
> "David W. Fenton" <XXXusenet@dfenton.com.invalid> wrote in message
> news:Xns9A2DB04D022F5f99a49ed1d0c49c5bbb2@64.209.0.91...
>
>> Do you have your production replicas under a regular compact
>> schedule? If not, you would be wise to make sure they are
>> compacted regularly.
>
> No. I occasionally run the compact manually.
>
> I could use Windows 'scheduled tasks' to run the /compact command
> line, is it safe to run this if the synchronizer is running?
> (assuming I set the compact and synchronize schedules to not
> clash)
On the non-managed replicas, yes.
On the managed replicas, no.
For compacting the managed replicas, I'd use a VBScript that shuts
down the synchronizer, does the compact, and then restarts the
synchronizer. I'd use the TSI Synchronizer for starting the
synchronizer and shutting it down, but I'm not sure what I'd do for
the compact. I'm sure that it's possible to use late binding to
somehow utilize DAO or JRO to do it, but I've never done it.
--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
date: 23 Jan 2008 21:48:46 GMT
author: David W. Fenton lid
|
|
