Dimension Update Error : TM1.Lock.CriticalSection

[SBK88]

Hello All,

Need your help guyz,

I was updating a diminsion. ( Copied all the updated related objects from Production environment to UAT Environmant, like process and the respective dimension, subsets and attributes).

While running the TI in UAT environment I am getting following error in message logs : (sample of it I have pasted below)

7936 [] DEBUG 2015-07-14 10:01:35.044 TM1.Lock Requesting Lock type Dimension 0x0000000001472E10(0x000000000144B058), Mode 1, Commit Log 0x00000000085E3980, Module ..\tm1_r7s\ColIterator.cpp, Line 393
7936 [] DEBUG 2015-07-14 10:01:35.044 TM1.Lock.CriticalSection Entering critical section: 0000000000FC1900. Recursion Count 0
7936 [] DEBUG 2015-07-14 10:01:35.044 TM1.Lock Adding 7936 to current copy holders of 0x0000000001472E10
7936 [] DEBUG 2015-07-14 10:01:35.044 TM1.Lock.CriticalSection Leaving critical section: 0000000000FC1900. Recursion Count 1
7936 [] DEBUG 2015-07-14 10:01:35.044 TM1.Lock Lock 0x0000000001472E10(0x000000000144B058) granted, Mode 1, Name ADM Change, Type 4, Module ..\tm1_r7s\ColIterator.cpp, Line 393
7936 [] DEBUG 2015-07-14 10:01:35.044 TM1.Lock Requesting Lock type Dimension 0x0000000001470210(0x0000000001449858), Mode 1, Commit Log 0x00000000085E3980, Module ..\tm1_r7s\ColIterator.cpp, Line 393
7936 [] DEBUG 2015-07-14 10:01:35.044 TM1.Lock.CriticalSection Entering critical section: 0000000000FC1840. Recursion Count 0

I have no idea of this , encounter this error for the first time.

Kindly help.
is there anything that I am missing or what?

[declanr]

DEBUG messages are a very detailed setting of what sort of message you want to receive in the logs (e.g. you can set it to only tell you about errors or you can get it to tell you about everything - everything is the debug setting.)

Are you actually seeing any issues? Like the dimension not updating as expected or are you just worried by the messages in the log?

P.S. you normally have to explicitly turn on DEBUG logging and I would only use it on very rare occasions as it will produce a LOT of data; most of which is completely useless. It looks like you have debug logging set for Locks; I would ask your other devs/admins if someone set it for a specific reason with a view to turning it back off again ASAP.

[SBK88]

I am worried about the process, it doenst get executed.

Logs I will change, but first I want to make sure the process should run successfully.

Thanks,

[tomok]

I am worried about the process, it doenst get executed.

Forgetting about the messages in the tm1server.log file, what error messages are in the specific error log file for the TI process? That should tell you why it isn't working.