DSXchange

Dear All,

When I try to open DataStage Designer or Director, I get this message :

ACCESS DENIED: Project currently locked. The project is currently locked by Administrator. Try again or see your Administrator

I've been searching about this message..

I ran ps -ef | grep dscs | wc -l
and the result is 70... *note : there's only about 10 people accessing the DataStage

Here I post some of the result of ps -ef | grep dsapi

dsadm 9117 9116 0 Apr 07 ? 1:30 dsapi_slave 8 7 0
dsadm 24490 24489 0 Apr 08 ? 0:49 dsapi_slave 8 7 0
dsadm 21052 21051 0 Apr 11 ? 0:08 dsapi_slave 8 7 0
dsadm 6834 6833 0 May 13 ? 0:01 dsapi_slave 8 7 0
dsadm 26880 26879 0 May 12 ? 0:03 dsapi_slave 8 7 0
dsadm 12346 12345 0 Apr 10 ? 0:00 dsapi_slave 8 7 0
dsadm 23086 23085 0 Apr 08 ? 0:04 dsapi_slave 8 7 0
dsadm 6824 6823 0 May 13 ? 0:04 dsapi_slave 8 7 0
dsadm 543 542 0 May 06 ? 0:00 dsapi_slave 8 7 0
dsadm 2455 2454 0 Apr 08 ? 0:45 dsapi_slave 8 7 0
dsadm 16610 16609 0 Apr 09 ? 0:09 dsapi_slave 8 7 0
dsadm 6202 6201 0 Apr 17 ? 0:01 dsapi_slave 8 7 0
dsadm 17592 17591 0 Apr 09 ? 0:06 dsapi_slave 8 7 0
dsadm 928 927 0 Apr 10 ? 0:01 dsapi_slave 8 7 0
dsadm 3644 3643 0 May 07 ? 0:04 dsapi_slave 8 7 0
dsadm 21969 21968 0 13:53:02 ? 0:01 dsapi_slave 8 7 0

What i want to ask is...
Is it okay if i kill the dsapi_slave with the date 'May' or 'April'?
How to kill it?

and 1 more... can I start the deadlock daemon without restarting the Datastage?

Thanks,
Ratna

You can (as root or dsadm) start the dsdlockd process without restarting DataStage, from the $DSHOME directory. You can also get dsdlockd to perform just a single probe by adding a -p option to the command line. Try never to kill DataStage processes with kill -9 command. This is particularly true for parallel jobs, in which there can be myriad processes.

hiks.. i couldnt see your post ray...
i know you would say its worth it to be premium member... but i am just not in the able condition of subscribing to premium member

The important part of the post is visible, the rest you can use the documentation and the search facility to figure out.

Thx AndrW..
I'm just scared im missing something on Ray's post..

Not scared enough to get a premium membership, though

Search the forums for DS.TOOLS and use the 'logout' option there as 'dsadm' to clear those old pids. It's under '4' then '9' from what I recall.

Thanks chullet,

That 'logout option' in DS.TOOLS is the same with the Cleanup Resources in Datastage Director, right?

So nothings wrong is gonna happen on my datastage when i 'logout' the old pids, right?

Thanks alot everybody, for helping me...

Basically yes, the same. Only 'wrong' thing might be if you logged out the wrong PID, I suppose.

Recently, we met this issue as well.
And does it have certain relationship with the tunable paramter MFILES?
Pls guide me, thanks in advance.

Regards
Brian.

Recently, we met this issue as well.
And does it has certain relationship with the tunable paramter MFILES?
Pls guide me, thanks in advance.

Regards
Brian.

The MFILES setting in the UVCONFIG controls how many actual Hashed files are open at any time; this setting can seriously affect performance but has not direct impact on the problems described in this thread.

ArndW wrote:The MFILES setting in the UVCONFIG controls how many actual Hashed files are open at any time; this setting can seriously affect performance but has not direct impact on the problems described in this ...

Hi Arndw,

Thanks for your reply.
Currently, on our dev server, there is prompt message popped up, "ACCESS DENIED: Project currently locked. The project is currently locked by Administrator. Try again or see your Administrator", when someone tried to open client tool Designer.

The DS server is running on Linux Box.

So, do you think what kind of problem is to this issues?

Thanks in advance.
Brian

In the first reply on this thread, Ray detailed how to start the deadlock daemon. Do you have this running?

ArndW wrote:In the first reply on this thread, Ray detailed how to start the deadlock daemon. Do you have this running? ...

Hi ArndW,
Thanks for your reply.
The deadlock daemon process is not running on our dev env.
And I would appreciate it if you could elaborate what the deadlock daemon works for. Or tell me which document I could reference for deadlock daemon.
Thanks in advance.