warnings...is it ok to ignore them?
Moderators: chulett, rschirm, roy
warnings...is it ok to ignore them?
Hi All,
I am getting similar warnings in all the 4 PX jobs i am developing.
Source table has EMPLOYEE_NBR in Numeric(8,0).
compareEmployeeTables: When checking operator: On input data set 0: When binding input interface field "EMPLOYEE_NBR" to field "EMPLOYEE_NBR": Implicit conversion from source type "int32" to result type "decimal[8,0]": Possible range limitation
Is there anyway to overcome these warnings ?
Is it ok to ignore such warnings, since the jobs run fine ?
Thanks
Jay
I am getting similar warnings in all the 4 PX jobs i am developing.
Source table has EMPLOYEE_NBR in Numeric(8,0).
compareEmployeeTables: When checking operator: On input data set 0: When binding input interface field "EMPLOYEE_NBR" to field "EMPLOYEE_NBR": Implicit conversion from source type "int32" to result type "decimal[8,0]": Possible range limitation
Is there anyway to overcome these warnings ?
Is it ok to ignore such warnings, since the jobs run fine ?
Thanks
Jay
Jay,
no, DS does not have a problem using the 2 versions of Ora, the development is quite transparent to that.
no, DS does not have a problem using the 2 versions of Ora, the development is quite transparent to that.
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
Memrinal - In my opinion it is not OK to ignore these warnings. I would prefer to do a cast or conversion to the data type that the job expects to avoid the warnings and accept the performance hit that this might entail.
I do this for future maintenance - if I now get into the "ignore warnings" mode for a job I will ignore any warnings in the future and would most certainly miss any new warnings that might occur, which could be really serious ones.
I do this for future maintenance - if I now get into the "ignore warnings" mode for a job I will ignore any warnings in the future and would most certainly miss any new warnings that might occur, which could be really serious ones.
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
A 32-bit integer (int32) can not fit into a Decimal(8,0) column. These integers can have up to 10 digits - the largest integer is 2147483647.
That's why DataStage issues you with a warning. What you're trying to do may have catastrophic consequences for large enough integers (such as a segmentation violation).
That's why DataStage issues you with a warning. What you're trying to do may have catastrophic consequences for large enough integers (such as a segmentation violation).
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.
Do a "StringToDecimal(Right(field, )" within a transformer stage if you must squeeze it within the Number[8,0] field.
Yes, StringToDecimal. Within DataStage EE, Integer is interchangeable with String. Decimal is not.
To date, I have been able to eliminate ALL BUT ONE WARNING MESSAGE for my jobs. The one warning message? A Remote DB2 warning message that I am still trying to plug in.
Yes, I even fixed the partition warnings. And the column propagation warnings. There is absolutely no reason why you can not do what I did. It is simply good development practice.
Yes, StringToDecimal. Within DataStage EE, Integer is interchangeable with String. Decimal is not.
To date, I have been able to eliminate ALL BUT ONE WARNING MESSAGE for my jobs. The one warning message? A Remote DB2 warning message that I am still trying to plug in.
Yes, I even fixed the partition warnings. And the column propagation warnings. There is absolutely no reason why you can not do what I did. It is simply good development practice.