When Activity Logging and Activity Trends are enabled on an IBM Lotus® Domino® server in a domain with an existing Sametime® server, the activity.nsf database is created with the same replica ID as vpuserinfo.nsf.
Vpuserinfo.nsf uses the same hardcoded replica ID as activity.nsf.
Resolving the problem
This issue was fixed in Domino releases 6.5.6 and 7.0.
Fix details: SPR# CSCT65YMW6
Refer to the Upgrade Central site for details on upgrading Notes/Domino.
The Activity Trends database (activity.nsf) now has a different domain replica ID. The Activity Trends task will automatically update an existing database to the new replica ID. The value of the "ATC_SET_REPLICA_ID" notes.ini file variable can be used to change this behavior, if necessary.
In relases prior to 6.5.6 and 7.0, the suggested workaround is to create a new copy of activity.nsf (File -> Database -> New Copy), which will change the database's replica ID.
Valid Values are:
Negative (-1) : will reset the replica ID to the old value, which conflicts with Sametime's vpuserinfo.nsf.
0 : will cause the replica ID to remain unchanged
Positive (1) : will cause the new value to be used.
Note: Since activity.nsf should never replicate, no real problems should result from this issue.