Ncompact and nfixup problems after upgrade from 5 to 6 and my workaround

Hi,

here is my problem:

For migration testing purposes I installed a 6.0.1 test server. Then i ran the compact and fixup on this server against my 5.0.11 mail databases. Here is the problem:

R5.0.11 mail databases with R6.0.1 offline ncompact -C:

08.05.2003 09:46:10 Compacting mailDatabase.nsf

08.05.2003 09:46:37 Error compacting mailDatabase.nsf: Invalid or nonexistent document

after that the ODS remains at level 41.

R6.0.1 offline nfixup -F against these databases:

08.05.2003 10:30:29 Document (UNID OF00E68E70:D8B3461B-ONC1256D1D:00291201) in database mailDatabase.nsf has been deleted

sometimes i also get: Unable to fixup database mailDatabase: The integrity of a database storage container has been lost - the container will be rebuilt.

this happens to about every 4th mail-database out of several hundreds…

And now the “workaround”:

if i run ncompact and nfixup against these databases on my Release 5 server and after that ncompact and nfixup on my Release 6 server then NO error at all comes up.

So i will compact and fixup ALL databases offline BEFORE the upgrade and then once more AFTER the upgrade to directly update the ODS. Of course this doubles upgrade time!

PS:

Lotus Support do not have any information about this behaviour yet or did not tell me. Indeed there are several postings here in this forum pointing to the same problem.

regards

Markus

Subject: Exactly our problems

Thanks for the suggestions. My next upgrade was similar except we were not going to compact on both sides …but now will. ALso we were going to disconnect network cables and leave domino running to get error msg.

Subject: ncompact and nfixup problems after upgrade from 5 to 6 and my workaround

I am facing same problem when client is replicating mail file from server

“invalid or non-existing document”

Then I run compact -c to upgrade ODS to 43 in the client side, but I cannot upgrade my server ODS

becoz…the server is running still with R5.

I cannot run Fixup in the client side becoz I dont have fixup executablein the client.