Searching large transaction logs

Added v2.0.7 If there are too many INVALID records, for example more than 500 invalid records in one search in the transaction logs, search stops and an error message is generated in the server log. User intervention is required to clean up the transaction logs. This change prevents the server from searching for long periods and blocking other activities.

For example, the error message contains the following text:

Starts from <file name>, over 500 bad transaction records found, transaction log searching stopped.

The error message indicates where the search was started. For example, if the user searched from December 1 to December 12, the server searches multiple log files. The Starts from indicates where in the transaction logs the cleanup must start.

This change in the behavior of searching large transaction logs prevents the TM1® Server from generating large logs. However, user intervention is required to clean up the invalid records if the logs become too large.

Changed v2.0.9 This behavior changed in IBM® Planning Analytics version 2.0.9. The default behavior is to search all logs. You can configure a limit to the number of invalid logs that are allowed before search stops. This configuration parameter is private. Contact support to learn more.