All,
is there a simple generic way to capture the rows causing the 'Reference lookup generated X rows'-warning. Logging the current keys used for the lookup would do...
thanks,
William
Identify rows resulting in Reference lookup generated X rows
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Welcome aboard.
Query the reference table.
Query the reference table.
Code: Select all
SELECT key,COUNT(*) FROM tablename GROUP BY key HAVING COUNT(*) > 1;
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Ray,
thanks for the reply. As a matter of fact that's exactly the way we currently figure it out at a runtime 'incident'. But what we are actually trying to achieve is that the (keys of) the row(s) causing the warning, also come forward in the Director warning log automatically, so no manual SQL is needed to figure it out at a runtime incident... So next to the warning entry saying: Reference lookup generated X rows'' we would like to have an entry in the log that identifies the row... So querying the reference table is actually the thing we're trying to get rid of....
Thanks,
William
thanks for the reply. As a matter of fact that's exactly the way we currently figure it out at a runtime 'incident'. But what we are actually trying to achieve is that the (keys of) the row(s) causing the warning, also come forward in the Director warning log automatically, so no manual SQL is needed to figure it out at a runtime incident... So next to the warning entry saying: Reference lookup generated X rows'' we would like to have an entry in the log that identifies the row... So querying the reference table is actually the thing we're trying to get rid of....
![Confused :?](./images/smilies/icon_confused.gif)
Thanks,
William