Running state
Moderators: chulett, rschirm, roy
Running state
Hi everyone,
I performed a job with some transformations and some stages.when i compile and run the job ,its in running state showing all yellow and blue lines.It is in the running state only not getting the result, so finally i aborted and ran the job again but still the same process i.e. in running state only.when i try to run a different job its working fine but having this issue only with this job.can anyone tell me what might be the issue?
thanks in advance
I performed a job with some transformations and some stages.when i compile and run the job ,its in running state showing all yellow and blue lines.It is in the running state only not getting the result, so finally i aborted and ran the job again but still the same process i.e. in running state only.when i try to run a different job its working fine but having this issue only with this job.can anyone tell me what might be the issue?
thanks in advance
Could you narrow down the "some transformations and some stages" part, since that is most likely where your error is happening.
Make a copy of your job with just the input stages and put in dummy output stages (sequential files going to "/dev/null") and see if the job hangs. If not, the problem is in your output stage(s).
Make a copy of your job with just the input stages and put in dummy output stages (sequential files going to "/dev/null") and see if the job hangs. If not, the problem is in your output stage(s).
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 35
- Joined: Wed Oct 06, 2010 11:24 am
Correct...as metioned in his earlier post that he forcibly stopped his job...sometimes when you forcibly stop tour job...your target table in database get locked or it will show used by another user....so ask your DBA the state of your target table....or just for check creat a copy of your job and replace orignal target table with a test target table...if it works ...you need to contact your DBA or wait for the default time of unlocking the tables as set by your DBA.ray.wurlod wrote:The problem is definitely in the database. Whether or not you involve your DBA depends entirely on how important solving the problem is to you. ...
Pacific