TM1 Forum

Hi All,

I have recently run a process that updates the hierarchies in our our reporting cube and have noticed that when a single user tries to read data from the cube
it crashs the server. Currently using 9.1 SP3. The TI process deletes and rebuilds the hierarchy. I am guessing that when the user tries to read data from the
cube, TM1 has a fit cause it cannot locate the data cause the hierarchy does not exist/in the process of being rebuilt. This is when the server crashes.

What should i do to get around this? Obvious answers would be to run it outside business hours. Should i build a security process to LOCK users from reading the cube
while the process takes place??? Will this prevent this sort of thing from happening?

Cheers

Zark

Hi Zark, welcome to the forum.

There's no way that it should crash. When TI rebuilds a dimension it works on a clone copy, then when it is finished it replaces the original dimension with the updated one. The switch over time should be a matter of nanoseconds.

If you can reliably replicate this problem I suggest you raise it with IBM as a bug. The worst you should get is a hang while the TI process finishes working with the cube.

Have you taken a look in the logs, particularly tm1server.log? It might give you an indication of what's happening.

Martin

if a user's view is setup against elements that may not always exist after a dimension rebuild then that may explain it. i've never seen it crash a server but i have seen it stop users opening a cube when the default has been affected. likewise if the view is saved with any user-defined consolidations that may throw some issues up.

Hi Guys,

Thanks Steve and Martain. I had a look at the log and there appears to be no error. The last process that i ran when it crashed was in the log file:TM1.Process Process "dimension build - accounts" finished executing normally, then TM1 rebooted itself. When I spoke to the client, she mentioned that she was opening up the accounts dimension subset editor and then tm1 just hung. This was at the exact time i was running the hierarchy update process for this dimension. This is not the first time this has happened so b4 i ran the hierarchy updates, I emailed the tm1 community and then disconnected all the current users and then ran the process while watching TOP to see whether anyone would pop in ( someone did) , and then BAM! TM1 down!

Maybe this is a bug? To get around this should I LOCK users from this dimension b4 i run the process? I suppose I could test this just wondered what your thoughts are on this??

Cheers

Zark

You could try to create some workarounds like locking the dimension I guess, but the fact is this shouldn't be happening.

If you can reliably replicate the problem (and it sounds like you can) then I suggest you get the latest hotfix for the version you're running and if that still doesn't fix it, submit it to IBM for fixing.

Martin

Just want to point out that you are on 9.1 SP3, the early 9.1s were poor to say the least, suggest you get all SPs and HFs to take you onto the highest version within 9.1 if possible. This ought / might clear your issue.
Cheers