After upgrading to ND6, is the general consensus out there, to compact all files on the server with at least the -K parameter to enable the larger UNK per database?
I know the directory needs it, but what does everyone think about applying it to all dbs?
Simon
Subject: Running compact with -K parameter
Hi Simon, here are some of my installation notes when we upgraded to Domino 6 early this year.
Some info about the -K parameter:
http://www-10.lotus.com/ldd/nd6forum.nsf/0/a58aa321de908cbe85256d2e002df317?OpenDocument
I used the -K parameter on some of our larger databases, but I don’t think small databases really need it. In fact, when you create a new blank database the “allows more fields in database” option is not enabled on the database properties.
Shutdown the Domino server.
Reboot the machine.
Turn off all anti-virus software, and all other applications that may be running.
This is also a good time to run Windows Update.
Open Windows Explorer, and delete these files (as you see fit, they will be recreated automatically)
catalog.nsf
admin.nsf
busytime.nsf
statrep.nsf
events4.nsf
reports.nsf
log.nsf (delete or move outside the Domino directories)
Look in the data directory and delete all the existing full-text folders. For example, “name.ft”.
Install the Domino 6 server software. DO NOT start the Domino server.
BEFORE STARTING the Domino 6 server, do the following:
(These actions will take several hours on the large Domino servers. 60GB of databases may take 10 hours to compact, depending on the server’s speed.)
Open a command window (dos prompt). Issue the following commands, one at a time, from the Domino program directory. After one command is finished, move on to the next one listed.
Run a fixup on key system databases.
nfixup names.nsf -f -j -v
nfixup admin4.nsf -f -j -v
Run a compact on key system databases, also increases the UNK table.
ncompact names.nsf -c -i -K -F
ncompact admin4.nsf -c -i -K -F
Rebuild views on key system databases
nupdall names.nsf -R
nupdall admin4.nsf -R
Compact all databases and convert them to the new ODS.
ncompact
Rebuild all database views, and full-text indexes (if previously built).
nupdall
Start the Domino server.
When prompted to upgrade the address book, answer yes (Y).
Let the server runs for 5 minutes.
Type “load design”.
Let the server run for at least 30 minutes.
Use a Domino 6 Administrator client. Check that all databases are now using ODS 43.
Subject: RE: Running compact with -K parameter
“I used the -K parameter on some of our larger databases, but I don’t think small databases really need it”
A small database can have enough long and unique field names to cause UNK problems. Likewise a huge database may be nowhere near UNK table limits. It is not related to database size.
There is a utility called ItemDef available in the Knowledgebase that will tell you for a given database what mode the UNK table is in, either size limited (default up to 64,000 bytes) or number of entries (which is the “allow more fields” mode and switches to 64,000 entries instead).
names.nsf in general will not blow the standard limit unless it is a D6 design and you have defined policy documents. Unless of course you have customized it to heck and have added lots of long field names that are not in the default design.
Subject: RE: Running compact with -K parameter
Sorry, by “small database” I was trying to say “small application”. Most database designs will not have many unique field names.