Hi All,
The following error had occured when tried to load the oracle table.
" Failure during execution of operator logic ",
since the error type is fatal I'm unable to proceeed. If I remove the Oracle Stage and replace with Seq File then the file gets loaded. Any ideas.
Regards.
Error while inserting in Oracle Stage
Moderators: chulett, rschirm, roy
Previous Warning Message:
LkpVIN,0: When binding input interface field "XVIN" to field "XVIN": Converting nullable source to non-nullable result; fatal runtime error could occur (use a modify operator to specify value to which null should be converted)
Current Error:
Failure during execution of operator logic
Both the source and lookup are non-nullable columns...FYI
Regards
LkpVIN,0: When binding input interface field "XVIN" to field "XVIN": Converting nullable source to non-nullable result; fatal runtime error could occur (use a modify operator to specify value to which null should be converted)
Current Error:
Failure during execution of operator logic
Both the source and lookup are non-nullable columns...FYI
Regards
As a rule, you must provide a method for DataStage to handle conversion of Nullable values to non-nullable values. Because if you don't, then DataStage will act very funny when it is provided a Null value without any way to handle it.
Unfortunately, I can not simply believe you when you said that source and lookup values are Non-nullable. Look further back to ensure that all data are non-nullable. Chances are likely you will find a field that was nullable (probably the database field you are using for lookup?
It is a well known flaw within DataStage EE (especially on 6.x) that they propagate Database-defined metadata despite what you declares. Thus you will get that warning message when you have a database field that is nullable. You will need to use the modify stage (yes, through the Generic Stage, you can invoke the Modify stage), or the Transformer to handle the nullable field.
Add a copy stage, and turn off column propagation, and see how the warning messages behaves. In fact, turn off the job's RCP, and see how it affects the behavior of the job.
Are there any other warning messages in the job?
Unfortunately, I can not simply believe you when you said that source and lookup values are Non-nullable. Look further back to ensure that all data are non-nullable. Chances are likely you will find a field that was nullable (probably the database field you are using for lookup?
It is a well known flaw within DataStage EE (especially on 6.x) that they propagate Database-defined metadata despite what you declares. Thus you will get that warning message when you have a database field that is nullable. You will need to use the modify stage (yes, through the Generic Stage, you can invoke the Modify stage), or the Transformer to handle the nullable field.
Add a copy stage, and turn off column propagation, and see how the warning messages behaves. In fact, turn off the job's RCP, and see how it affects the behavior of the job.
Are there any other warning messages in the job?