Hm.{ Link }

I wonder if the log_update=2 would have also provided the information ?

I take my hat off to you sir! Many thanks.

I was having a big problem with replication between 2 servers where the replication would transfer 53M every replication rather than the <300K normally seen. It would also take nearly an hour rather than the 10secs it usually took.

I had seen this before being down to a corrupt doc, but in this case all I was getting in the logs was 'partially replicated due to a previously reported error' which helpfully had never been reported. fixup and compact did not find any problems. The db was not full text indexed anyway, but I thought I'd try it, and bingo, found the doc, deleted it and we are back to normal with replication.

Thanks again,

Jez.

Hi Julian,

We're facing the same problem and we've already have tried all suggested.

Once we have identificated the corrupted documents we cannot delete them because 32k error is raise.

Do you have any ideas?.

Thanks in Advance.

use ytria scanEZ to remove the document once you have the noteID / UNID

Fixup -V helps (Domino 8.5.2FP3), all other tips failed, even ScanEZ couldn't delete the document.

12/01/2011 06:32:41 PM Remote console command issued by Michael/415/INT/EEC: Load Fixup "database.nsf" -V

12/01/2011 06:33:17 PM Queuing compact command for database.nsf by Michael/415/INT/EEC

12/01/2011 06:33:18 PM Document NT000216C6 in database D:\Lotus\Domino\Data\database.nsf is damaged: Field is too large (32K) or View's column & selection formulas are too large

12/01/2011 06:33:18 PM Document (UNID OF3E4B8880:85F8FDB7-ONC1257952:00348576) in database D:\Lotus\Domino\Data\database.nsf has been deleted

12/01/2011 06:33:29 PM Completed consistency check on database.nsf

12/01/2011 06:33:29 PM Database Fixup: Shutdown

thanks for the tip, that didn't work in my previous cases... I will try it on 8.5.3 when such problem arises again.

Interesting thread ...

But .. why do you want to delete these documents ?

Are they worthless ?

I would have suggested an agent which would have set the summary flag of the item to false ... so - this item would be able to store text upto 64k.

And next thing .. if the item has to be shown in views ... cut value at 30k and insert rest of values in another field which probably same name ...

OK .. for sure anything to do for a workaround ...

but only worth if the docs have to be kept !

Best regards

Peter, you cannot open these kind of documents anymore. The only thing you can do with them is to delete them.