Job Aborting with Runtime Stack Overflow
Posted: Wed Sep 28, 2005 4:09 am
I have a job sequence that has start loop - end loop activities built in and am having a problem that is happening consistently. After 256 iterations of the loop the job sequence falls over with the error shown below:
From previous run
DataStage Job 72 Phantom 12977
Program "JOB.223462050.DT.1377734115": Line 2375, Runtime stack overflow.
Attempting to Cleanup after ABORT raised in stage ExtractFundMeasurement.ST_PPSA.JobControl
DataStage Phantom Aborting with @ABORT.CODE = 3
This information is added to the director log after I reset the aborted job sequence. There is no other helpful information in the log apart from Job ExtractFundMeasurement.ST_PPSA aborted.
The number 257 scared me a little as it is too close to the binary number 256 but I have created a simple loop version that process past this point.
Can anyone help me with what the above error means as I am out of ideas for the moment - is it to do with resources ?
A little more about the job sequence -
A Sybase Server is connected to and data are written back to a file.
A Basic routine checks the content of the data file and either
(1) FTP's the data file to another server
(2) Update a SQL Server setting a flag that no data were found.
Data files can contain many thousands of rows.
After a file is FTP'ed it is removed from the file system.
For each loop iteration two DSLogInfo messages are written to the director log for each iteration.
There are no hash files.
It is not a data issue or failure with one particular item in the loop - each time this code is run a different item is at iteration 257.
From previous run
DataStage Job 72 Phantom 12977
Program "JOB.223462050.DT.1377734115": Line 2375, Runtime stack overflow.
Attempting to Cleanup after ABORT raised in stage ExtractFundMeasurement.ST_PPSA.JobControl
DataStage Phantom Aborting with @ABORT.CODE = 3
This information is added to the director log after I reset the aborted job sequence. There is no other helpful information in the log apart from Job ExtractFundMeasurement.ST_PPSA aborted.
The number 257 scared me a little as it is too close to the binary number 256 but I have created a simple loop version that process past this point.
Can anyone help me with what the above error means as I am out of ideas for the moment - is it to do with resources ?
A little more about the job sequence -
A Sybase Server is connected to and data are written back to a file.
A Basic routine checks the content of the data file and either
(1) FTP's the data file to another server
(2) Update a SQL Server setting a flag that no data were found.
Data files can contain many thousands of rows.
After a file is FTP'ed it is removed from the file system.
For each loop iteration two DSLogInfo messages are written to the director log for each iteration.
There are no hash files.
It is not a data issue or failure with one particular item in the loop - each time this code is run a different item is at iteration 257.