Aggregator stage error

snassimr · Post by **snassimr** » Thu Jun 30, 2005 1:11 am

I use Aggregator stage to remove duplicated rows on source
and it has return the following error :

DataStage Job 82 Phantom 2228
Program "DSP.ActiveRun": Line 51, Exception raised in GCI subroutine:
Access violation.
Attempting to Cleanup after ABORT raised in stage LoadDW_FACT_VISITS..AggregateVisits
DataStage Phantom Aborting with @ABORT.CODE = 3

Any ideas ?

ray.wurlod · Post by **ray.wurlod** » Thu Jun 30, 2005 1:15 am

What did you find when you searched the forum for this?

snassimr · Post by **snassimr** » Thu Jun 30, 2005 1:19 am

Nothing

snassimr · Post by **snassimr** » Thu Jun 30, 2005 1:53 am

The problem was solved by getting hint to aggregator about sorted data

chulett · Post by **chulett** » Thu Jun 30, 2005 6:20 am

You may have hit one of the Aggregators problem thresholds, like the number of records it can handle. Any chance you were sending it a very large number of (or some rather 'fat') records? At some point it will just fall over unless you sort your incoming data and assert that in the stage.

vinaymanchinila · Post by **vinaymanchinila** » Thu Jun 30, 2005 8:58 am

Hi Craig,
in the input page of the Aggregator stage, when we select Ascending or Descending in the OSrt ORder column, it doesnt stay like that, it disappears, is it the way it works?
Thanks,

chulett · Post by **chulett** » Thu Jun 30, 2005 9:21 am

No, it should stick around. Did you fill out the Sort field first with a number to show which is 1, 2, etc?

vinaymanchinila · Post by **vinaymanchinila** » Thu Jun 30, 2005 9:36 am

opps no, can I just give the order as 1,2,3,4,5,...or is there any specific reason on how to order them.
Thanks,

chulett · Post by **chulett** » Thu Jun 30, 2005 9:40 am

You need to match reality, otherwise the stage doesn't know and it has to do its own 'sorting'.

pnchowdary · Post by **pnchowdary** » Thu Jun 30, 2005 3:52 pm

Hi Vinay,

You need to give the sort column values like 1,2,3 depending upon how the records are sorted before you feed them to aggregator.

1 - stands for the first key that the records have been sorted on
2 - stand for the secondary key that the records have been sorted on
etc.........

The sort order column will retain the values of Ascending or Descending only when the sort column has been assigned a value (1,2,3...etc)