Hello friends,
I have a shellscript which triggers DataStage job multiple times in a loop. In short, at the beginning the shellscript executes a PL/SQL procedure which generates some files. Then it triggers the DataStage sequence which in turn triggers the job to process the files. This process continues multiple times until the conditon of the loop is false (atleast 10 times per execution)
The problem is sometimes the status of the DataStage job shows 'Running' in Director even though the job is done (in Designer all the links turn Green). As a result the shellscript loop cannot trigger the job next time and the whole process freezes
I found the following sessions on the server the job froze last time.
dstage 26116 24880 99 21:34 ? 01:34:06 phantom DSD.RUN CNMR_RPT_001. 0/1/1/0/0
dstage 26129 26116 0 21:34 ? 00:00:00 [uvsh <defunct>]
dstage 26131 26116 0 21:34 ? 00:00:00 [uvsh <defunct>]
dstage 26463 26116 0 21:34 ? 00:00:00 [uvsh <defunct>]
dstage 26494 26116 0 21:34 ? 00:00:00 [uvsh <defunct>]
dstage 26497 26116 0 21:34 ? 00:00:00 [uvsh <defunct>]
dstage 26509 26116 0 21:34 ? 00:00:00 [uvsh <defunct>]
Can someone please help me in debugging the issue
Thanks a lot in advance
Yamini
Problem with long running DataStage job
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Make sure that the deadlock daemon (uvdlockd) is running.
Make sure that the job finishes reliably - even an after-job subroutine that performs a small innocuous task.
Make sure that the job finishes reliably - even an after-job subroutine that performs a small innocuous task.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
-
- Participant
- Posts: 15
- Joined: Tue Dec 13, 2005 12:38 am
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
The deadlock daemon is not governed by any environment variable.
Its auto-start is configured in a file called dsdlockd.config in the DataStage engine directory.
You can check to see whether it's running by looking for its process using UNIX commands.
Its auto-start is configured in a file called dsdlockd.config in the DataStage engine directory.
You can check to see whether it's running by looking for its process using UNIX commands.
Code: Select all
ps -ef | grep dsdlockd | grep -v grep
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.