Oracle_Nxrp_Trn_Tgt_Mns_Pbip_Rej_Dtl: When checking operator: When binding input interface field "YR" to field "YR": Implicit conversion from source type "int64" to result type "decimal[10,0]": Possible range limitation.
we have gone through the previous posts and changed to integer in all the stages of job.
Now We got this warning
Oracle_Src_Mns_Pbip_Dtl: When checking operator: When binding output interface field "YR" to field "YR": Implicit conversion from source type "int64" to result type "int32": Possible range limitations.
Help me out to eliminate this warning.
Warnings in Datastage
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 28
- Joined: Mon Nov 06, 2006 5:44 am
- Location: chennai
Warnings in Datastage
J.Ithayavino
-
- Participant
- Posts: 12
- Joined: Wed Oct 19, 2005 5:29 am
Re: Warnings in Datastage
[quote="Vino_joe84"]Oracle_Nxrp_Trn_Tgt_Mns_Pbip_Rej_Dtl: When checking operator: When binding input interface field "YR" to field "YR": Implicit conversion from source type "int64" to result type "decimal[10,0]": Possible range limitation.
we have gone through the previous posts and changed to integer in all the stages of job.
Now We got this warning
Oracle_Src_Mns_Pbip_Dtl: When checking operator: When binding output interface field "YR" to field "YR": Implicit conversion from source type "int64" to result type "int32": Possible range limitations.
Help me out to eliminate this warning.[/This warning generaly comes for the coversion,you are conerting th int to decimal and the length specified is wrong.Make sure u r handling the lengh in this case]
we have gone through the previous posts and changed to integer in all the stages of job.
Now We got this warning
Oracle_Src_Mns_Pbip_Dtl: When checking operator: When binding output interface field "YR" to field "YR": Implicit conversion from source type "int64" to result type "int32": Possible range limitations.
Help me out to eliminate this warning.[/This warning generaly comes for the coversion,you are conerting th int to decimal and the length specified is wrong.Make sure u r handling the lengh in this case]
amie
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
It's an alert rather than a warning.
On the input to the stage YR is defined as int64; on the output from the stage YR is defined as int32 (or decimal[10,0] in the other case).
You are being alerted to the fact that not every int64 value can be represented as int32.
To eliminate the warning, render your data types compatible - either int32 on the input or int64 on the output. Using explicit data type conversion functions would also help.
On the input to the stage YR is defined as int64; on the output from the stage YR is defined as int32 (or decimal[10,0] in the other case).
You are being alerted to the fact that not every int64 value can be represented as int32.
To eliminate the warning, render your data types compatible - either int32 on the input or int64 on the output. Using explicit data type conversion functions would also help.
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.