DCT Idiosyncrasies

While tinkering with Domino Configuration Tuner today, I noticed that it recommends adding Debug_Logger_Buf_Full_No_Wait=1. However, rerunning DCT after adding the entry yields a different recommendation:

One or more settings were found in NOTES.INI that usually should not be set: 
DEBUG_LOGGER_BUF_FULL_NO_WAIT=1

Looks like something squeaked by QA.

Another finding worth mentioning is the recommendation to use CREATE_R85_LOG=1. I don’t necessarily have a problem with that recommendation, but the suggested implementation method is atrocious:

Recommendation: 
Bring down the server. Back up existing transaction logs, then delete them. Set Create_R85_Log=1 in the server NOTES.INI and restart the Domino server to have new logs created using the updated format. The new logs will have properly aligned I/O blocks. There is no need to verify the current block size. Domino will use correctly format the log even if the block size is 512.

Um, don’t do it that way, please. If you want to use, CREATE_R85_LOG=1:

  1. Set it in the ini (or via the config doc).
  2. Disable transaction logging for the server via the server doc.
  3. Restart the server.
  4. Verify via a “show server” console command that transaction logging is, in fact, disabled.
  5. Via the OS, delete the transaction log files (including the nlogctrl.lfh file).
  6. Enable transaction logging for the server via the server doc.
  7. Restart the server.

Standalone IBM Traveler Maintenance Post-9.0.1.7

Beginning with IBM Traveler 9.0.1.8, the NTS_DEFRAG_INTERVAL_DAYS= ini setting is no longer valid.

If the setting is still present in the Traveler server’s ini, you will see the following warning on the server console (and/or in the log) when Traveler starts:

Traveler: WARNING *system Unrecognized IBM Traveler parameter in notes.ini: NTS_DEFRAG_INTERVAL_DAYS

If the server was upgraded with the NTS_DEFRAG_INTERVAL_DAYS= in place, the upgrade process appears to transfer the previously set interval. The same result can be achieved by issuing: tell traveler dbmaint set interval 30

You can then verify the set interval using: tell traveler dbmaint show

Don’t forget to remove the NTS_DEFRAG_INTERVAL_DAYS= setting from your post-9.0.1.7 server’s ini.

In a standalone DB situation where you want to trigger Traveler database maintenance, you can issue the following command at the console: tell traveler DBMaint run

This will set the ini parameter NTS_DEFRAG_ONCE=1 which will trigger defrag at the next Traveler restart. The server will automatically remove the NTS_DEFRAG_ONCE=1 setting after the triggered defrag completes.

Again, in a standalone DB situation, you could automate regularly scheduled defrags to run by:

  1. Using the “tell traveler DBMaint set” commands to set the desired interval, time, day
  2. Creating a Program document that issues the server command, restart task traveler, just after the time set in the command above