Process re-starting in a chore TM1 10.2.0
Posted: Sat Jun 28, 2014 6:09 am
Hi
Hoping someone can help with an issue that I have not come across before
A long running chore has processes that seem to be restarting, the chore is only scheduled once at 12:30am local time
I have attached an extract from the TM1Server log
Note that the process DIM_Build_Business_Unit_Grouping_Tenant runs at local time 12:30:02 AM, then at 3:09:54 AM and 3:36:17 AM before finishing at 4:42:29 AM
There is no information as to WHY this process restarted in the logs
The information I have provided is just an extract, I have more information that I can provide but the log file is large.
Other information:
There is another chore running just prior to this that started at 12:01am and finished at 3:10am local time
There is a DataSaveAll at 3:10 as well
The chore that finishes at 3:10 has process that do not take advantage of Parallel Interaction; lots of view creates and destroys
I am guessing that the problem relates to the processes constantly having to roll back and restart due to conflicts
A consultant pointed me to log4j.logger.TM1.Commit=DEBUG as a means of getting more information and I plan to do this overnight tonight, but I am concerned that this may come with an overhead
Any suggestions?
Happy to provide any more information as required
Hoping someone can help with an issue that I have not come across before
A long running chore has processes that seem to be restarting, the chore is only scheduled once at 12:30am local time
I have attached an extract from the TM1Server log
Note that the process DIM_Build_Business_Unit_Grouping_Tenant runs at local time 12:30:02 AM, then at 3:09:54 AM and 3:36:17 AM before finishing at 4:42:29 AM
There is no information as to WHY this process restarted in the logs
The information I have provided is just an extract, I have more information that I can provide but the log file is large.
Other information:
There is another chore running just prior to this that started at 12:01am and finished at 3:10am local time
There is a DataSaveAll at 3:10 as well
The chore that finishes at 3:10 has process that do not take advantage of Parallel Interaction; lots of view creates and destroys
I am guessing that the problem relates to the processes constantly having to roll back and restart due to conflicts
A consultant pointed me to log4j.logger.TM1.Commit=DEBUG as a means of getting more information and I plan to do this overnight tonight, but I am concerned that this may come with an overhead
Any suggestions?
Happy to provide any more information as required