Re: Sync Failed; Record is Deleted -- Append Confusion

Tech-Archive recommends: Fix windows errors by optimizing your registry

On Jul 28, 4:12 pm, "David W. Fenton" <XXXuse...@xxxxxxxxxxxxxxxxxxx>
wrote:
mikej711 <mikej...@xxxxxxxxxxx> wrote innews:8e0b9b2b-7d32-4089-8727-d8ce615d28a6@xxxxxxxxxxxxxxxxxxxxxxxxxxx
:

I found the corrupt record--the s_ColLineage reads OLE instead of
long binary--but can't delete it. Access asks if I want the
deleted it and removes it from the table, but when I reopen the
table, there sits the record. I can remove other records but not
the corrupted one.

Have you compacted after the deletion and before opening it again?

Are there child records that might be preventing the deletion but
the error message is not asking you about it?

Before you do anything drastic, at least try copying the problem
replica to a new file and seeing if that file can synchronize.

If you try all three of those and still get no joy, then you're in
the tough spot of needing to rebuild if not the whole replica set,
at least that one table. I would synch all the replicas that you are
able to synch with the Design Master, then remove referential
integrity between the table with the bad record and any child
tables, then synch around all the replicas you can synch with. At
that point, you may be able to synch with the problem replica (the
change to RI may "jiggle it loose" and allow things to work).

Once that's done, you'll unreplicate the problem table, synch around
the set of synchronizable replicas, and try again synching with the
problem replica. If none of that works, you're really at the point
where there's not much use in doing anything other than restoring
the problem table to replicability in the DM, synching around the
other replicas and then adding the RI back and synching again.

At that point, the problem replica is dead because nothing you did
was able to "wake it up." So you'll have to recover its data
manually. I hope you have time/date stamps in all your records.

Now you really need to try to figure out what the likely causes of
the corruption might be. You don't want to have to go through this
again.

One thing that I'd highly recommend is to set up each replica with
at least one backup replica. This is the simplest possible replica
farm, and insures that if the first replica gets corrupted, you'll
have all the data since the last synch with the backup replica.

--
David W. Fenton                  http://www.dfenton.com/
usenet at dfenton dot com    http://www.dfenton.com/DFA/

When a corrupted replica is compacted two files are created, one that
has the replica's name but has lost replicability and other named
"~tempRec" which seems to be a copy of the replica minus the bad
record. "~tempRec" is still replicable. Is "~tempRec" what it seems?
Could I rename it and use it as a replacement for the bad replica?

MJ
.

Relevant Pages

  • Re: Intermittant 3167 error/indexing problem
    ... risk of corruption. ... Network drivers can get upgraded/downgraded. ... Indirect synchs between a replica that is being edited? ... The synch should only happen when the edited replica is ...
    (microsoft.public.access.replication)
  • Re: Synchronize Database Replication
    ... database is not updated. ... could you provide me coding to Synchronize the databases. ... The scenario is, when a user open the replica, the ... direct synch fail, so my guess is that the data you think should be ...
    (microsoft.public.access.replication)
  • Re: Synchronization History AWOL
    ... How do you allow your laptop users to synch back at the office. ... You said you wouldn't manage the edited replica but that you would ... unmanaged and the hub synch replica managed, with a scheduled synch ... I will note that I don't have any current clients using ...
    (microsoft.public.access.replication)
  • Re: Cannot find search key: error message of death?
    ... warnings about doing direct synchs over a VPN, ... onto the server itself and doing a local direct synch. ... Indirect Synch process a top prioirty. ... re-initializing your replica set (i.e., ...
    (microsoft.public.access.replication)
  • Re: Replman - Managing multiple sets of application databases
    ... The laptop should be ... replica on the server. ... It's much easier to share one hub replica ... would add unnecessary risk of conflicts) should use a direct synch, ...
    (microsoft.public.access.replication)