Explanation:
Some of the following information is also available as part of the entry for SERVER_NAME_LOOKUP_NO_UPDATE.
While the Update task is explicitly updating Domino Directory (names.nsf) views, any NameLookup or NIFFindByKey calls that need to access a view being updated will back up on the locked collection until the update is done.
Any threads waiting on a NameLookup call will wait because the collection is being updated. Thus, you will see this behavior in the form of hangs. For example, NRPC connections (which do a NameLookup for authentication) might either take extra time to complete or return saying 'server is not available'.
Unnecessary view updating can be suppressed with the use of DEBUG_ENABLE_UPDATE_FIX=MASK (where MASK can equal any bit pattern up to 0x7FFF, entered as an integer) & SERVER_NAME_LOOKUP_NO_UPDATE=1. These settings should be used together.
NOTE: Having this setting in the server's notes.ini may impact new program documents showing up in the schedule immediately. Technote 136184 explains a workaround, if needed.
Default:
When absent, Domino Directory views can be updated unnecessarily. This default behavior is equivalent to DEBUG_ENABLE_UPDATE_FIX=0
Recommendation:
Set DEBUG_ENABLE_UPDATE_FIX=32767 on all Domino versions prior to 8.5.
Restrictions:
Introduced for Domino 6.5.5, 7.0.2 & 8.0. No longer required for Domino 8.5 and beyond.
Restarts:
No restart required. Changes to this setting will be detected within 5 minutes.
Related Settings:
Server_Name_Lookup_No_Update
References:
Technote 1254752: NameLookup performance fixes that address unnecessary updates
Technote 1244315: Domino server hangs after replicating Domino Directory
Technote 1364184: Change to Program document not reflected immediately
Domino Configuration Tuner:
This setting is included in the
DCT catalog of best practices.