Writing the WVARCHAR column into a VARCHAR database column
Moderators: chulett, rschirm, roy
Writing the WVARCHAR column into a VARCHAR database column
Hi all,
I have job that extracts data from DB2 and loads into MySQL using IBM Data Direct ODBC Driver.After successful completion of the job,I got the following error message:
"Writing the WVARCHAR column into a VARCHAR database column can cause data loss or corruption due to character set conversions.".
I strongly feel problem is with the table creation,
I tried using UTF8 but the same problem persists.
So Please let me know any solution for the above issue.
I have job that extracts data from DB2 and loads into MySQL using IBM Data Direct ODBC Driver.After successful completion of the job,I got the following error message:
"Writing the WVARCHAR column into a VARCHAR database column can cause data loss or corruption due to character set conversions.".
I strongly feel problem is with the table creation,
I tried using UTF8 but the same problem persists.
So Please let me know any solution for the above issue.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
warning across all jobs
This issue persists with respect to environment and persists across all the jobs in different environment,
I tested in local environment it works fine.
But in client environment it throws the above warning
Locally i faced this issue but was solved by appending utf 8 to create table, but the same does not work in client side.
Tried removing that too, but same result
I tested in local environment it works fine.
But in client environment it throws the above warning
Locally i faced this issue but was solved by appending utf 8 to create table, but the same does not work in client side.
Tried removing that too, but same result
Did you follow Ray's suggestion. I haven't been to a site yet where this approach didn't work.
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
I haven't looked into the database DDL scripts, but if you keep all of your databases in the same character set plus do the same for DataStage then no conversion will be necessary and correspondingly no warnings will be produced.
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
Hi all,
I developed a job that extract the data from source and loads into target without any transformation logic.But i used RCP in my job.After successful completion,I got the following warning message
"Writing the WVARCHAR column into a VARCHAR database column can cause data loss or corruption due to character set conversions.".How to solve this warning
I developed a job that extract the data from source and loads into target without any transformation logic.But i used RCP in my job.After successful completion,I got the following warning message
"Writing the WVARCHAR column into a VARCHAR database column can cause data loss or corruption due to character set conversions.".How to solve this warning
In this case you ARE converting from WVarChar to VarChar, and since you are doing a generic job using RCP you cannot get rid of the message. But you can deprecate the warning message to an informational one either at a job level or at a project level using the DataStage message handlers.
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
I ran across the same issue, and tried conversion in a Transformer using UStringToString to no avail. I then realized that column metadata captured in my source data had the column in question declared as VarChar(10) non-Unicode. Adding Unicode to the Extended Properties for the offending column fixed it for me.
The middle of every successful project looks like a disaster -- Rosabeth Moss Cantor