Save Data All

[JFerguson]

We have been running savedataall as a chore twice a day for years. Each data save has until recently taken seconds to complete. Now each data save takes between 2000 & 4000 seconds according to the message logs and consequently causes TM1 to be locked up for our users for 30 mins to an hour at a time. Because our users are worldwide, whatever time we schedule the saves there will be impact on some users. We have not changed our model to cause such an increase. But don't know if our Group IT shared service centre has made any changes to the infrastructure which may have caused this - they say not, but they don't know TM1.

Would you have an idea as to what could cause this increase in time and how we could possibly fix it?

Thanks...

[Martin Erlmoser]

maybe you can try to clean up your logdirectory ( change cfg to an empty one) and test it again

[John Hammond]

Check that you are not running 2 savedataall commands at exactly the same time so that they are continually competing for locks on the same object. Its possible if you duplicated a chore.

Other than that try using tm1top to see what is causing the locking contention.