DSXchange

Change the preserve partitioning option in your input dataset to "Clear".
This can be found in the Advanced tab under the stage properties of the dataset.

Change the preserve partitioning option in your input dataset to "Clear".
This can be found in the Advanced tab under the stage properties of the dataset.

Check the sequence of fields for partitioning and sort on each input link to the join.

It looks like a timmings issue to me. Most probably the lookup data is not available when you are running it first time but becomes available when you run it again. Check the dependency with jobs creating the lookup data.

You can get a MIN or MAX of only a number column in Aggregator stage in PX.... :( The easist way would be to use a sort->Remove Duplicate stages after adding a constant value column and sorting on the date-field you want the MAX for. Another way of doing it would be to derive a new integer for the t...

ok thanks for the info Roy.Leaving the space issue aside, atleast from the time consuming perspective, can you advice me an alternative logic or stages to acheive the same functionality? I would add another sort stage which generates a clusterkey and derive column3 based on the value of clusterkey....

ray.wurlod wrote:Would you be prepared to try using an Enterprise ODBC stage, just to determine whether the symptom is database related or client software related?

I think I have seen this problem. Try to set the commit level (or whatever it is called in DB2) to 1 and run the job again....