| When the Analyze > Activity tool starts, it checks for documents in the $ActivitySchema view of the server's LOG.NSF in order to determine what activity data can be analyzed. This error is generated if no documents are found in the $ActivitySchema view.
The ActivitySchema documents are static in nature (the content of them does not change after they are created), but they contain the field $NoPurge=1.
Due to a problem with the log purging code (defined by the log= line of the NOTES.INI) these documents are inadvertently purged once the log purge interval is reached (default is every 7 days) as well. |
| The problem with documents purging from the log even with $NoPurge defined on them has been reported to Quality Engineering as SPR# as LJAS6F6V92.
Each time the server is restarted the schema documents are touched by the server (or re-written if they do not exist), so provided the Domino server is recycled more frequently than the log purge interval is reached, this problem should not occur.
Thus, if scheduled maintenance is performed requiring the server to be recycled every 30 days, then increasing the purge interval to 31 days should be sufficient to prevent this problem from occurring.
Keep in mind that increasing the purge interval for the LOG.NSF will cause the database size to increase as well.
NOTE: The log purge interval is defined by the fourth argument in the log= line in the NOTES.INI. For example, the following line would cause the log to purge unmodified documents every 7 days:
|
Error: 'No activity data found...' when attempting