Replication BUG?

I have a db on two servers (replicas) and 6 notes clients. First server is 6.5.2 on win2000, second is 6.0.2CF2 on linux redhat. Notes Clients are 6.0.3PL(tested also on 6.5.2EN). Scenario:

UserA create document on serverB(linux). Users from local replicas cant see this doc because of readers fields.

There is some flow(few days), local users cant see this doc.

After that flow i’m changing form in that doc, add other users to readers and authors fields(by role and " * "), create some responses to that doc.

Problem:

After replication local users can’t see this doc on local replicas(“Document has been deleted”), can on server.

Using notespeek i see deletion stub of that doc on local replicas. Users can see this doc on server replicas, cant see on local. Responses i created are visible on all replicas. If i access that local db with my id(i have all priviledges, roles etc.), ofcourse i dont see that doc(only deletion stub). Replication on my id dont change anything(no errors during replication process).

So i made a test:

I putted that local replica on third server and run replication process, and missed docs are back!

(this is a regular issue, not sinlge document)

Can anyone explain this to me ??

Thanks.

Subject: Replication BUG ?

Try clearing the replication history and things should be fine.

Subject: RE: Replication BUG ?

I cleared replication history(on both sides) and nothing happened.That was first step i made. I also run a fixup and compact.

I save that doc few times more to update $revisions and $updatedby.

Nothing happened.

Subject: RE: Replication BUG ?

It clearing the history didnt do the trick, then i guess you can delete the replica and create a new one. Reason being, that initally the user didnt have read access to the documents and hence they never came in the replica And then the value of the readers field was modified on the server and the user eventually got access. But during replication these documents will not come in since they were ignored earlier. I am not quite sure whether i have made my self clear, but re-creating the replica should solve the problem.

Subject: RE: Replication BUG ?

Yes.Recreacion replica solved problem, until next document was created.

Problem occur on ALL local replicas, on all documents specific type.

This metod is not good.