(SAP?) UTF-8 Encoding problem only on Server Console not in Studio (Data too long error)

[Anonymous]

Hi, i have this problem with tMysqlOutput.

tMysqlOutput_3 Data truncation: Data too long for column 'APPLICATION' at row 85

I have set these additional JDBC parameters:

noDatetimeStringSync=true&useUnicode=true&characterEncoding=utf8

and the problem is resolved in the Studio but on server continues to persist.

[Anonymous]

---

@MZ wrote:

Could the error be due to the sap component as well as the mysql component?

---

OMG 

Ok the problem is on the sap component because also eliminating the tMysqlOutput component the encoding is wrong on TAC.

Studio:

|303  |TR prel. a div.     |TF rem.fm.stor.to pl|UL Auslagern an Werk|TR Sortie -> div.   |

TAC:

303|TR prel. a div.|TF rem.fm.stor.to pl|UL Auslagern an Werk|TR Sortie -> div.

What happens? 

[Anonymous]

Hello,

With your subscription solution, would you mind creating a case on talend support portal so that we can give you a remote assistance(webex) on your issue through support cycle with priority.

Please log on to the Support portal https://login.talend.com/support-login.php

Many thanks.

Best regards

Sabrina

[Anonymous]

I think that this Jira may be related: https://jira.talendforge.org/browse/TDI-35499

It seems to have been corrected in Studio from 6.2.1, but it's possible we may not have patched the Job Server. We will look into it.

Thanks,

Arthur

[Anonymous · Accepted solution]

Hi all, with the support team we realized that the cmdline is executed by default in 32-bit.

We modified the commandline.bat file to run the 64-bit cmdline.

Thank you.

Manuel

[Anonymous]

---

@MZ wrote:

Hi all, with the support team we realized that the cmdline is executed by default in 32-bit.

We modified the commandline.bat file to run the 64-bit cmdline.

Thank you.

Manuel

---

Hello Manuel,

Thanks for your feedback and sharing the solution here.

Best regards

Sabrina

T