Start/notes.ini Parameters/No_Force_Activity_Logging

No_Force_Activity_Logging

Parameter: No_Force_Activity_Logging
Short description: Prevents (1) the Statlog task from automatically enabling activity logging for all databases.

Profile

Parameter
No_Force_Activity_Logging
Category
Logging / Debug
Available since
At least 11.0.1 (HCL documentation)
GUI equivalent
According to HCL, no direct GUI option. Configurable in the configuration document on the NOTES.INI Settings tab.
Possible values
0 = automatic activity logging allowed · 1 = automatic activity logging prevented
Default
None — without an entry, Statlog enables the Record Activity option for every database and adds 64 KB per DB.

Description

According to HCL product documentation:
Controls whether the Statlog task automatically enables activity logging on all databases.
0 - Allows automatic activity logging on all databases
1 - Prevents automatic activity logging on all databases
Even when activity is not being recorded for the database, the information is still recorded in the Activity entry of the Database Usage view in the server's log file.
Statlog's default behavior can result in significant memory overhead with many databases (64 KB × N databases). With No_Force_Activity_Logging=1, Database Usage logging in log.nsf still applies, but without enabling the property on every individual database.

Example configuration

No_Force_Activity_Logging=1
With No_Force_Activity_Logging=1, the activity logging property on the databases stays as the admin set it — Statlog does not change it automatically.

Notes & pitfalls

  • Even without the DB property enabled, Domino captures the Activity entry in Database Usage (log.nsf) — the parameter only suppresses DB-side activation.
  • On large servers with many databases, 1 is often recommended to save the 64 KB overhead per DB.
  • According to HCL, there is no direct GUI equivalent.

Sources (HCL Product Documentation)