Hi,
Don’t know if this is related but since we migrated our clients to Notes client 7, sometimes the replicaID of a mail database on the server side changes on it’s own, but the local replicaID doesn’t follow. We daily run the compact -B task and the server is transaction logged.
Subject: ReplicaID change
I would check the logs around the time the compact occured on days when you discover the replicaID changed. The help does say “Uses in-place compacting, recovers unused space and reduces file size, unless there’s a pending structural change in which case copy-style compacting occurs.”
I wonder if a problem in the copy-style compacting could result in the new replicaID?
Another thought, if this is happening frequently, would be to not run the compact -B for a time and see if the problem stops happening. If so, that would also point to a problem with the compact.
Subject: RE: ReplicaID change
Strangely we don’t get the problem right after the compact -S 5 -B -K. We encountered this issue little after we migrated our clients to the version 7 of the client, but we kept our servers at version 6.5.5 FP1. Does anyone out there has a mixed environment and having problems with that ?