TM1.Lock.Exception Throwing IXConflict on object }DimensionProperties

Post Reply
User avatar
Steve Rowe
Site Admin
Posts: 2410
Joined: Wed May 14, 2008 4:25 pm
OLAP Product: TM1
Version: TM1 v6,v7,v8,v9,v10,v11+PAW
Excel Version: Nearly all of them

TM1.Lock.Exception Throwing IXConflict on object }DimensionProperties

Post by Steve Rowe »

Hi,
Seen on version 2.0.9.15 (developed on this release so I can't tell if this is new).

Have a muti-threaded load routine that works exactly as intended, except first use after a server restart.

After a server restart the first call to the job that spawns all the independent RunProcess loads, gets hit with a lock and rollback as below.

17696 [a7] DEBUG 2023-03-14 09:05:08.572 TM1.Lock.Exception Throwing IXConflict on object }DimensionProperties
17696 [a7] DEBUG 2023-03-14 09:05:08.572 TM1.Lock.Exception CommitActionLog::Rollback: Called for thread '17696' of user 'R*ChoreName' executing request 'POST /api/v1/Processes('JobName')/tm1.ExecuteWithReturn'.

This appears to happen after all the independent load threads have been launched, probably at the commit stage of the TI. The rollback and relaunch results in twice as many jobs being launched, with resulting havoc....

I’ve been through the script with a fine tooth comb and the closest suspect I have to something that could cause a problem is a set getting created. I don’t believe this enough on it’s own to cause a problem, particularly because it works properly the rest of the time.

This reminds me of a bug from way back where we needed to use AddCubeDependancy to create the relationships between ruled cubes and attributes cubes, as they were skipped over on start-up. This also used to block multi-threaded activity.

There is no mention in the logs of anything being created at the point of the lock. (Any ideas of what I could turn up in the log properties here?).

I’m just going to write a job that creates and deletes a sub against all the dimensions at the top of the job and see if this resolves. This is a bit blunt and I am wondering if anyone has hit this before or has ideas on how to narrow down where the issue is occurring.

Just to be clear though, the multi-threading works perfectly except on first use. I don’t believe there is a basic issue with the build.

TIA for any ideas

Cheers,
Technical Director
www.infocat.co.uk
lotsaram
MVP
Posts: 3651
Joined: Fri Mar 13, 2009 11:14 am
OLAP Product: TableManager1
Version: PA 2.0.x
Excel Version: Office 365
Location: Switzerland

Re: TM1.Lock.Exception Throwing IXConflict on object }DimensionProperties

Post by lotsaram »

It might be related to MUN generation or the initial lock the first time a dimension is queried.

After startup try looping through all dimensions and just doing a sEle = DIMIX(sDim, 1) within the loop (nothing else) then after the loop run RefreshMdxHierarchy.

Doing that before the load process may resolve the locking.
Please place all requests for help in a public thread. I will not answer PMs requesting assistance.
User avatar
Steve Rowe
Site Admin
Posts: 2410
Joined: Wed May 14, 2008 4:25 pm
OLAP Product: TM1
Version: TM1 v6,v7,v8,v9,v10,v11+PAW
Excel Version: Nearly all of them

Re: TM1.Lock.Exception Throwing IXConflict on object }DimensionProperties

Post by Steve Rowe »

Thanks, I'll give this a try, the build and destroy a sub versus all dimension didn't work. (I used static dims rather than MDX ones due to some issues with the naming of some views causing the MDX to fail).
Technical Director
www.infocat.co.uk
User avatar
Steve Rowe
Site Admin
Posts: 2410
Joined: Wed May 14, 2008 4:25 pm
OLAP Product: TM1
Version: TM1 v6,v7,v8,v9,v10,v11+PAW
Excel Version: Nearly all of them

Re: TM1.Lock.Exception Throwing IXConflict on object }DimensionProperties

Post by Steve Rowe »

Hi,
Just to close this one out, the addition of RefreshMdxHierarchy appeared to resolve the issue.
Thanks lotsaram, appreciated.
Cheers,
Technical Director
www.infocat.co.uk
Post Reply