Oracle Null handling
Moderators: chulett, rschirm, roy
Oracle Null handling
Hi All,
I have a parallel job with an Oracle Enterprise stage as the source, a modify stage and a dataset stage as the destiniation.
I am getting a warning as such:
Oracle_Enterprise_0: When checking operator: When binding output interface field "rel_name_rel_key" to field "rel_name_rel_key": Converting nullable source to non-nullable result; fatal runtime error could occur (use modify operator to specify value to which null should be converted)
The thing is I did use a modify operator with the handle_null function. Also, all the columns are specified as nullable:no.
Any ideas?
I have a parallel job with an Oracle Enterprise stage as the source, a modify stage and a dataset stage as the destiniation.
I am getting a warning as such:
Oracle_Enterprise_0: When checking operator: When binding output interface field "rel_name_rel_key" to field "rel_name_rel_key": Converting nullable source to non-nullable result; fatal runtime error could occur (use modify operator to specify value to which null should be converted)
The thing is I did use a modify operator with the handle_null function. Also, all the columns are specified as nullable:no.
Any ideas?
-
- Participant
- Posts: 437
- Joined: Fri Oct 21, 2005 10:00 pm
Re: Oracle Null handling
Oracle_Enterprise_0
Is that the target or source? I'm going to assume the target, but if not let me know.
When you performed the modify it is pretty typical to use the same metadata on the input and output link. Did you make sure that the column for which you are performing the null handle was changed to not null?
Is that the target or source? I'm going to assume the target, but if not let me know.
When you performed the modify it is pretty typical to use the same metadata on the input and output link. Did you make sure that the column for which you are performing the null handle was changed to not null?
Keith Williams
keith@peacefieldinc.com
keith@peacefieldinc.com
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Premium Member
- Posts: 353
- Joined: Wed Apr 06, 2005 8:45 am
Amazingly defining the columns as nullable and letting the modify stage handle them worked with no warnings. What is strange though is that the columns I am selected and concatenating together are primary key values so the columns are defined as not null on the Oracle database.
If anyone has an idea as to why this is, let me know.
Thanks for all the help
If anyone has an idea as to why this is, let me know.
Thanks for all the help
-
- Charter Member
- Posts: 199
- Joined: Tue Jan 18, 2005 2:50 am
- Location: India
-
- Participant
- Posts: 437
- Joined: Fri Oct 21, 2005 10:00 pm
Any calculation that you perform in your SQL will make DataStage interpret the field as nullable. So if your source Oracle stage has this concatenated field marked as not nullable, which you made that way because all of the columns that make up your concatenation are not null. When it runs your sql it is going to interpret the field as being nullable, and being inserted into a not nullable field. It will through a warning.
This is true for any calculation or function in the sql (nvl,concatenate,to_date, to_char...). To avoid this do your transformation in DataStage.
This is true for any calculation or function in the sql (nvl,concatenate,to_date, to_char...). To avoid this do your transformation in DataStage.
Keith Williams
keith@peacefieldinc.com
keith@peacefieldinc.com