Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi,
I have a very peculiar (and could be very simple) problem with tMap. Here is my job
I am trying to get a 6 column input to the destination. The tmap shows the mapping as I expect:
However when the data lands in final table it gets mapped to wrong columns. e.g. member_id column is loaded with page_nm data, domain_nm gets member_id data etc.
Can someone please help me figure out what I am missing here?
Thank you in advance,
workingbuddha
I think I figured out what the issue has been(and it is such a dumb issue).
The order of columns in my select statement in the query of tDBInput(select cd_event_id, member_id....) was different from the schema of tDBInput.
I just changed the select from query to match the order exactly as that of the schema and now the data is flowing perfectly.
I cannot believe this could be an issue for any ETL... smh.
Thanks for the help though CLi1594691515.
Hi,
Would you mind to capture you tDBoutput component? I suspect it is causing by the ordering in tDBOutput_1(Output) is not align with your input (tMap).
Sure... here is the screenshot of the tDBOutput:
Seems nothing wrong on the setting.
Maybe you can put tLogRow before and after tMap to see is the in and out results are as expected or not.
Put it after tmap and I get something like this.
Output in the table still has garbled values..... Am I missing some delimiter/carriage return here?
How about the input one from tDBInput? Does it looks like the output?
I am not sure what you mean by input from tDBInput but this is the schema for tDBInput.
Simply said, use tLogRow to check the input data from tDBInput vs output data from tMap. 😄
I think I figured out what the issue has been(and it is such a dumb issue).
The order of columns in my select statement in the query of tDBInput(select cd_event_id, member_id....) was different from the schema of tDBInput.
I just changed the select from query to match the order exactly as that of the schema and now the data is flowing perfectly.
I cannot believe this could be an issue for any ETL... smh.
Thanks for the help though CLi1594691515.