Funky replication message that might be an error message

One of our customers are experiencing some problems with some databases not replicating correctly. It might be connected to a recent upgrade to Domino 7.0.1 from 6.5.4 but we’re not sure. The problems can some times be fixed by clearing the replication history and manually replicating but that’s not really a long term solution.

To further troubleshoot I enabled the console log (set config console_log_enabled=1) and summary replication logging (set config log_replication=5) in the notes.ini via the Domino console. At the next scheduled replication I observed the strange messages (in bold below):

06-09-2006 10:49:35   Pushing dbname.nsf to servername/Organization dbname.nsf
06-09-2006 10:49:35   0 Bytes Saved from Field Level Replication
06-09-2006 10:49:35   0 Bytes Saved from Field Level Replication
06-09-2006 10:49:35   0 Bytes Saved from Field Level Replication
Unambiguous Note
NO Place Holders
Unambiguous Note
NO Place Holders
Unambiguous Note
NO Place Holders
Unambiguous Note
NO Place Holders
Unambiguous Note
NO Place Holders
06-09-2006 10:49:36   0 Bytes Saved from Field Level Replication
06-09-2006 10:49:36   0 Bytes Saved from Field Level Replication
06-09-2006 10:49:36   0 Bytes Saved from Field Level Replication
06-09-2006 10:49:36   0 Bytes Saved from Field Level Replication

I have never seen these messages before and it seems like they only appear with the databases we are having problems with.

If anyone has any information about these messages that they would be willing to share I would be a happy camper. I guess it’s also one of those times to be grateful that one can call Lotus Support!

3 thoughts on “Funky replication message that might be an error message”

  1. We are running into this as well. And it is on our NAB! yikes.
    I turned on Log_Replication=4 in the Notes.INI to check field level value changes because in the replication log I am seeing 295 documents being updated from our hub server to all the servers in our environment over and over and over… Always around 290-295 documents and always “updated.” There are many of these “no placeholder” errors as well, and I am having strange things happen (like renamed people reverting, old names showing back up, etc.).

    Just a “me too” post, I’m still chasing down the problem. If you have contacted Lotus Support on this issue, please share your findings…

    We are running a mixed 6.5.x and 7.0.x environment at this time.

Comments are closed.