DSXchange

Hi

DS 7.5.2
DB: oracle 10g

I have a job that has a dataset as source, and several look ups and all of them are joined using a merge stage and then load it to a dataset. now if i run this job i get the following warning message and it says job aborted.

warning message:

APT_CombinedOperatorController(7),0: Field 'AMOUNT_TYPE_KEY' from input dataset '0' is NULL. Record dropped.

can anybody hepl me fix this.

Not sure why something like this would be "urgent".

First thing you'd find searching here would be an error from "CombinedOperator" gives you no clue as to the stage giving the error. Disable Operator Combinality and then post the error. In the meantime, search for a generic portion of your message, something that's not specific to you but is enough to find other people with similar postings. For example, an exact search for "is NULL. Record dropped." returned 50 matches. The truth is out there.

Hi
Thank you so much for the suggestion, i really appreciate that. im sorry i was in a hurry thats why, I still have the warning message. but when i tested the same job by running from the designer it ran, but when i run the sequence from the DS director it aborts, so i removed the limits for the warning messages (which was set to 50) and my job didnt abort. I know this is not the right solution, but for time being i was able to handle this.

i will work on this and find the solution and will keep u updated.

thank you so much.

Hi,
Check the properties of all lookup stages that are used in your job. There are some properties which can tell the job how to handle if lookup doesn't exists. Simply change that property to REJECT. It will eliminate that warning.

Is the Field 'AMOUNT_TYPE_KEY' defined as Not NULL?

Are you using any transformer stage in the job?

Scope wrote:Are you using any transformer stage in the job?

It surely seems to be transformer where there are some transformations applied on 'AMOUNT_TYPE_KEY'. avoid using transformation on null values.

you can use syntax like:
Hope i understood it correct if not then disable operator combination and then post the log.

if you are equating that column to a value in a if then else statement

equate the value to NullToEmpty(Column)='the value'

i think what priyadarshikunal said is right,need to handle the null values properly when doing any arithmetic operations or uaing functions like 'Trim' or the column is defined as a key etc. other wise the record will drop.