Hi all,
We have a column defined as a CHAR (2) in Sybase, but when I read the column as a CHAR(2) in Datastage, I get the below mentioned warning .
Implicit conversion from source type "string[4]" to result type "string[2]"
I know that Sybase uses 2 bytes for a single CHAR value but how to avoid this warning. I get this warning only in the Sybase Enterprise stage, If I use the Sybase OCI stage, I don't get any warnings. Please let me know if there is a way apart from the message handler to avoid these issues.
I don't want to read the column as a CHAR (4) as that would have issues in my target as we use SPACE as the padchar value.
Thanks in advance.
Implicit conversion from source type-Sybase Enterprise Stage
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
If you have Unicode (or UTF, etc.) enabled, Char(2) is stored as four bytes in Sybase. In that case, DataStage table import reports the storage requirements as string[4].
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.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact: