Words and Phrases
Purge logs
Log information in server and client log files, dbdicts containing log information, and web tier log files require to be cleaned up frequently to prevent log files from growing to an unmanageable size, and to avoid Disc Full situations or performance impacts because of huge tables on the relational database system.
The cleanup of web tier log files is managed by the web application server.
Clean up server side log files
It is good practice to remove the log files completely or move them to a separate folder or even another network location before every startup of Service Manager.
Note Some countries have laws regarding which information may be captured in log files and how long log files may by stored before they need to be destroyed. The Service Manager Administrator shall assume responsibility to comply with the local rules.
Purge dbdicts containing log information
Old records in dbdicts containing log information should be cleaned up frequently. The following table describes out-of-box dbdicts containing log information.
| Dbdict | Description |
|---|---|
|
msglog, syslog |
Internal log files |
|
stathistory |
Used for daily tracking of module license usage |
|
systemperform, systemtotals |
Used for system load tracking. This is started and stopped from System Status > System Monitor > Capture. Caution Keeping this activated for a long time may cause slow performance. |
The dbdicts can be purged automatically by scheduling an archive or purge. The out-of-box system provides a background purge to clear the msglog and syslog records that are over 7 days old. Modify the purge interval if needed. To do this, go to the schedule table from the Database Manager and search for “background purge/archive”. You can modify the purge/archive parameters on the Strings tab.