I have 3 databases that grow so large that I can almost never open them. log.nsf, admin4.nsf, and ddm.nsf. I have the space savers tab set to only keep 5 days worth of info but the databases continue to grow. From what I hear, this is not normal. Does anybody have any suggestions on why this might be occurring or how I can bring them back to a manageable level?
Subject: Re: Log.nsf
Good Evening Jim,
That’s a rather interesting issue. I’m not sure what is causing it, but I thought I would pass along this Technote which may help.
Regards,
-Bob
Do not distribute outside IBM. Draft Information - Subject to change.
Is there a way to limit the size of the Domino server log (log.nsf)?
Product:
Lotus Domino > Lotus Domino Server > 8.0, 7.0, 6.5, 6.0
Platform(s):
AIX, HP-UX, i5/OS, Linux, OS/390, OS/400, Solaris, Windows
Doc Number:
1220275
Date:
11/07/2008
Problem
The Domino console log can have its size limited with the Notes.ini parameter ‘Console_Log_Max_Kbytes’.
What about the log.nsf database?
Unlike the Domino Console log, the size of the ‘log.nsf’ cannot be limited by a setting or a Notes.ini parameter to a given size.
However, it can be kept under control:
The size of the ‘log.nsf’ is dependant on how much is logged to it (various logging levels) and for how long (number of days retained).
To keep the size under control, it is a balance between how much space is made available for the ‘log.nsf’, and how much information is required to be logged and for how long.
- There are three levers to control the size of the log.nsf:
-
the ‘days’ value of the ‘log’ parameter in the notes.ini
-
a possible log filter; see Admin Help (Creating log filters)
-
the following logging settings:
-
‘Passthru_LogLevel’
-
‘DIIOPLogLevel’
Log_AgentManager
Specifies whether or not the start of agent execution is recorded in the log file and shown on the server console.
Log_DirCat
Logs information about the Directory Catalog task to the Miscellaneous Events view of the log file (LOG.NSF).
Log_Replication
Specifies the level of logging of replication events performed by the current server.
Log_Sessions
Specifies whether individual sessions are recorded in the log file and displayed on the console.
Log_Tasks
Specifies whether the current status of server tasks is recorded in the log file and displayed on the console.
Log_Update
Specifies the level of detail of Indexer events displayed at the server console and in the log file.
Log_View_Events
Specifies whether messages generated when views are rebuilt are recorded in the log file.
Mail_Log_To_MiscEvents
Determines whether all mail event messages are displayed in the Miscellaneous Events view of the log file.
Mail routing
“Logging level” field on the Router/SMTP - Advanced - Controls tab of the Configuration Settings document.
Modem I/O
File - Preferences - User Preferences - Ports - COMx - Trace
Modem script I/0
File - Tools - Preferences - Notes Preferences - Ports - COMx - Trace - Options
Traced network connections
Set a com port option in the Port Setup dialog box.
Web Navigator
The “Retriever log level” field on the Server Tasks - Web Retriever tab of the Server document.
- In addition, the following can be checked:
-
that ‘Don’t maintain unread marks’ is checked in the database properties, together with ensuring that other properties are under control (maintain ‘LastAccessed’, limit entries in ‘$UpdatesBy’ & ‘$Revisions’ fields etc.)
-
perform a “compact -b” on ‘log.nsf’ daily after 4 AM (when the purging occurs) to compact white space for re-useability.
-
after heavy logging for troubleshooting purposes, turn the relevant debugging off, use “compact (-c or -B)” to recover database space, or even create a new ‘log.nsf’ (shutdown Domino, rename ‘log.nsf’, start Domino) if really necessary, to resume normal operations Domino logging.
- Since Notes/Domino 6, there is a way to log high levels for longer periods (volume+length) without seriously sacrificing performance and risks: in order to keep older log information out of the live log.nsf, Server Archiving can be used.
Because the log.nsf is a live ‘system’ database that is frequently updated, it is not the best candidate for monstrous sizes (performance impact, log integrity risk increased, etc.)
One way of keeping more worth of log is to use archiving (hence to an archive databse as opposed to a live database). Then because the log archive database is not as exposed as the log itself, you can keep a few weeks worth of data there , that you can full text index (FTI), and then set to automatically purge the documents after a few weeks.
The server archiving could be scheduled before the daily ‘log.nsf’ purging which occurs - by default at 4 AM - by defining the archiving settings (Database Properties) and scheduling “compact log.nsf -A” at 3 AM, for instance.
© 2008 IBM Corporation. All rights reserved.
Material may not be reproduced or distributed in any form without permission.
Subject: is it data or empty space?
What’s the percent space utilization?How many documents are in the database?
What’s the size of some documents?
Subject: answers part 2
Sorry, forgot to mention 9.5% space used.
Subject: answers
The first example is the log.nsf. Its 8.8 GB with 363,000 docs. I have the space savers tab to only keep 7 days of info which appears to be working.
Subject: I see same problem in some installations
HiI have seen this on several occations, mostly with administrative databases like Adminp, log, DDM etc.
Check out this post :