Prepare for changes in behavior in TM1 Server
IBM® Planning Analytics Local version 2.0.7 and the cloud release of IBM Planning Analytics version 2.0.7 includes updates that change behavior in IBM TM1® Server version 11.5.0. Review this list to prepare for your upgrade.
Default logging level of TM1.Mdx.Interface logger
In IBM Planning Analytics version 2.0.7 or later, the TM1.Mdx.Interface logger reports syntax errors only when set to DEBUG level.
Previously, in IBM Planning Analytics version 2.0.6 or earlier, the TM1.Mdx.Interface logger reported syntax errors when it was set to ERROR level. However, when Planning Analytics for Microsoft Excel or Planning Analytics Workspace generated invalid MDX internally, the tm1server log filled up quickly with a large number of entries in the form:
11276 [6b5] ERROR 2017-10-16 13:51:10.237 TM1.Mdx.Interface
Syntax error at or near: 'hildren},{[Entity].[]})}', character position 21
These errors now appear only when the logging level is set to DEBUG. For more information, see System and performance monitoring.
Default value of RulesOverwriteCellsOnLoad parameter
In IBM Planning Analytics version 2.0.7 or later, if the RulesOverwriteCellsOnLoad parameter is not present in the configuration file then it is assumed to be False by default. This is a change in behavior.
Previously, in IBM Planning Analytics version 2.0.6 or earlier, if this parameter was not present in the configuration file then it was assumed to be True by default.
For more information, see RulesOverwriteCellsOnLoad.
Searching large transaction logs
In IBM Planning Analytics version 2.0.7 or later, 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.