How to reduce TM1 transaction log sizes

[Jodha]

Hi All,

Gradually TM1server.log size is increasing in production environment,Some times it end up generating 50 GB log file for single day after running daily save data chore. Is it normal that TM1 server expected to generate 50 GB log file per day ? but on regular basis TM1 server is genrating between 8 to 18 GB logs every day and it is hard to open log files of these size using notepad .
Can some please suggest possible options like which parameter to modify in config file ,turning off cube logging or any other options to look at .

I am on 10.2.2 windows 2008 R2 server with 100 users and 8 to 10 active users on server , AuditLogOn=F in config file .

Reviewed

http://www.tm1forum.com/viewtopic.php?f=3&t=8016

post but not much helpful in my case. Please advise .

Thanks

[qml]

Tm1server.log (a.k.a. server message log) and tm1s.log (a.k.a. transaction log) are not the same thing. For the purpose of this post I will assume you are talking about the server message log.

Check what type of messages are prevalent in your message log and use tm1s-log.properties (you might need to create this file) to control what is logged. You can also set the maximum size of the file, define the backup policy and even split it into separate log files (e.g. SQL-related messages can be printed out to one file, security into another etc.).

A bit of IBM documentation on this subject can be found here.

They don't document all the individual loggers, but you can easily identify the ones that are blowing up your log by just looking at the log entries. If you e.g. see a lot of TM1.Process messages you can reduce the level of logging on that logger by adding this entry to the properties file:

Code: Select all

Log4j.logger.TM1.Process=WARN

It's just an example, but it's easy to figure out.

[lotsaram]

Are you talking about the transaction log tm1s.log or the message log tm1server.log?

Yes transaction logs can get big but why would you ever want to open it in notepad? To control transaction log volume turn logging OFF when doing zero out and data loads that are related to a source system (that you can always reload from) the critical thing to log is user driven input.

If you are talking about the message log then even in a very busy system running TI every other minute or second you're still not going to generate more than a few MB of logs per day with the default INFO level logging. If some loggers are set to DEBUG then you could get GBs worth of message log but you would never do that unless there was a specific issue you were wanting to diagnose.

[David Usherwood]

They don't document all the individual loggers

Can anybody suggest (politely) what the point would be of building a major piece of functionality and not publishing this documentation?
I suppose we can be thankful that (as qml notes) you can turn specific logging off by reading the logfiles to find out what messages are being written and disabling them.
Words fail me.....

[qml]

Can anybody suggest (politely) what the point would be of building a major piece of functionality and not publishing this documentation?

Since they do in fact have the documentation as can be deduced from this line:

Note: Customer support can provide you with guidance and assistance to enable individual TM1 loggers.

... therefore the only logical conclusion on why they don't want to share it publicly is that they like their customers so much that they want to interact directly with them as much as possible.

[Gabor]

There was a file (released on Mar 19, 2007) available at support "INTERNAL_TM1_Server_Logging_Methodology_and_Reference.pdf", which had listed the TM1 logger items for 9.1 FP1 and later. I haven't seen any newer document so far.

[EvgenyT]

There was a file (released on Mar 19, 2007) available at support "INTERNAL_TM1_Server_Logging_Methodology_and_Reference.pdf", which had listed the TM1 logger items for 9.1 FP1 and later. I haven't seen any newer document so far.

... And I'm assuming that one is nowhere to be found either