Abort Code

EJRoufs · Post by **EJRoufs** » Thu Jul 29, 2004 7:55 am

I am pulling data off of a SQL Server database, writing it to a temporary file, then trying to summarize that file. I am getting an error when trying to summarize:

DataStage Job 200 Phantom 2456
Program "DSP.ActiveRun": Line 51, Exception raised in GCI subroutine:
Access violation.
Attempting to Cleanup after ABORT raised in stage PullSPC1998SS..SumHistory
DataStage Phantom Aborting with @ABORT.CODE = 3

My first question is, why is my program blowing up? I am looking into this at the moment.... hoping i can figure that out quickly on my own. My second question, maybe more of my question i'm hoping to get answered here in the forum.... where is a good source of documentation? Like, where do i find out what "ABORT.CODE = 3" is telling me? The help built into DataStage doesn't seem to have the answer, nor does the documentation that came with the install. Is there a good place to search for this type of information?

Thanks for any help.

chucksmith · Post by **chucksmith** » Thu Jul 29, 2004 8:37 am

Could you have mistyped the name of a function in a derivation or routine, or have an incorrect argument list in a call?

EJRoufs · Post by **EJRoufs** » Thu Jul 29, 2004 8:44 am

chucksmith wrote:Could you have mistyped the name of a function in a derivation or routine, or have an incorrect argument list in a call?

It's possible; i'll double-check that. I wouldn't think so in this case, though. I had the entire routine working fine in DB2. All i did was switch the input to a SQL Server table instead, with the same set up. And that part works fine. It doesn't blow up until it gets about half way thru loading the records to the Summing step, which is identical to the Summing step i used with my DB2 read.

chulett · Post by **chulett** » Thu Jul 29, 2004 8:46 am

After it aborts, have you tried Resetting the job? If you do, is there anything in the log labelled 'From previous run'? This can give more clues as to the cause of the abort.

EJRoufs · Post by **EJRoufs** » Thu Jul 29, 2004 8:53 am

chulett wrote:After it aborts, have you tried Resetting the job? If you do, is there anything in the log labelled 'From previous run'? This can give more clues as to the cause of the abort.

I just reset it, but not getting any more helpful information. I basically have 2 million records i'm trying to sum down. It sends about 1.25 million of those records to the Sum step when it blows.

chulett · Post by **chulett** » Thu Jul 29, 2004 8:59 am

Probably memory / resource related. There are definitely limits to the amount of un-ordered data the Aggregator can handle on any given system, but I don't know of any hard-and-fast rules on how to determine what that limit might be.

Any chance you can sort the incoming data to support your aggegation? That would help the Aggregator out tremendously if you could. Make sure you tell it the 'sort order' of the incoming data - and don't lie!

It will blow up in a different way if you do...

EJRoufs · Post by **EJRoufs** » Thu Jul 29, 2004 9:14 am

chulett wrote:Probably memory / resource related. There are definitely limits to the amount of un-ordered data the Aggregator can handle on any given system, but I don't know of any hard-and-fast rules on how to determine what that limit might be.

Si. I believe you are correct. Before i was pulling in a month at a time and all was just peachy. Now i am pulling in a year at a time. The smaller amounts seem to work just fine. Thanks!

Anybody have any ideas how to determine my limits, or how to adjust my limits to handle more?