TM1 Forum

I am running TM1 9.1 SP2 Update 3.

Can someone explain to me exactly how object locking in this version of TM1 works?

If two cubes share dimensions does cube1 lock when changes are made in cube 2? It seems from the testing that I have done that I am prevented from making changes to cube 1 while certains views (but not all views) are being calculated on cube 2.

I know from monitoring TM1top that I am having some issues with locking, but am having difficulty determining exactly what is causing the problem.

Thanks,
James

James,

Cognos didn't get the new locking model "right" until the Cognos branded 9.1 SP3. In SP2 U3 granular cube locking was not quite there yet.

Thanks for the reply. Can you explain how the locking is supposed to work?

I installed 9.1 SP3 U2 on my development instance yesterday and I'm still seeing some locks that I don't understand.

Thanks,
James

I would also love to know more about TM1's locking.....can anyone help?????

There is a lot regarding locking and it is different between version. Can you be a little more specific?

running TM1 9.1 SP2 update 3
if two cubes share the same dimensions how does the locking work?

Anyone correct me if I am wrong, but if you are updating the dimension you lock all cubes, but if you are updating cube 1 it does NOT affect cube 2.

What Eric says is correct for 9.1 SP3 (& U1, U2).

The new cube level locking model is only in effect from 9.1 SP3 onwards.

For 9.1 SP2 U3 both cubes will still lock if writing to one.

if you are updating a cube and that cube shares a dimension with another cube - how could you not lock both cubes?????

Not getting to deep in my answer, but it should suffice.

Because you are locking the intersection of a combination of elements within the dimensions of a cube and NOT the dimensions themselves. Each cube is its own object/independent table. Like I said before though if you are update a dimensions you will lock all of the cubes.