Reference lookup generated, Only the last row was used
Moderators: chulett, rschirm, roy
Reference lookup generated, Only the last row was used
IndividualDim_S..X_individual: Reference lookup generated 3 rows. Only the last row was used.
When data exceeds above the recordcount then I am getting this warning.
When data exceeds above the recordcount then I am getting this warning.
You need to change your lookup logic so that only a single row is returned
Or are you trying to return multiple row for lookup ?
Give your job design, what you are trying to do, more details.... if the above does not help you.
Or are you trying to return multiple row for lookup ?
Give your job design, what you are trying to do, more details.... if the above does not help you.
Narasimha Kade
Finding answers is simple, all you need to do is come up with the correct questions.
Finding answers is simple, all you need to do is come up with the correct questions.
What stage are you using to do the reference lookup? As noted, when your query in the stage returns more than one record, only one will be returned. Some stages do this silently, some do it and log a warning as well. The solution is to rewrite the query so that it returns the singleton row you want out of the rows it selects.
Unless you need to return multiple rows, for that you'd have to use either the ODBC or UV stage.
Unless you need to return multiple rows, for that you'd have to use either the ODBC or UV stage.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Participant
- Posts: 83
- Joined: Sat Oct 28, 2006 6:25 am
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Sounds like you are populating your reference data set (from the dimension table) with both current and non-current rows. Check that you only load current rows.
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.
The bussiness want to maintain the multiple records(Realtime) for each employee working on different locations and SSN in the lookup and insert a single active record in the target table.
So that when the same employee come in with the same SSN and same ID and diff location it will do the updates and inserts.
So that when the same employee come in with the same SSN and same ID and diff location it will do the updates and inserts.
-
- Participant
- Posts: 83
- Joined: Sat Oct 28, 2006 6:25 am
As highlighted "insert a single active record in the target table", we should have only one active record which if changed should be updated or if a new record not present in db comes, should be inserted.
Therefore in no scenario the count of records returned from the lookup should be more than one, if you are extracting only active records!
Therefore in no scenario the count of records returned from the lookup should be more than one, if you are extracting only active records!