DSXchange

I am facing an issue of the jobs getting aborted abruptly(No message of Fatal or warning found in Director log and log is incomplete). When the job is restarted it is showing the following error message:

Error setting up internal communications (fifo RT_SCTEMP/BIW_Dimen_Vehicle_Vehicle_01_SIT1.fifo
LOCKED STATUS () -1); file is locked

Moreover, if I want to compile the job it is giving compilation error:

Cannot get exclusive acces to job. Job may be monitored

Have to close the director log to release the job lock/compile the job.
What could be reason for the abrupt abortion and job lock. How to avoid this?

parag.s.27 wrote:I am facing an issue of the jobs getting aborted abruptly(No message of Fatal or warning found in Director log and log is incomplete). When the job is restarted it is showing the following error message:

Error setting up internal communications (fifo RT_SCTEMP/BIW_Dimen_Vehicle_Vehicle_01_SIT1.fifo
LOCKED STATUS () -1); file is locked

Moreover, if I want to compile the job it is giving compilation error:

Cannot get exclusive acces to job. Job may be monitored

Have to close the director log to release the job lock/compile the job.
What could be reason for the abrupt abortion and job lock. How to avoid this?

Were you able to resolve the issue? I have exactly same problem?

If you stop the job and check the directory, is the fifo file still there? If so, delete it. Also, are you using BASIC stages in the PX job?

anu123 wrote: Were you able to resolve the issue? I have exactly same problem?

Which issue you are talking about?

I am facing an issue of the jobs getting aborted abruptly(No message of Fatal or warning found in Director log and log is incomplete).

or

Error setting up internal communications (fifo RT_SCTEMP/BIW_Dimen_Vehicle_Vehicle_01_SIT1.fifo
LOCKED STATUS () -1); file is locked

ArndW wrote:If you stop the job and check the directory, is the fifo file still there? If so, delete it. Also, are you using BASIC stages in the PX job? ...

I am not using any BASIC stages in my PX job. My job has errored out. I am not sure how to check 'fifo' file?

thanks anyway.

priyadarshikunal wrote:

anu123 wrote: Were you able to resolve the issue? I have exactly same problem?

Which issue you are talking about?

I am facing an issue of the jobs getting aborted abruptly(No message of Fatal or warning found in Director log and log is incomplete).

or

Error setting up internal communications (fifo RT_SCTEMP/BIW_Dimen_Vehicle_Vehicle_01_SIT1.fifo
LOCKED STATUS () -1); file is locked

Sorry for the confusin. I was talking about below error.
Error setting up internal communications (fifo RT_SCTEMP/BIW_Dimen_Vehicle_Vehicle_01_SIT1.fifo
LOCKED STATUS () -1); file is locked

you need to unlock this job , before you recompile the job
there should be a process lock with name BIW_Dimen_Vehicle_Vehicle_01_SIT1.fifo

unlock this process and unlock the userno

UNLOCK USER <nnnn> ALL

Not necessarily the case in version 8.

Using Director, release all locks n the job then logout all processes in the job using Cleanup Resources.

ray.wurlod wrote:Not necessarily the case in version 8.

Using Director, release all locks n the job then logout all processes in the job using Cleanup Resources. ...

Thanks Ray.

I tried to 'clean up resource'. I got below error.

ERROR: Cannot find any process numbers for stages in job 'Job Name'

Moreover, if I want to compile the job it is giving compilation error:

Cannot get exclusive acces to job. Job may be monitored

When I am facing this error, I had tried to by copying the job and saving it with different name.. it was working...

you can try by stopping the DSENGINE and starting it again so that the above mentioned error may not occur..

I am also having jobs with the same error.

anu123 wrote:ERROR: Cannot find any process numbers for stages in job 'Job Name'

You got this when in Cleanup Resources? If it was right when it started, it can be ignored - continue on, switch it to all processes and find your culprit.

Hi,
I am also getting the same error and i tried the solution given above still i am facing the same problem and i could not identify the fifo location. Could you please help me out. I tried to rename the job also but still facing the issue.

Can any one help me out why the issue is coming in datastage?

Thank you,
Senthur

Please start a new post when you have a problem, that way we know all of your particulars and you can post your specific error messages rather than saying it's "the same" as someone else's error.

If you feel it would help, post a link back to this topic when you do.