Hello,
I'm trying to execute a very simple job :
OCI oracle ->transformer -> sort -> OCI Oracle
But during the execution, the process returned a very weird error :
"Null value on accessor interfacing to field"
i was thinking that DS PX was able to handle itself the "null" value for the sort stage, so i'm wondering where this error came from ?
thanks in advance
Chanthou
error "Null value on accessor interfacing to field"
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 11
- Joined: Mon Jun 16, 2003 2:21 am
-
- Participant
- Posts: 3593
- Joined: Thu Jan 23, 2003 5:25 pm
- Location: Australia, Melbourne
- Contact:
One place you can get into problems with null fields is within the Transformer. Find out what source field has nulls in it and then add null handling for that field (such as NullToValue) in the Transformer. Do not try to use that field in any derivation function until it has been null handled.
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
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Re: error "Null value on accessor interfacing to field&
If you were the Sort stage, how would you handle null? Can you be more specific about how you think that the Sort stage can handle null?chanthou_2000 wrote: i was thinking that DS PX was able to handle itself the "null" value for the sort stage, so i'm wondering where this error came from ?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
don't know if this is relevant in your case, but I got this error in a different situation:
I've created a lookupfile with a field as nullable. When reading from this file the field was set to non-nullable, and I got this error from the lookup-stage.
So : maybe it's just mismatch in column-definition between stages.
I've created a lookupfile with a field as nullable. When reading from this file the field was set to non-nullable, and I got this error from the lookup-stage.
So : maybe it's just mismatch in column-definition between stages.
-
- Participant
- Posts: 222
- Joined: Tue Aug 30, 2005 2:07 am
- Location: pune
- Contact:
Just Try out by null handling with the nullable YES input fields.
Source : Nullable YES
If Isnull(ColumnA)
then ' ' or 0 (depends on your requirement, usually for sting Spaces and for numeric 0)
Else
ColumnA.
Target : Nullable ( Yes/No)
Source : Nullable YES
If Isnull(ColumnA)
then ' ' or 0 (depends on your requirement, usually for sting Spaces and for numeric 0)
Else
ColumnA.
Target : Nullable ( Yes/No)
NageshSunkoji
If you know anything SHARE it.............
If you Don't know anything LEARN it...............
If you know anything SHARE it.............
If you Don't know anything LEARN it...............