Issues with Partitioning after Fixpacks

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
rsadevelopers
Premium Member
Premium Member
Posts: 8
Joined: Wed Nov 16, 2011 2:11 pm

Issues with Partitioning after Fixpacks

Post by rsadevelopers »

Hi All, we have run into a production issue that started after DataStage Fixpack 3 was installed on our production server. It seems that DataStage decided to partition differently after the patch than it did previously. The job is very simple with an input dataset joining to other datasets with AUTO paritioning. The issue is the join wasn't working anymore in that we do not get matches based on the key. We changed the partiioning from AUTO to SAME and it resolved the issue. The worry is how many other jobs are affected? Has anyone else run into a similar issue after a fixpack installation?
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

To which actual version did you apply Fix Pack 3? What does your official support provider have to say? Have you searched IBM website for known issues around this Fix Pack?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
rsadevelopers
Premium Member
Premium Member
Posts: 8
Joined: Wed Nov 16, 2011 2:11 pm

Post by rsadevelopers »

Found this link on IBM support site. This describes what is occurring.


https://www-304.ibm.com/support/docview ... wg21459416
Post Reply