Q
Problem solve Get help with specific problems with your technologies, process and projects.

Why does new Domino server keep corrupting my log.nsf file?

I have a brand new Domino server, installed about two weeks ago, running Domino 6.5.4 FP2. I have over 500GB free space and 2GB of RAM, tons more than Domino needs to run efficiently. My log.nsf has corrupted five times since I installed the server. It says "Database corrupt -- cannot allocate space." What should I be looking at?

I have a brand new Domino server, installed about two weeks ago, running Domino 6.5.4 FP2. I have over 500GB free space and 2GB of RAM, tons more than Domino needs to run efficiently. My log.nsf has corrupted five times since I installed the server. It says "Database corrupt -- cannot allocate space." What should I be looking at?
First, check any operating system utilities that may be involved in I/O on the drive on which the Domino Data directory resides. Things like scandisk and defrag are able to modify "files" at the disk level. Remember that Domino databases are just files on a disk drive. If your Domino server is running while a disk utility is actively modifying files, including Domino databases, corruptions can occur easily. (see Side Note in yesterday's blog).

Also note that certain Domino databases are always open by the server (names -- or Domino Directory, and the log is a list of examples of these files), so running any disk utilities that may alter the file structure or attempt an I/O on a file would most likely affect one of these databases.

One other thing to mention is the backup system you are using. Does your backup software support "Open File" backup? Many vendors supply add-ins that enable systems like Domino and the M$ mail servers to stay active while the backup process is running, rather than shutting them down during backup.

If you have recovered the database successfully, check the consistency of the application by running the fixup and compact tasks with appropriate switches. For example:

Load Compact -c -i log.nsf 
Finally, in the case of this SPECIFIC database, while the log is an important review and diagnostic tool, it does not contain any configuration settings for your Domino server. Therefore, I would be inclined to "archive" this log database -- due to the persistent errors you are describing -- and begin with a new log. Shut down the server, move and/or rename the log file (i.e., put it in an admin folder under data and call it oldlog.nsf) and then restart the server. When the server initializes it will recognize the log does not exist and will create a new one for you.
This was last published in April 2006

Dig Deeper on Lotus Domino Designer

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

Start the conversation

Send me notifications when other members comment.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Please create a username to comment.

-ADS BY GOOGLE

SearchWindowsServer

Search400

  • iSeries tutorials

    Search400.com's tutorials provide in-depth information on the iSeries. Our iSeries tutorials address areas you need to know about...

  • V6R1 upgrade planning checklist

    When upgrading to V6R1, make sure your software will be supported, your programs will function and the correct PTFs have been ...

  • Connecting multiple iSeries systems through DDM

    Working with databases over multiple iSeries systems can be simple when remotely connecting logical partitions with distributed ...

SearchDataCenter

SearchExchange

SearchContentManagement

Close