rejected records
Moderators: chulett, rschirm, roy
rejected records
Hi All
From source 83 records coming to transformer
but out of the transformer only 2 records are coming,no records were rejected.
I am getting the following warning
APT_CombinedOperatorController(3),1: Field 'pt_state' from input dataset '0' is NULL. Record dropped
APT_CombinedOperatorController(3),1: Warning, all other rejected records will be silent.
anyone help me in this
Thanks
sundar
From source 83 records coming to transformer
but out of the transformer only 2 records are coming,no records were rejected.
I am getting the following warning
APT_CombinedOperatorController(3),1: Field 'pt_state' from input dataset '0' is NULL. Record dropped
APT_CombinedOperatorController(3),1: Warning, all other rejected records will be silent.
anyone help me in this
Thanks
sundar
Sundar,
the warning is telling you that at least one record and more likely all 81 missing rows are being dropped because they have a NULL value and your target column does not allow nulls.
the warning is telling you that at least one record and more likely all 81 missing rows are being dropped because they have a NULL value and your target column does not allow nulls.
Last edited by ArndW on Thu Jul 27, 2006 4:24 am, edited 1 time in total.
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
I can state that the difference in these two is that column "'pt_state" is not null.
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
Reconfirm the output metadata of the transformer for pt_state column is nullable.Field 'pt_state' from input dataset '0' is NULL. Record dropped
If you source is nullable = 'no', check the RCP. Disable it.
Esle change this column as nullable = yes right from begining and do a 'Force compile' and rerun the job.
Impossible doesn't mean 'it is not possible' actually means... 'NOBODY HAS DONE IT SO FAR'
You may also check the "null field value" property set in "Sequential file stage".
In your case, the transformer / the sequential file would drop records if :
1. transformer : put a "NULL" to a non-nullable field
OR
2. sequential file : you have not set "null field value" for stage to handle how it represent "NULL" on IO disk.
you may check it also.
p.s. "null field value" property is located in
right click row -> edit row -> click "nullable" -> you may find "null field value" in property window.
Hope it can help you.
In your case, the transformer / the sequential file would drop records if :
1. transformer : put a "NULL" to a non-nullable field
OR
2. sequential file : you have not set "null field value" for stage to handle how it represent "NULL" on IO disk.
you may check it also.
p.s. "null field value" property is located in
right click row -> edit row -> click "nullable" -> you may find "null field value" in property window.
Hope it can help you.
alphac
Transformers can handle null values without any problem, you don't need to use any null field value etc, however sequential files cannot handle nulls by itself, you need to handle by yourself. ( use special null value as suggested, )
Thanks,
Chad
__________________________________________________________________
"There are three kinds of people in this world; Ones who know how to count and the others who don't know how to count !"
Chad
__________________________________________________________________
"There are three kinds of people in this world; Ones who know how to count and the others who don't know how to count !"
-
- Participant
- Posts: 3593
- Joined: Thu Jan 23, 2003 5:25 pm
- Location: Australia, Melbourne
- Contact:
This is quite common when you put a transformer after a join or lookup stage. You end up running a transformation function against a reference field that can be null.
You need to put null handling around any transformer field that might contain a null and requires some type of transformation change or checking. Especially the columns that have come back from the join.
You need a reject link from the transformer to trap those rows that are getting dropped off. You might fix this first NULL problem but a new problem may show up weeks later.
You need to put null handling around any transformer field that might contain a null and requires some type of transformation change or checking. Especially the columns that have come back from the join.
You need a reject link from the transformer to trap those rows that are getting dropped off. You might fix this first NULL problem but a new problem may show up weeks later.
Certus Solutions
Blog: Tooling Around in the InfoSphere
Twitter: @vmcburney
LinkedIn:Vincent McBurney LinkedIn
Blog: Tooling Around in the InfoSphere
Twitter: @vmcburney
LinkedIn:Vincent McBurney LinkedIn