I had a user who could not archive to a local 1.5GB archive database (just after upgrade from r5.0.10 to r6.1 CF1 with the infamous Invalid or nonexistent Document error.)
nupdall would give the same error - compact -c would take too long. To I decided to create a new copy of the mail file, this failed with a break point error.
I decided then to create new replica - this seemed to stall at 0% and hung the client, so I used the ZapNotes ulitily to close the client.
I restarted the client, and it started a consistency check of the archive mail file - this deleted some documents flagged as damaged, then…I could archive!!!
I feel that if I was able to run a fixup (nfixup style like nupdall) a lot of time would have been saved.
In summary, I would really like to know how to run a fuxup or force the consistency check locally on local databases. Is this possible without hanging the client first?
Subject: How do I force a fixup/consistency check of a local database? (archive problems)
we have a product for central notes desktop administration, which integrates with lotus notes clients at the time the login dialog is displayed, which means, that the notes client has not yet locked any databases.
we could enhance our product or do a spin off so that fixups could be done (individually/optionally) before notes actually starts - would that be of interest ?
Subject: How do I force a fixup/consistency check of a local database? (archive problems)
If the database on your local machine is not located in the DATA folder of Lotus Notes, then consider changing its location (I would recommend, directly in the DATA folder). The close Notes and start it again. It should automatically perform a consistency check on the databases located in the DATA folder.