Thanks,
Sarita
Have you followed the instructions in the error message? The default
MaxLocksPerFile is 9500, and every time I've ever encountered this
error, I just increase it to 100000, run the synch, then change it
back to the default.
This is usually the result of synching after a very long time of no
synchs, so that there are a large number of updates to be
propagating between the replicas. It usually indicates that you
ought to be synching more often. It can also happen when you do
something drastic, like deleting or adding a very large number of
records, but that's a much less common trigger for this message.
--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
> I am well aware of what your saying but it still doesn't solve my
> replication issue. I can' t follow the error because this is the
> error message crases the database. The database size is over
> 300,000 and its growing. Any ideas?
Other than unreplicating, I don't have any ideas.
Why did you allow it to get into this state? Don't do it again!
Apparently you did not read my orginal post that clearly stated that I HAVE
RECENTLY INHERITED A REPLICATED DATABASE. Please refrain from scolding me
like a child. Grown-ups are suppose to be more cautious and aware of the
comments falling out of their mouths. Don't do it again! Thank you for your
assistance.
Sarita
"David W. Fenton" wrote:
> .
>
> Apparently you did not read my orginal post that clearly stated
> that I HAVE RECENTLY INHERITED A REPLICATED DATABASE. Please
> refrain from scolding me like a child. Grown-ups are suppose to be
> more cautious and aware of the comments falling out of their
> mouths. Don't do it again! Thank you for your assistance.
You can be sure you won't get any more from ME.
<PLONK>