Hi,
I am getting the following error:
ODBC_PR_CUSTOMER: When checking operator: When binding output interface field "PARTY_NAME" to field "PARTY_NAME": Implicit conversion from source type "ustring[max=50]" to result type "string[max=255]": Converting ustring to string using codepage UTF-8.
The source and target columns are VARCHAR but of different lengths.
I dont understand why it is saying USTRING to string.
How to resolve this issue?
Thanks in advance.
Deepa
"ustring[max=50]" to result type "string[max=
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 95
- Joined: Thu Sep 24, 2009 12:15 am
- Location: India
-
- Participant
- Posts: 334
- Joined: Fri Dec 01, 2006 5:17 am
- Location: Texas
Re: "ustring[max=50]" to result type "string[
Hi,deepa_shenoy wrote:Hi,
I am getting the following error:
ODBC_PR_CUSTOMER: When checking operator: When binding output interface field "PARTY_NAME" to field "PARTY_NAME": Implicit conversion from source type "ustring[max=50]" to result type "string[max=255]": Converting ustring to string using codepage UTF-8.
The source and target columns are VARCHAR but of different lengths.
I dont understand why it is saying USTRING to string.
How to resolve this issue?
Thanks in advance.
Deepa
I guess ... not sure ... in source metadata you are using "PARTY_NAME" column as Unicode --Varchar2(50).
Just remove the unicode and run the job ...
Thanks!!
http://findingjobsindatastage.blogspot.com/
Theory is when you know all and nothing works. Practice is when all works and nobody knows why. In this case we have put together theory and practice: nothing works. and nobody knows why! (Albert Einstein)
Theory is when you know all and nothing works. Practice is when all works and nobody knows why. In this case we have put together theory and practice: nothing works. and nobody knows why! (Albert Einstein)
-
- Participant
- Posts: 95
- Joined: Thu Sep 24, 2009 12:15 am
- Location: India
-
- Participant
- Posts: 95
- Joined: Thu Sep 24, 2009 12:15 am
- Location: India
In job 1, I am loading Table 1 to Table 2. In Table 2 all columns have been declared VARCHAR and all data is loaded successfully.
In job 2, I am loading Table 3 from the same Table 2. Both have all columns declared as VARCHAR. In this job 2 its throwing this error of implicit conversion from ustring to string.
If there were Unicode or special characters, it should have thrown the same warning for Job 1 too right?
In job 2, I am loading Table 3 from the same Table 2. Both have all columns declared as VARCHAR. In this job 2 its throwing this error of implicit conversion from ustring to string.
If there were Unicode or special characters, it should have thrown the same warning for Job 1 too right?
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact: