I can't get something as simple as a lookup to work. When I try to debug to see what may be going on, the trace for the lookup does not display. It also shows 2 rows in 0s with 0 rows/s. What the hell do I make of that? Is there some trick or secret that I don't know that I need to use to get the trace for the lookup to display? Look at GroupLkp in my image.
You've got left outer joins on your input tables. Click the spanner tool to expand the rules box.
The lookup called LocInfoLkp always works the way I expect it to. I know how to do a lookup in a tMap. This second lookup I added is not working properly, though. I don't think I am explaining this very well. Please allow me to try again. Forget the cartesian join for now. The lookup does not return any values in the tMap even though the keys match and I am getting rows out of the tMysqlInput. If I delete the data flow, rename it from the default name and run the job the lookup will work, SOMETIMES. If I then change anything in the tMap relating to that lookup, it will no longer work, even if I change it back.
I haven't tried starting from scratch but yeah, something is not right. I've put a lot of work into this. Hopefully support can help. My head hurts from banging it against this wall.
After 24 hours support never got back to me so I put in a workaround. I don't have time to do all my work over so I put in a second tMap right after the first one and did the lookup on that one and now it works. Defeats the purpose of tMap but the tMap component apparently can't handle more than 2 inputs.
tMap can handle lots of lookups if the rules are set up correctly. You're using left outer joins on both lookups so you will never get a sensible result.
