DSXchange

Dear All,

Could you please let me know the root cause of this problem

In our Jobs Hashfile As a key coulmn and remainng three coulmns hardcoded to '0' ,even though that hashfile key column is allowing null values from the source becuase of that jobs are getting aborted!!!

help on this

Thanks and Regards
srini

It's not hashed file allowing nulls. It's that you are trying to write the nulls from the source column into the hashed file( If I understood what you have written correctly). Define a constraint saying That way, you won't be processing all those rows whose key value is set to(or are) Null.

HTH

kris007 wrote:It's not hashed file allowing nulls. It's that you are trying to write the nulls from the source column into the hashed file( If I understood what you have written correctly). Define a constraint saying

Code: Select all

Not(IsNull(Hashedfile.Key))

That way, you won't be processing all those rows whose key value is set to Null.

HTH

Hi

I know the solution for this but I would like to know the root cause!!!

Problem is simple, your sending in null values.
Or maybe while building the hashed file you have one key defined and while reading the hashed file you have another key defined, or maybe the meta data is not identical. Look into it.

Server jobs do not enforce data types or nullability. Therefore, even though the Key column is marked Not Null, you are not prevented from sending NULL. It is up to you to prevent this from happening. Or switch to parallel jobs, where data types and nullability are enforced.

Can you post the message while getting aborted.