DSXchange

Yes. Having the data sorted makes aggregator stage work efficiently.

There can be more than one reason.

Search the forum as this has been discussed before.

Use Job Param

The grep will return the full line. Hence you may want to extract the value from the list.

You may be assigning char value to a numeric variable.

Let us take a step back.

You designed a job to 'create' an hash file whereas the other developer is using it to 'reference' from an hash file. So where is the hash file now?

I see a 'missing link' there.

Check whether you can run sqlplus from the server and establish connection to required Ora SID.

Try logging in as dsadm.

That is the SAP naming convention + DataStage process name.

Check your /tmp directory also. But, I couldn't get around this problem and had to design a solution that did not include the Aggravator stage. Good luck. (Great error msg isn't it?) Larry Yep...it is the 'Aggregator' stage and not 'Aggravator' stage. Why do you want to aggrevate his problem? (Just...

That is because a transform stage does not support reference links emerging from it.

It is better to perform using file patterns than a global set. Also you need to arrange the values in the sequencer to process the files.

The field you see is not a COMP field. It is decimal with implied sign and decimal value.

Did you bounce DS after changing dsenv?

Did you try importing from Oracle?

By the name of the file - Fact Table - I assume that the DS logic must ensure that the dimension keys are looked up before loading. Also in this stage, you must ensure the data quality and have minimal (or zero) reject rows.