DSXchange

Stage variables are not-nullable always and so you cannot use setnull function inside the stage variable. You may need to achieve setting null outside the stage variable.

Yes stage variables are always not nullable and so we cannot use setnull function in the stage variable. Sorry for creating the confusion.

If stage variable property is non-nullable then we should not assign any null value to the stage variable. If we do we get a default value of 0.

But for better performance definetly DB2/UDB Enterprise stage

Search the forum I believe it will answer your question.

check the properties of stage variables which should solve the issue.

Check the following message from your post::
Setting null to this non-nullable field: StageVar0_FISCALMTHENDDT

I would go with Hash partitioning.

Can you provide few details of your job. Just by seeing your message we cannot analyse anything.

gd is your problem solved?

Please post the server issues in server forum only.... :D

You cannot trim the columns directly in hashfile.If you don't have any transformer between the hashfile and the source stage try trimming the column directly at the source only( I mean database only.). But please be cautious while doing this as it may impact your job performance.

try once trimming both the columns

hemachandra can you please give some instances when you got wrong values? I used it quite frequently. It will help me further

How are you loading the data into the table in your job