Problem executing Server job

yaminids · Post by **yaminids** » Sun May 21, 2006 2:11 am

Hello friends,

I am running into issues while running a simple Server job.
The job inserts data into an Oracle table reading from a Seqeuntial File Stage.

SequentialFileStage==>Transsformer==>OCI9i Stage

When I tried to execute the job for the first time it did not insert any records ever after running for 3 hours. I got the following error when I tried to clear Job Resources after killing the job

ERROR: Cannot find any process numbers for stages in job TEMP_CORPFEED3

I am getting the same error when I tried to rename the file and execute it.

Did anyone face this problem before?
Any help would be highly appreciated

Thanks a bunch in advance
Yamini

ray.wurlod · Post by **ray.wurlod** » Sun May 21, 2006 6:54 am

Is there something else, perhaps another DataStage job, perhaps some other process. that has locked the Oracle table? Check with your DBA.

kris007 · Post by **kris007** » Sun May 21, 2006 9:53 am

As Ray mentioned check if the table is being locked by another process.

Also, try inserting, updating a record into that table manually from SQLplus or TOAD or whatever and see howlong does it take to insert/update a single row. The last time that happened to me, it was taking 10sec to insert a single row

and the job never ran completely. I had to kill it always not knowing the reason.

Then, the DBA had to analyze the table and then it ran fine. So, check for these and discuss it withyour DBA. I am pretty sure it is not as much a datastage issue as much as it is a database issue.

IHTH

ray.wurlod · Post by **ray.wurlod** » Sun May 21, 2006 2:36 pm

That error message can also occur if an attempt has been made to kill the job processes using operating system commands. There must be processes (resources) existing for Cleanup Resources to be able to work.

kumar_s · Post by **kumar_s** » Sun May 21, 2006 10:57 pm

Try to do export and import the same job. And make sure you dont get any warning or error during that process. This is to make sure you job design with the DS repository is ok.

yaminids · Post by **yaminids** » Mon May 22, 2006 12:56 am

Hello all,

Thanks a lot for your suggestions...
Analyzing the table did the trick

Yamini

kumar_s · Post by **kumar_s** » Mon May 22, 2006 7:58 am

So what was the action point taken to the table to make the job to perform well?

yaminids · Post by **yaminids** » Wed May 24, 2006 1:40 am

I have requested the DBA to Analyze the table and collect the Statistics

kumar_s · Post by **kumar_s** » Wed May 24, 2006 7:26 am

Based on the statistics,have you taken remidial action to improve the performance?

yaminids · Post by **yaminids** » Wed May 24, 2006 11:28 am

Apart from collecting the Statistics we did not take any action to solve the issue