DSXchange

Hi Ajith, Padchar pads the given character till the given length. Hence if say length is 10, and if the input is ' Hello' the result will be ' Hello '. So the filter will facilitate the check by assuming all the chars that present in the right of the character will be due to the padded character. Wh...

Ooo... Thats the biggest number that can be found in our site. :D

Ray's option is for previously grouped and sorted.

How can Filter stage can diffrentiate, if the space is from the source or that been padded by previous stage? Or you check for the presence of space in the first char of the DESC.

This sounds interesting that the job got compiled after changing the Trim option. Usually these sort of error will lead to the work on the compiler liecence or the expiry date of it. PWD may also need to be set in Environmental variable.
How about other jobs, does it all compile without any issues?

Group by dosn't sort the data and Auto partition doesn't assure you the sorted output. The preferred option is to hold hash partition on the sorting key which should be same or should atleast cover up all the joining key.

Main differentiating factor is performance.

What was the error message prompted when you compile in Windows environment?

Is it a message from DS or custom produced error message. What is the desing of the job? When was this error appearing?

Is your statistics shows as 1474430 or the count on your target table? If its the later case, you might be counting the previously inserted data as well. In not, do you see any duplicates in the extracted data for any specific key?
Ensure partition method is 'same' and not Entire in copy stage.

...working fine with a single partition which solves our problem...

Which doesnt utilize the PX functionality.

Can you explain with some more details. How many number of rows were in table and what was the output number of rows. How many stages were there? what partition is used in all stages? Select query if any?

Sort stage will itself insert a sort operator, and by giving Don't sort, you are suppresing it. Rather you can include the environmental variable APT_NO_SORT_INSERTION in that job if you have used order by in both the source stages.

This case you can check for the space for the full length of the DESC field. Or you can trim and check for ''.

As mentioned, it many not only within Datastage, you you may need to focus on Database side as well. It also depends on the two table. Are the both same. Are they both indexed in similar columns. Are they both analyzed recently. Are the query from each table taking same time.