Job locked

[Nagaraj]

My Job is locked because the session died suddenly.

things which i have tried.

Find the job locked by the item_id which is nothing but the job name:
Take the correspindng userno of the Item_id
Execute the command UNLOCK USER 56986(item_id) OR unlock user 56986 ALL


Other Option.
Go to Director Tools then click Clear the Job Resources optionthere u note the PID Number 1.Go to Administrator 2.Properties3.Command 4.type ds.tools5. u will get options6.select 4th option6.select the 6th option7.Then enter the PID Number


In version 8 the better mechanism is to disconnect the session using Web Console for Information Server. When you open the job you get a dialog showing the owner of the lock. That's the session ID that you need to disconnect.


i dont seem to find the session id correcponding to the joc lock session id.

i even cleared all the locks on the server.
and guess what last but not the least i recycled the engine.

any ideas why the job is still locked.

can i do something at the XMETA level?

[ray.wurlod]

You can, but I'm surprised you didn't find the session when managing sessions through the Web Console for Information Server. The session ID is the long hex number reported on the "job locked" message in Designer or Director.

The locks in XMETA are stored in a table called XMETALOCKINFO - you can delete the appropriate row from this table. I suggest that you describe the table first, to get an idea of the column names, so that you can specify the correct row in a WHERE clause.

[greggknight]

Another thing I might recommend
The deadlock daemon can be started to release locks and abandoned shared memory segments for processes that are terminated via the UNIX kill command or abnormally due to an unforeseen event.

To start the dslockd process edit $DSHOME/dsdlockd.config and set the start flag to 1. The daemon will start automatically the next time the DataStage server is started

Enter the time interval, in seconds, that the daemon should wait before rechecking for deadlock conditions. The default is 900 seconds, but you may want to select a smaller interval like 300 seconds.
After changing the start value restart the engine so the damon will run.

default values
start=0
timer=900
res=0
log=

[Nagaraj]

Finally table called XMETALOCKINFO helped me unlock.

thanks all for you valuable inputs i am documenting this thread

[abc123]

Two questions:

1) How do you unlock through IBM Information Server Web Console? I see 'Domain Management','Log Management' and 'Scheduling Management' under the Administration tab. How do you pick the job or see what is unlocked?

2) What steps did you use to unlock through the XMETALOCKINFO table?

[greggknight]

Personally, Unless you are quite familiar with the xmeta database, I would not mess with it. You could cause more problems then you want. Anytime you make back door changes to anything nothing good comes of it.
Thats why the provisions are there to handle this issue from the front door.
But, it is your system. Bear in mind that all teirs use that database.

I do it the way I discribed above. takes 2 min to do. But I guess I just like the old way of doing things.

You could write a batch job to issue the commands and use parameters
One gets the list of the locks and the other removes them based on the parameters.

[abc123]

I didn't get an answer to either of my questions though.

[pandeesh]

I didn't get an answer to either of my questions though.

For your second question:

You need to find out the specific entry in XMETALOCKINFO table and delete that entry,

[ray.wurlod]

You can disconnect a session in Session Management. This will clear all locks owned by that session.

[Nagaraj]

This time same issue, it didnt show up in the web console, but it showed up in XMETALOCK table.