NoteOpenCallBack Message

Hi,

I have a 7GB DB replicating between two 6.0.3 Servers (Both 2000 SP4).

Both servers have manager access and replication has been spot on for 12 months.

During the past week I have had problems replicating certain documents. Clearing rep history and forcing rep seems to work on the odd document, but I have started to see the current message on console:

NoteOpenCallback: n=13, TotalNotes=30, NotesToCopy=22

NoteOpenCallBack: hNote=0, (source)NoteIDxxxxx, status0x225=Document has Been deleted

NotesStream: Requested 30, got 20

Nothing has changed in the way of design or security. The only thing that has changed on one of the servers is that Transactional Logging has been enabled. This has since been disabled, but the problem still exists.

Monitoring doc counts on both servers seems to imply that documents are actually been deleted, but the logs contain no information that will help.

Has anyone seen this message? Any Ideas?

Will an upgrade to 6.0.4 help, or should I hold back for the moment?

Thanks in advance.

Jase

Subject: NoteOpenCallBack Message

hi

I know this message from big problems replicating db’s but message was “…invalid or non existant document…” (Not “…document has been deleted…”) → Solution was running Fixup see http://www-10.lotus.com/ldd/nd6forum.nsf/55c38d716d632d9b8525689b005ba1c0/9ac7906015ae356a85256eaf005aebdb?OpenDocument

There is another post for that message but no solution offered:

http://www-10.lotus.com/ldd/nd6forum.nsf/55c38d716d632d9b8525689b005ba1c0/bbb18422f387791685256ec1003808ce?OpenDocument&Highlight=0,n%3Fteopencallback

Try running Fixup from Console, may be running Compact will also help

Hope this will help

H.Mueller

Subject: RE: NoteOpenCallBack Message

Thanks Heinrich. I’d already tried Fixups/compacts from the console, but to no avail.In the end, I ended up creating a new replica over the weekend and all seems to be ok now.

If anyone has any ideas or fixes for the future, it would be good to hear them.

Thanks,

Jason