TM1 Forum

I have a TI data load process that causes users to wait during integrated login. This situation is reflected in TM1Top in the following way:
USername: ???
State: Wait:IXCur (UserName) - (Client)
Function: SystemServerConnectIntegrate
Obj Lock Status: Client

This TI process does not create subsets, change view, does not touch control cubes and dimensions directly. It just operates with dimension elements and cube data. Can CubeSetLogChanges(vCube,0) drive such behavior?

We use 64x TM1 10.1.
Thanks.

4rtem wrote:Can CubeSetLogChanges(vCube,0) drive such behavior?

Yes.
And also metadata updates may be blocking.

It looks like the the TI process is touching the client objects. Are you doing anything with the TM1User() function or the }Clients dimension in the TI?

No operations with TM1USer() and }Clients dimension and any of control cubes/dimensions.
Statistic cubes are active on the server, maybe it is the source of locks...
I will turn it off tomorrow and check if it helps.

Hi 4rtem,

Just thought of checking with you how you resolved this issue. I am facing exactly the same issue on (10.2.2 FP5). I disabled the command that plays on cube logging. There is no commands that play on control objects. But, I am still getting the same locking contention.

Any help will be highly appreciated.

Dhims

Do not use CubeSetLogChanges.
If you want to turn on/off logging in the cube set the LOGGING property on the
}CubeProperties cube directly.
That worked for me.

That is only the old wisdom, isn't it? AFAIK this was sorted somewhere around 10.2.2 FP4+