hemanthakumar wrote:As per the suggession from dsexchange users we have tried with clear patition in stage advanced --> preserve-partitioning --> clear
Hi hemanthakumar,
on which stage did you set the preserve-partitioning option to clear? Understand that you have to do it on the stage
preceding the one where repartitioning occurs on the input dataset (if I got it right you do hash-partitioning on an Aggregator before your Join-stage - look at the stage preceding your Aggregator then).
The message also points to the fact, that DataStage inserted an additional TSortOperator to your job-design, because you did not specify the sort-order (on the Aggregator?) yourself. It might be a good idea to specify that explicitly.
"It is not the lucky ones are grateful.
There are the grateful those are happy." Francis Bacon