You need to correct your job design. Something is wrong if your hashed lookup is supposed to get you updates and then they're not found in the target database.
-craig
"You can never have too many knives" -- Logan Nine Fingers
I would guess that either your lookup constraint logic is faulty or the hashed file hasn't been populated correctly. Forced to guess due to an extreme lack of details.
-craig
"You can never have too many knives" -- Logan Nine Fingers
There must be some key by which you are updating the target table..
Check for few records which are failing to update
if the record exists and it fails to update , probably you dont have update permission..if the record doesn't exits then no problem..
I checked the log in director
suppose i have input query which contain 5 columns c1,c2,c3,c4,c5
in transformer i lookedup for c3.=c3.hash file
but in prev same job abort when i checked reason for this job abotrion it is showing /it looks that datastage is picking up c4 instead of c3 in lookup with hash file
What makes you think it is 'picking up c4 instead of c3'? Are you using the exact same metadata in the lookup hashed file as the hashed file was created with?
-craig
"You can never have too many knives" -- Logan Nine Fingers