Job Design change for Left outer join

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
rajudx
Participant
Posts: 45
Joined: Tue Nov 14, 2006 1:58 pm
Location: NJ

Job Design change for Left outer join

Post by rajudx »

One datastage job is designed with 3 input oracle stages and one join stage and one output stage (sequential stage)

o1------------
->
o2----------> Join (Left Outer)---------------->Output
^
o3---------------

In Join stage join type defined as left outer join and key column is C1 and all input stage having different types of meta data expect key column..
Due to some data issue on o3 input we need to make a change in join condition,if any key column will come from o3 it should go to go output column without checking value on o1.
I think any kind of join type won't work and can some one please suggest for design change which we can bring the record from o3 even if key value is not matching with 01 key value.

Thanks,
Raju.
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

All inputs to one Join stage must specify the same join key. If the join key is changing, use cascaded Join stages.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Sampath
Participant
Posts: 21
Joined: Tue Apr 05, 2005 2:03 am

Re: Job Design change for Left outer join

Post by Sampath »

First u do join with 1 and 2 table after use one more join for joining 1&2 output with 3 table
Post Reply