DSXchange

2 licenses.

Not that i can think of right now. Maybe someone else knows and will shed some light on it.

Great. Thanks for sharing that with us. Now you can mark your post as resolved.

Coming back to the "Why you are not using the Aggregator stage", inconsistant and inaccurate data is not the fault of the aggregator stage. Its the fault of how it was used. Take a small set of data, use the aggregator stage to build a job out of it. Test it out. If you have problems, we are here to...

And thats where you are going wrong. You need to partition it by keys. Do this, provide Hash as partitioning and choose the three keys. Now run your job again. See what happens.

Row merger stage gets all the columns and puts them together into a single string and spits it out to the 'merged column'. If you want the each row to be concatenated to a single output row then and only then check the 'multiple lines' option under the general tab. If you just want to merged columns...

In the transformer, go to the stage properties, what partitioning are you providing?

This is due to the fact that the data is partitioned and executed on different nodes in parallel. One node could finish faster than the other and hence the shuffled behaviour. If you want the output to be in order, go to your output sequential file under 'Partitioning' tab, change the Collector Type...

Do you have that new column in your target table?

Parametrize the start value and provide the start value during run time. You can store the last generated key in a file. During run time, the contents of that file can be passed to the job parameter.

Yes you can. Add another stage variable say svSum. Put it after svCnt and before svPrevRow. Its derivation will be if input.key1:input:key2:input.key3 <> svPrevRow Then svSum Else svCnt + in.Amount Then again, if your running in sequential mode it will work, otherwise you need to partition on your k...

Is this just to check if the compiler is not there? If yes then i would say that the compiler, has been infact, removed as the job is not getting compiled. Why dont you go to the environment variable APT_COMPILER, check out its path, go to that path and verify it there.

Search on the error message. This has been covered before.

ghostraider wrote:I need to subtract the greater date from the smaller one

Not too fond of ABS either but instead of checking which one is bigger using if then else, just a positive difference could be achieved using ABS.

I think the driver that is being used is not compatible with that data type. I think you need to get in touch with support and get a patch or a workaround.