Datastage server job locked

sujaoschin · Post by **sujaoschin** » Sun Aug 03, 2008 7:02 pm

I am unable to open certain jobs in Datastage server edition 8. I stopped and started the server and also tried to clean up the resources for unlocking the jobs in Director. Can anyone guide me thru the steps to be followed.

I am getting this below error

'Unable to open the job

The job 'ADDRESS_HASH' is locked by the user 'dsadm'
(Session ID - 10E0749C-0295-41B1-BD 12-F676A8FE6D61)

Do you want to continue and reopen the job in read-only mode?'

ray.wurlod · Post by **ray.wurlod** » Sun Aug 03, 2008 8:08 pm

Welcome aboard.

Check that no-one else has the job open in Designer or Director. If they have, get them to close it.

Open up the Information Server web console to the Session Management page and identify the session whose Session ID was given in the message. You can disconnect this session (at the risk of upsetting the user whose session it is - which is why you checked first).

sujaoschin · Post by **sujaoschin** » Sun Aug 03, 2008 8:27 pm

sujaoschin wrote:I am unable to open certain jobs in Datastage server edition 8. I stopped and started the server and also tried to clean up the resources for unlocking the jobs in Director. Can anyone guide me thru the steps to be followed.

I am getting this below error

'Unable to open the job

The job 'ADDRESS_HASH' is locked by the user 'dsadm'
(Session ID - 10E0749C-0295-41B1-BD 12-F676A8FE6D61)

Do you want to continue and reopen the job in read-only mode?'

Yes. I have checked expect me , no one has logged into the Datastage designer or Director.

sujaoschin · Post by **sujaoschin** » Mon Aug 04, 2008 12:39 am

Hi Ray,

As posted in the forum, I went and checked in the session Management --> Active sessions in IBM information server console, session ID I got while opening the job is not present. Is there any other way to unlock the jobs, Please advise.

ArndW · Post by **ArndW** » Mon Aug 04, 2008 1:21 am

That might mean you have orphaned processes and/or locks. I always recommend that the deadlock daemon is started in order to have an automated cleanup happen when processes are killed or stopped, you can read on how to do that in many places in this forum.

If your system is not busy with users, you can check to see which UNIX processes are running for that ID or enter into the DataStage TCL and type "PORT.STATUS" and "LIST.READU EVERY" to see which users are active in DataStage and which locks are actively being held.

sujaoschin · Post by **sujaoschin** » Mon Aug 04, 2008 5:37 pm

Hi,

I have changed the start=0 to start=1 in dsdlocked.config file in $dshome directory. still the job is getting locked. Please advise

ray.wurlod · Post by **ray.wurlod** » Mon Aug 04, 2008 5:40 pm

The deadlock daemon will not start automatically until DataStage is re-started.

The job may still lock. The deadlock daemon will clear that lock, but it may take quite some time - the daemon only wakes every 15 minutes (by default) and it usually requires two cycles to clear locks held by redundant processes.

You really should find out WHY this lock is happening.

sujaoschin · Post by **sujaoschin** » Mon Aug 04, 2008 8:05 pm

I stopped and re-started the server, but the jobs are still getting locked

dineshrk · Post by **dineshrk** » Tue Aug 05, 2008 10:01 am

sujaoschin wrote:I stopped and re-started the server, but the jobs are still getting locked

Please check if the process are running in the backgound. Use

ps -ef | grep username

to find the number of processes running and check if the job's one is also running. if so kill the process manually before re-staring the serer.

sujaoschin · Post by **sujaoschin** » Tue Aug 05, 2008 5:05 pm

Hi,,

When I used the below command , I got the below output

au02uap003btox2:/opt/IBM/InformationServer/Server/DSEngine$ps -ef| grep dsadm
dsadm 389222 794780 0 08:49:31 - 0:00 sshd: dsadm@pts/0
dsadm 458898 569458 0 08:59:08 - 0:00 dsapi_slave 7 6 0
dsadm 569458 1044508 0 08:59:08 - 0:00 dscs 4 0 0
dsadm 712790 1 3 14:50:04 - 17:38 /opt/IBM/InformationServer/Server/PXEngine/bin/resource_tracker
dsadm 749604 389222 0 08:49:31 pts/0 0:00 -ksh
root 794780 1597554 0 08:49:25 - 0:00 sshd: dsadm [priv]
dsadm 1261660 749604 1 09:02:43 pts/0 0:00 ps -ef

can you please advise me, what is the next step?

sujaoschin · Post by **sujaoschin** » Tue Aug 05, 2008 5:10 pm

Hi,,

When I used the below command , I got the below output

au02uap003btox2:/opt/IBM/InformationServer/Server/DSEngine$ps -ef| grep dsadm
dsadm 389222 794780 0 08:49:31 - 0:00 sshd: dsadm@pts/0
dsadm 458898 569458 0 08:59:08 - 0:00 dsapi_slave 7 6 0
dsadm 569458 1044508 0 08:59:08 - 0:00 dscs 4 0 0
dsadm 712790 1 3 14:50:04 - 17:38 /opt/IBM/InformationServer/Server/PXEngine/bin/resource_tracker
dsadm 749604 389222 0 08:49:31 pts/0 0:00 -ksh
root 794780 1597554 0 08:49:25 - 0:00 sshd: dsadm [priv]
dsadm 1261660 749604 1 09:02:43 pts/0 0:00 ps -ef

can you please advise me, what is the next step?

sujaoschin · Post by **sujaoschin** » Tue Aug 05, 2008 7:34 pm

I killed the process by PID and stopped and restarted the server. Still the job locks are not released. Please advise.

lstsaur · Post by **lstsaur** » Tue Aug 05, 2008 8:12 pm

Just delete all the rows in the XMETALOCKINFO table.

sujaoschin · Post by **sujaoschin** » Tue Aug 05, 2008 11:55 pm

Please let me where can I find this XMETALOCKINFO table.

sujaoschin · Post by **sujaoschin** » Wed Aug 06, 2008 12:19 am

I got it. I deleted all the rows from XMETALOCKINFO table. Now all the job locks got released.

Thanks a lot, lstsaur.

DSXchange

Datastage server job locked

Datastage server job locked

Re: Datastage server job locked