DSXchange

Posted: **Fri Nov 21, 2014 1:49 pm**

How many users do you have on the system at once?

Here is a technote link (desc: "DataStage: Problems with 40 or more simultaneous users"). I am curious if this is the same error you are getting.

http://www-01.ibm.com/support/docview.w ... wg21318249

Posted: **Fri Nov 21, 2014 2:03 pm**

FWIW, that's exactly the situation where I've seen that error before back in the 7.x world.

Posted: **Fri Nov 21, 2014 8:43 pm**

Hi

Thanks. already I have enabled deadlock services and also I have noticed that. If some one open designer and start compile one job and then open Director then immediately the same user getting "Access Denied - Project Lock issue" issue.

But I am seeing only one connection for that user. Again I have to manually unlock this user using user no.

Is this any issue with repository?

Device.... Inode.... Netnode Userno Lmode Pid Login Id Item-ID.............
2424836 242947 0 62024 71 RL 56033372 aaa aa_project&!DS.ADMIN!&

/opt/IBM/InformationServer/Server/DSEngine - dcdedsa1 $ ps -ef |grep 56033372
aaa 56033372 39583746 0 16:18:35 - 0:01 dsapi_slave 7 6 0 4

Thanks
man

Posted: **Sat Nov 22, 2014 7:34 am**

That sounds very unusual. Try contacting Support about resolving it.

Posted: **Mon Nov 24, 2014 8:36 am**

try running smat -a after sourcing dsenv. Should get some idea on what may be the problem, but based on the output you have posted, it does look unusual.

This will also show uvconfig parameters currently in use.

Posted: **Mon Nov 24, 2014 1:15 pm**

Thanks Lot.
smat -a is AIX level monitor commend .

Thanks
Man

Posted: **Mon Nov 24, 2014 4:02 pm**

The aa_project&!DS.ADMIN!& is a shared lock only, to signal administrator tools that they don't have exclusive access to the project. This kind of lock will not exhibit the symptoms you have described.

I'm not sure what the problem is here. It might be that you only have a single licence for the C++ compiler, though why compiling should prevent a new client connection is beyond me. Might be a glitch that only your official support provider can resolve.

Posted: **Tue Nov 25, 2014 12:26 pm**

Hi

I have fixed this issue. I have restarted DS9.1 services and then it got solved.

FYI :

1) I didn't change UVCONFIG file
2) I have enabled deadlock service with following way.

/opt/IBM/InformationServer/Server/DSEngine $ more dsdlockd.config
start=1
timer=900
res=0
log=
recordlocks=0

Thank you all for your help.

Thanks
Man