Start/notes.ini Parameters/Temp_Index_Max_Doc

Temp_Index_Max_Doc

Parameter: Temp_Index_Max_Doc
Short description: Limits the maximum number of documents per temporary full-text index that the Notes client/server can build for a database without a permanent FT index. Without this limit, large databases (mail file > 50,000 documents, archives) can lead to memory issues and slow searches when implicitly indexing for the search bar.

Profile

Parameter
Temp_Index_Max_Doc
Component
Notes Client, Domino Server (Indexer)
Category
Full-text indexing / Performance
Available since
9.0.1 FP10 and 10.0 (per KB0033195)
Default
not set → no upper limit; the temporary index covers all documents in the database
Value range
positive integer (e.g. 50000, 100000)

Description

During search operations on a database without a permanent full-text index, Notes Client and Domino Server build a temporary index that is held in memory. With very large databases (e.g. archive mail files, log databases, large discussion DBs), this temporary index can:
  • consume large amounts of memory (RAM) on the client/server,
  • cause noticeable delays for the user ("Notes does not respond" while searching),
  • in extreme cases, lead to crashes (Notes client) or memory exhaustion (server).
With Temp_Index_Max_Doc=N, an upper limit of N documents is set for these temporary indexes. If the database contains more documents, Notes/Domino reports an error and the user must:
  • run the search with restrictive selection criteria so that fewer than N documents are involved, or
  • create a permanent full-text index for the database.
Per HCL KB0033195, the parameter is intended to:
  • improve client stability for searches in extremely large mailboxes,
  • prevent server-side memory pressure when many users search simultaneously without an FT index.

Examples

Limit to 50,000 documents per temporary index:
Temp_Index_Max_Doc=50000
Client-side recommendation in HCL Notes 14.x for large mail files:
Temp_Index_Max_Doc=100000
Deactivate (default behavior → no limit):
; Temp_Index_Max_Doc remains unset

Notes

  • Workplace, not symptom relief: The right answer for large databases is a permanent full-text index. Temp_Index_Max_Doc is a guardrail to prevent worse damage when no permanent index has been created.
  • Error when exceeded: When the limit is reached, Notes/Domino returns an error message; the search aborts. The user must then restrict their search or create an FT index.
  • Client and server: The parameter applies to both Notes clients (search via the search bar) and Domino servers (server-side searches via Notes API or Web).
  • Activation: Takes effect after restart of the Notes client or Domino server.
  • Diagnostic: When the limit is reached, the indexer logs an error in the log; in the Notes client, the user receives an error dialog.
  • No effect on permanent FT indexes: As soon as a database has a permanent FT index, the parameter does not apply.

Sources (HCL Product Documentation)

  • HCL Customer Support – KB0033195 "How to limit the size of temporary FT indexes via the Temp_Index_Max_Doc notes.ini setting" (Applies to: Notes/Domino 9.0.1 FP10, 10.0.x, HCL Domino 11.0.x and higher).