Lookup Fails on Timestamp with MicorSeconds.

[synsog]

My Source Data:
ID SOURCE_TS
230 2012-05-31 15:13:32.6540000
230 2012-05-31 15:13:52.1540000

Reference Data:

REF_ID REF_TS
230 2012-03-22 07:19:37.1490000
230 2012-05-31 15:13:32.6540000
230 2012-05-31 15:13:52.1540000

Getting Error:-
Ignoring duplicate entry at table record 3; no further warnings will be issued for this table

[jwiles]

What's the failure? That message is just a warning and will not force a job to fail.

[synsog]

here the issue, we need to retrieve the reference data based on lookup condition, for specific ID & REF_TS, we will get the some key fields data from reference table.

[mobashshar]

Are you using Extended Microseconds for timestamp fields?

[zulfi123786]

Getting Error:-
Ignoring duplicate entry at table record 3; no further warnings will be issued for this table

As noted this is not error but just a warning and looking at the warning it is clear that on the reference link the column is defined as Timestamp witthout the microseconds extension

[ntr]

Getting Error:-
Ignoring duplicate entry at table record 3; no further warnings will be issued for this table

Why above warning will come and what need to do to supress that one

Thanks

[zulfi123786]

Look up will generate the warning if there are duplicate values over the key columns, in your case there are no duplicates if the microseconds are considered.

It is not advisable to look for means of how to suppress warnings rather approach with a resolution to fix the warnings.

you have two choices:
1) Select the extended "microseconds" option in the reference link
2) Select "Multiple rows returned from link" option in the look up - Beware this would make your look up work like a join stage (inner join)