DSXchange

chulett wrote:Are you sure it is actually locked? "Cannot get exclusive access to job" doesn't necessarily mean locked, but could mean running or perhaps even someone browing the job log. Or did it specifically tell you it was locked?

Job was not running and nobody was log in when the error arose
And what is worse, it has been like this for days

Can you use ps -ef|grep java and find the job and PID?

Here is an example of my output from the command:

$ ps -ef|grep java
root 245944 1 0 Apr 19 - 2:35 /opt/app/IBM/InformationServer/ASBNode/bin/RunAgent -Xbootcl.....

245944 is the PID.

Please answer the question - do your error messages actually use the word 'locked' or not?

chulett wrote:Please answer the question - do your error messages actually use the word 'locked' or not?

Actually message is

Cannot get exclusive access to log for job JS_ATN

You should have mentioned that full message in the first post, would have saved some chasing of the wild gooses.

There's no lock here to find but someone or something accessing the job's log. Query the repository to get the job's internal number and then try using the Director's 'Cleanup Resources' option to see if there is any entry that mentions RT_LOGnnn where nnn is that number.

If it is disabled, you should be able to go to the Administrator, select that Project and enable the option that is something like (off the top of my head) 'Enable job cleanup from Director'.

chulett wrote:You should have mentioned that full message in the first post, would have saved some chasing of the wild gooses.

There's no lock here to find but someone or something accessing the job's log. Query the repository to get the job's internal number and then try using the Director's 'Cleanup Resources' option to see if there is any entry that mentions RT_LOGnnn where nnn is that number.

Hi, coming back with the same problem

I enabled job administration in Director

Get into the job, Cleanup Resources option, and in both sections, picked 'show by job'. Nothing showed up
Then selected show all, nothing where my job number is involved

I also clear status file for the job (in the DS.TOOLS option), but also did not help

I dont know what else to do....

manuel.gomez,

Which version of IIS are you running? 8.1?

DataStage logging was changed at release 8.1 to save the logs in the operational repository- xmeta -, so local project level log files (RT_LOGxxx) are not used anymore unless you manually change the default setting to save the logs in files as in previous DS versions. So probably you won't see any entry that mention RT_LOGnnn

Just curious .. are you able to see the new logs after the job ran each day?

JRodriguez wrote: Which version of IIS are you running? 8.1?

8.0

Just curious .. are you able to see the new logs after the job ran each day?

Yes, I can see all executions carried out

manuel.gomez,

Lock details are found in XMETA.XMETALOCKINFO table, but executing the cleanup_abandoned_locks.bat script should remove any entry in that table ... and you done that ....

Another posibility is that the script failed when you ran it ....the script just return to the command line and does not show any messages

Would you mind trying again ..execute the script while logged in as root and provide the IIS admin user/password when prompted ...

If that doesn't work ask your DBA to remove any entry in XMETA.XMETALOCKINFO table

And let us know

What does your webconsole say?

Sainath.Srinivasan wrote:What does your webconsole say?

absolutely nothing

As far as I know, correct me if I am wrong, the only thing I can manage from web console is opened sessions. No sessions are opened but still the job is locked

Did you trying bouncing DS ?

Sainath.Srinivasan wrote:Did you trying bouncing DS ?

this was suggested earlier before

as said, this is a production server, If I do have any problem when restarting datastage, this lock will be just the smallest thing to think about

JRodriguez wrote:Lock details are found in XMETA.XMETALOCKINFO table

As noted earlier and in spite of the subject, this is not a job lock issue. The problematic message is simply "Cannot get exclusive access to log for job JS_ATN".