Start/notes.ini Parameters/DEBUG_REPL_CHANGES

DEBUG_REPL_CHANGES

🛠️
Parameter: DEBUG_REPL_CHANGES
Short description: Logs, per replicated note, which Note ID / UNID was transferred from which server to which target database – helpful for disputed replication conflicts.

Profile

Parameter
DEBUG_REPL_CHANGES
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 = off (default), 1 = basic, 2 = incl. field changes

Description

While DEBUG_REPL_ALL enables a general, very verbose replicator trace, DEBUG_REPL_CHANGES focuses exclusively on the changes – that is, every individual note that is transferred, updated, or deleted as part of a replication. The Note ID, UNID, source/target database are logged, and at level 2 the changed fields are additionally captured.
Ideal for topics such as a specific note does not replicate, conflict notes arise for no apparent reason, deletions unexpectedly propagate to other replicas, audit: which server passed on which change?.

Example configuration

DEBUG_REPL_CHANGES=2
Debug_Outfile=/local/notesdata/IBM_TECHNICAL_SUPPORT/repl_changes.log

Notes & pitfalls

  • Level 2 produces a lot of output during large replications.
  • Takes effect immediately via set config DEBUG_REPL_CHANGES=...; a restart is not strictly required.
  • Entries appear in console.log and in Debug_Outfile.
  • Complementary to DEBUG_REPL_ALL, Log_Replication.
  • For conflict analysis, additionally check the Replication History of the affected DB.