Start/notes.ini Parameters/TRANSLOG_AutoFixup

TRANSLOG_AutoFixup

Parameter: TRANSLOG_AutoFixup
Short description: Controls whether Domino automatically runs a Fixup on the affected database after translog recovery errors: 1 = automatic Fixup (default), 0 = database is blocked from access instead.

Profile

Parameter
TRANSLOG_AutoFixup
Component
Server, also Notes client
Category
Transaction log
Available since
Domino 5.x; currently documented in HCL Domino 9.0.x–14.5.1
Value format
Boolean (0 / 1)
Default
1 (automatic Fixup on)
GUI equivalent
only notes.ini (no direct field in the server document)

Description

Domino runs a translog replay at server startup or on first access to a logged database, in order to bring the file into a consistent state. If this fails (e.g. due to a damaged translog, missing extent, or structurally defective NSF), TRANSLOG_AutoFixup decides the further course of action:

TRANSLOG_AutoFixup=1 (default)

  • Domino automatically runs a Fixup -J on the affected database.
  • Fixup -J repairs the NSF and brings it back online; corrupt documents may be discarded or marked as unreadable.
  • The action is logged in console.log and log.nsf.
  • Recommended for servers and Notes clients where continuous availability is more important than manual review of every damage event.

TRANSLOG_AutoFixup=0

  • Domino performs no automatic Fixup.
  • The affected database is blocked; access returns errors such as "Database is being repaired" or "File is corrupt".
  • The administrator must decide manually (Fixup, restore from backup, re-replicate).
  • Useful on servers with critical data, where automatic Fixup would deliver availability but might mask data loss.

Notes client recommendation (Daniel Nashed)

For translog on a Notes client, typically:
TRANSLOG_AutoFixup=1
TRANSLOG_UseAll=0
TRANSLOG_Style=0
TRANSLOG_Performance=2
TRANSLOG_Status=1
TRANSLOG_MaxSize=256
TRANSLOG_Path=c:\translog
The standard recommendation is 1, since a single damaged mail file entry on a client rarely justifies the effort of manual intervention.

Examples

Server standard configuration:
TRANSLOG_Status=1
TRANSLOG_Style=1
TRANSLOG_Path=D:\Domino\txn
TRANSLOG_AutoFixup=1
TRANSLOG_Performance=2
Critical archive server that should be assessed manually after recovery error:
TRANSLOG_Status=1
TRANSLOG_Style=1
TRANSLOG_Path=D:\Domino\txn
TRANSLOG_AutoFixup=0
TRANSLOG_Performance=2

Notes

  • Effective only after restart – TRANSLOG_AutoFixup takes effect at the next server start.
  • Fixup -J can discard data – In some cases, Fixup discards damaged documents. For critical data, prefer a restore from backup.
  • No server-document equivalent – Unlike TRANSLOG_Style or TRANSLOG_Path, this parameter is not represented in the server document.
  • Companion parameters – TRANSLOG_Status, TRANSLOG_Path, TRANSLOG_Style, TRANSLOG_Performance, TRANSLOG_MaxSize, TRANSLOG_UseAll.

Sources (HCL Product Documentation)