DSXchange

Interesting, I've never had much need for the -local option so tend to forget about it. Now, does this work in the OP's scenario where the Environment Variable has been defined not just in the .profile but in the Administrator as well? Meaning, it allows a locally set value to override the Project's...

Divide the column by 10000000. Or use FMT to shift the decimal point over the correct number of places.

You marked this as a Server question so you got a Server answer.

Ah... guess I should have said 'six ways from Sunday' if I wanted to get the idiom correct. It just means 'a lot' or 'every way conceivable' to me. 'Premium free' means without premium. Meaing I chose not to mark my posts as 'premium content' so you could read everything. If I had marked the answers...

What?

You have to sort the data in a manner that actually supports the grouping being done or it will be ignored. And the stage will bust you if it finds you've lied about the order and abort with the ever appreciated 'row out of sequence' error. You can tell you've got the sorting correct when rows flow ...

I've already explained this six ways to Sunday, all Premium free... not sure what else to say. [sigh]

If someone else has something to add, please feel free to do the needful.

Right. You need to ensure that the Aggregator knows your input is sorted or it will 'sort' it itself. Again. And go boom when the volume is too high to hold all in memory. Never mind the fact that your job design will run all ten segments at the same time, compounding any memory issue.

I have tried it as i said in my first post. The env variable $DIRSRC has got a default value of "/dbload01/test" as defined in datastage administrator. But i want to override it with the current setting value. That is why, when i used the above variable in my job , I changed the value from defalut ...

Good.

ps. There's no need to set either ORACLE_SID or ORASID in the dsenv file. Doesn't hurt but they aren't needed.

But the default value of the environment variable and current value set in the environment is different. How so? Not according to your post they're not. I think we just have a semantics issue here. Please tell me with detail if I want to use $ENV as default value for an env variable in job properti...

If you want it to default to the current value in the environment as you stated and use that default value in the job, then yes.

satishbalantrapu - you need to uncheck the 'Disable BBCode' option in your posts, otherwise all that quoting and bolding doesn't really work all that well.

Looks to me like you can take that list and look for stage names with a 'dot' in them, the portion before the dot seems to be the Container name.

You can still do a 'union' if the queries all return the same number of columns and like column types. If you take a moment and actually provide some detail for your question rather than just basically repeating the same thing you might get some better advice. So... how similar are these queries?