July 5, 2007 at 1:57 am
Hi,
While Executing LOOKUP transformation for doing Key resolution from a Dimension Table to load a Fact table, I am getting the following error:
[Lookup 1 [2983]] Warning: The Lookup transformation encountered duplicate reference key values when caching reference data. The Lookup transformation found duplicate key values when caching metadata in PreExecute. This error occurs in Full Cache mode only. Either remove the duplicate key values, or change the cache mode to PARTIAL or NO_CACHE.
Can someone help me fix this ?
Any help is Deeply Appreciated.
Thanks a lot,
Regards,
Sundar
July 5, 2007 at 2:26 am
it's as the error says - you have a duplicate in your cache.
The statement that you are using for the lookup is returning a duplicate based on the key. Run the statement in SSMS and find the duplicate.
Cheers,CrispinI can't die, there are too many people who still have to meet me!It's not a bug, SQL just misunderstood me!
July 5, 2007 at 3:18 am
Hi,
I am not using any statement for the Lookup.
Still I am getting this error...
Any Hint/Clue ?
Thanks,
Sundar
July 5, 2007 at 3:26 am
First note: Don't select a table unless you are using every single column in it. If you are not, select only the columns you will use. Why waste memory?
The key is the columns you are using to join onto the data flow. Run a select in SSMS with the same columns and check for duplicates.
Is the key using the same columns as your dim's PK?
Cheers,CrispinI can't die, there are too many people who still have to meet me!It's not a bug, SQL just misunderstood me!
July 5, 2007 at 4:29 am
Hi,
After running data viewer , I found that there was no error in data.
In the Lookup error configure properties, I selected "Ignore Failure" and now it works like a charm !!
Thanks a lot for your Time and Help !
Cheers,
Sundar
July 5, 2007 at 4:36 am
hold your horses....
The duplicates in cache cannot be seen in the data viewer. You are looking at your source data there, not the cache.
Saying ignoring errors because there is an error you do not understand is hardly a brilliant way to do error handling. Do you understand what Ignore Errors does in the lookup? IF not, you're bound to find out soon.
Fix the problem - don't mask it.
Cheers,CrispinI can't die, there are too many people who still have to meet me!It's not a bug, SQL just misunderstood me!
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply