Since notes 6.0 upgrade, when I try to replicate my database I get this error : Invalid or nonexistent document. Failed with notes.
Does anyone have any ideas or experience with this error ?
Thank you,
Susana Pires
Subject: Replication - Invalid or nonexistent document
I’m running release 6.0.1 CF and I had the same problem. What you can do is to run “nfixup mail/db.nsf” with –f –l (Use –j to include transaction logged databases) switches. That deleted a lot of invalid documents from the database, and after that i had no more problems with the replication.
Subject: RE: Replication - Invalid or nonexistent document
Hi,
I am facing same problem, I am trying to repair the document, but cannot, any help is highly appreciated.
How to run fixup on client pc ? Becoz my client Discussoin thread got corrupted.
08/15/2003 12:40:10 PM Index update process started
08/15/2003 12:40:10 PM Updating views in c:\lotus\notes\data\sandytan.nsf
08/15/2003 12:40:33 PM Error updating view ‘(Discussion Threads)’ in c:\lotus\n
otes\data\sandytan.nsf: Invalid or nonexistent document
08/15/2003 12:43:05 PM Index update process shutdown
Subject: RE: Replication - Invalid or nonexistent document
Hi,
I found out that the problem was caused after an upgrade. The problem is that the consistency of the databases has to be checked before the upgrade. A replication to the client should be done before the server upgrade too. I solved the problem by running the “fixup” from the server console on different databases. You can even run “nfixup” from the OS console if you are need that before you start your Domino server. In your case it should be done on the database you have problems with. Add the switches you need.
I ran “load fixup -f -j -v -l”
-f = Exhaustive fixup, all docs are checked
-j = Include transaction (If you have transaction logged databases)
-v = Exclude database views. Faster process.
-l = Log all processed databases.
If you need to rebuild your views, use UPDALL
Run COMPACT to upgrade the ODS level.
When you are done with these steps, delete the client’s local database and make a new replication.
If this doesn’t help, delete the index, repeat the steps and create the index again!