Remove the warnings

[Vino_joe84]

Oracle_Src_Nxrp_Trn_Vce_Avl_Dtl: When checking operator: When binding output interface field "TIME_KEY" to field "TIME_KEY": Converting a nullable source to a non-nullable result;
a fatal runtime error could occur; use the modify operator to
specify a value to which the null should be converted.

We use all the keys as not null column in both source stage as well as the target stages.We are try to eliminate this warnings by introducing modifier stage.Still it is not poss.....share ur ideas to avoid this warnings

[Nageshsunkoji]

Hi,

I think, you have to check your flow once again.Any where, by mistakenly you have different nullability of field TIME_KEY from source to target. The warning saying that, handle those null, its suggesting that use modify stage for this purpose.Check the your source data also for the field TIME_KEY.

One more possibility is if you are perofrming lookup or join to get the filed TIME_KEY. Then check, if lookup fails it will give the null value to u r filed.

[ArndW]

Introducing a modify stage isn't enough, you need to add a handler for null as the in the stage as message suggested. Look at page 28-4 of the Parallel Job Developer's Guide

[chulett]

Search the forum for handle_null which doesn't seem to be documented anywhere else.

[splayer]

Your TIME_KEY field is null somewhere, most probably in your source stage or one of the intermediate stages. If it is NOT NULL across the board, Datastage would not give this message.

[ray.wurlod]

Orchestrate Operators manual is where handle_null() is documented.