Page 1 of 1

Job geting hanged

Posted: Thu Sep 06, 2007 6:55 am
by ramank1981
Hi ,
I am facing a strange problem.
I am running one job with sequential file as source and Db2 as target with some transformations in between.

Problem is that sometimes the job runs fine and populates data in target table, but on other day the same job gets hanged and keeps on runing until i go and stop from the director.

We are facing this isse since long time.

Re: Job geting hanged

Posted: Thu Sep 06, 2007 7:41 am
by Ultramundane
ramank1981 wrote:Hi ,
I am facing a strange problem.
I am running one job with sequential file as source and Db2 as target with some transformations in between.

Problem is that sometimes the job runs fine and populates data in target table, but on other day the same job gets hanged and keeps on runing until i go and stop from the director.

We are facing this isse since long time.
What OS and version? Did you make sure that nothing was hung in DB2? What step was the job on when it hung?

Posted: Thu Sep 06, 2007 4:01 pm
by ray.wurlod
Did you make sure that nothing was locked in DB2?

Posted: Thu Sep 06, 2007 10:30 pm
by ramank1981
I checked the DB2 stage, there is no hung process of DB2.
Stange part is that we ran the same job with same source , same target 2 days back and the job was completed in few seconds.
But now the job is hanging ...

Posted: Thu Sep 06, 2007 10:48 pm
by ray.wurlod
Wrap your job design in

Code: Select all

 tags so we can see it properly.

Add Peek stages on relevant links so you can truly verify where data are and are not flowing.

And you need to check the DB2 database (not the DB2 stage) to determine whether anything is locked.  Are you, for example, updating one or both of the tables that provide input to the Join stage?

Posted: Fri Sep 07, 2007 7:47 am
by Ultramundane
ramank1981 wrote:I checked the DB2 stage, there is no hung process of DB2.
Stange part is that we ran the same job with same source , same target 2 days back and the job was completed in few seconds.
But now the job is hanging ...
What OS and version? Just curious, because AIX has a patch to fix fifo thread intermittent hangs caused by a timing issue. This caused us big problems.

Posted: Fri Sep 07, 2007 8:21 am
by rajendharreddy
One thing you can try is, drop the table and recreate the table with proper table space. Thanks..

Posted: Mon Sep 10, 2007 8:33 pm
by dspxguy
Ultramundane wrote:
ramank1981 wrote:I checked the DB2 stage, there is no hung process of DB2.
Stange part is that we ran the same job with same source , same target 2 days back and the job was completed in few seconds.
But now the job is hanging ...
What OS and version? Just curious, because AIX has a patch to fix fifo thread intermittent hangs caused by a timing issue. This caused us big problems.
Hi, can you please explain the problems you faced and how did you resolve them, what version and o/s you have?
Please let me know, Thanks

Problem is still there..not resolved.

Posted: Wed Sep 12, 2007 5:09 am
by ramank1981
we are using AIX 5.3. it still seems like a resource problem, no further clue.

Posted: Wed Sep 12, 2007 5:14 am
by Raghavendra
can you please check if your /tmp directory is filled.
And also check for &PH& directory.

Re: Problem is still there..not resolved.

Posted: Wed Sep 12, 2007 7:41 am
by Ultramundane
ramank1981 wrote:we are using AIX 5.3. it still seems like a resource problem, no further clue.
You could be running into the fifo_open problem. This caused us a lot of job hangs. There is patch for the AIX kernel to address this issue. The patch is: IY86253

I think you can google the patch.

Posted: Wed Sep 12, 2007 10:27 pm
by ramank1981
I had earlier cleared the &PH& , but the job was still hanging.
I have asked AIX admin for the patch IY86253, waiting for him to respond.

Posted: Wed Oct 03, 2007 10:44 pm
by ramank1981
It seems we finally found the root cause of the problem. One of the routine was creating the bottle neck. After we implemented the same thing with differnent logic, the jobs are running fine. :D

Thanks to all of you for giving inputs.