Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
1 Solution
Accepted Solutions
Hi xdshi,
i did some further investigation, it pointed out i made a mistake on the mssql -> mssql mapping, the string had too much characters so the error message was correct.
Concerning mssql -> oracle it was a bit trickier. The destination oracle database (i had no influence on the schema) has varchar fields with exactly the same size as the source (i thought
) but the was a small difference is saw when i inspected the oracle schema:
the definition of the fields was varchar (254 BYTE) which means the field has space for 254 BYTE. Since we are working with multibyte characters (ÄÖÜ etc.) we need 4 bytes space for saving it in the database.
So my solution is to count the occurences of these multibyte chars in the source field and cut the string (len - 4*occurences). I'm sure it's not the bust way, but it works for now
Regards,
M
i did some further investigation, it pointed out i made a mistake on the mssql -> mssql mapping, the string had too much characters so the error message was correct.
Concerning mssql -> oracle it was a bit trickier. The destination oracle database (i had no influence on the schema) has varchar fields with exactly the same size as the source (i thought
) but the was a small difference is saw when i inspected the oracle schema:
the definition of the fields was varchar (254 BYTE) which means the field has space for 254 BYTE. Since we are working with multibyte characters (ÄÖÜ etc.) we need 4 bytes space for saving it in the database.
So my solution is to count the occurences of these multibyte chars in the source field and cut the string (len - 4*occurences). I'm sure it's not the bust way, but it works for now
Regards,
M
Hi xdshi,
i did some further investigation, it pointed out i made a mistake on the mssql -> mssql mapping, the string had too much characters so the error message was correct.
Concerning mssql -> oracle it was a bit trickier. The destination oracle database (i had no influence on the schema) has varchar fields with exactly the same size as the source (i thought) but the was a small difference is saw when i inspected the oracle schema:
the definition of the fields was varchar (254 BYTE) which means the field has space for 254 BYTE. Since we are working with multibyte characters (ÄÖÜ etc.) we need 4 bytes space for saving it in the database.
So my solution is to count the occurences of these multibyte chars in the source field and cut the string (len - 4*occurences). I'm sure it's not the bust way, but it works for now
Regards,
M
i did some further investigation, it pointed out i made a mistake on the mssql -> mssql mapping, the string had too much characters so the error message was correct.
Concerning mssql -> oracle it was a bit trickier. The destination oracle database (i had no influence on the schema) has varchar fields with exactly the same size as the source (i thought
) but the was a small difference is saw when i inspected the oracle schema:
the definition of the fields was varchar (254 BYTE) which means the field has space for 254 BYTE. Since we are working with multibyte characters (ÄÖÜ etc.) we need 4 bytes space for saving it in the database.
So my solution is to count the occurences of these multibyte chars in the source field and cut the string (len - 4*occurences). I'm sure it's not the bust way, but it works for now
Regards,
M
Hi xdshi,
i think the problem in my case is a bad schema design, which i sadly can't change. But it might be a cool feature if the encoding can be set in the output elements, although i know encoding handling using java Strings is a bit tricky
Regards,
M
i think the problem in my case is a bad schema design, which i sadly can't change. But it might be a cool feature if the encoding can be set in the output elements, although i know encoding handling using java Strings is a bit tricky
Regards,
M