Start/notes.ini Parameters/DB_FIXUP_LOG

DB_FIXUP_LOG

🛠️
Parameter: DB_FIXUP_LOG
Short description: Controls the verbosity with which the Fixup task logs corrected notes/views and detected inconsistencies – important for post-crash analyses.

Profile

Parameter
DB_FIXUP_LOG
Category
Logging / Debug
Component
Server
Available since
10.0
Supported versions
10.0, 11.0, 12.0, 14.0, 14.5, 14.5.1
GUI equivalent
notes.ini only (no GUI)
Possible values
0 = summary only, 1 = per NSF, 2 = per note (very verbose)

Description

Fixup is the repair task that Domino starts after an unclean server stop or for corrupt databases. DB_FIXUP_LOG controls how verbosely these repairs are written to the log – from a single-line summary per NSF up to detailed entries per repaired note.
For production servers, level 1 is a good compromise; level 2 is only worthwhile for forensic cases but should be reset afterwards so log volume does not get out of hand.

Example configuration

DB_FIXUP_LOG=1

Notes & pitfalls

  • A higher level = noticeably more I/O on the log system.
  • Entries are visible in console.log and in log.nsf (keep Console_Log_Enabled=1 active).
  • Level 2 is practically mandatory for HCL Support tickets.
  • Takes effect immediately on the next Fixup run (load fixup ...).
  • Complementary to Debug_Outfile, DAOS_LOGGING, Console_Log_Enabled.