error in job log

qutesanju · Post by **qutesanju** » Fri Jun 19, 2009 3:39 am

I ran one job which is updating records based on hash file lookup
but it get failed for some records saying.......

Unable to locate and update an entity, when an action of Update Only has been specified.

what must be reason?
I set UPDATE only action at target table to update only

ArndW · Post by **ArndW** » Fri Jun 19, 2009 4:05 am

The database cannot update a record that does not exist.

qutesanju · Post by **qutesanju** » Fri Jun 19, 2009 4:09 am

So can i SET Insert NEW OR UPDATE EXISTING?
action at the target table?

The job is in production

ArndW wrote:The database cannot update a record that does not exist. ...

ArndW · Post by **ArndW** » Fri Jun 19, 2009 5:12 am

Sure, that would get rid of your error message, but you need to find out if that is a legal option in terms of your job design.

qutesanju · Post by **qutesanju** » Fri Jun 19, 2009 5:36 am

but since this is prod so i m not sure to set inser new or update existing at the target table

chulett · Post by **chulett** » Fri Jun 19, 2009 6:55 am

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.

qutesanju · Post by **qutesanju** » Fri Jun 19, 2009 7:01 am

same job works fine in developement environment

chulett · Post by **chulett** » Fri Jun 19, 2009 7:16 am

No it doesn't, you just think it does.

ArndW · Post by **ArndW** » Fri Jun 19, 2009 7:23 am

The job works the same, but I am sure your production data is different from your test data, thus the error.

chulett · Post by **chulett** » Fri Jun 19, 2009 7:31 am

Exactly.

qutesanju · Post by **qutesanju** » Fri Jun 19, 2009 9:12 am

ok the job design is like this

input query-->transformer(lookup for hash file)-->target table update

i joined input key=hash file key in transfomer lookup
i checked this job but i didnt found any thing interesting .....
.what should be done for this?

chulett · Post by **chulett** » Fri Jun 19, 2009 9:29 am

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.

major · Post by **major** » Sat Jun 20, 2009 11:51 am

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..

qutesanju · Post by **qutesanju** » Mon Jun 22, 2009 4:17 am

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

chulett · Post by **chulett** » Mon Jun 22, 2009 6:24 am

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?