Parameter:
TRANSLOG_AutoFixupShort description: Enables (
1) or disables (0) the automatic fixup after a transaction log recovery at server start.Profile
Parameter | TRANSLOG_AutoFixup |
Category | Transaction log |
Component | Server |
Available since | 9.0.1 |
Supported versions | 9.0.1, 10.0, 11.0, 12.0, 14.0, 14.5, 14.5.1 |
GUI equivalent | Server document |
Possible values | 0 = manual fixup • 1 = automatic fixup (recommended) |
Description
After an unclean server stop, Domino runs a transaction log recovery on the next start. If a database remains inconsistent afterwards (e.g. because the translog does not cover all changes),
TRANSLOG_AutoFixup decides how to proceed:1(default): theFixuptask is automatically launched for the affected databases.
0: the databases are marked as “needs fixup”; the administrator must startFixupmanually.
In production,
1 should remain active so that after crashes the server returns to availability with as little intervention as possible. Only in forensic scenarios (“no changes to the data before analysis”) does 0 make sense.Example configuration
TRANSLOG_AutoFixup=1
Notes & pitfalls
- Only effective when
TRANSLOG_Status=1(translog enabled).
- Takes effect after a server restart.
- Can be maintained in the Server document under “Transactional Logging” (preferred).
- Complementary to
TRANSLOG_Status,TRANSLOG_Style,TRANSLOG_Path.