MySQL Forums
Forum List  »  Microsoft SQL Server

Re: For the same MSSQL table migration script works in CentOS 6.6, but fails partially in CentOS 7.2, 7.3 and 7.4
Posted by: Jacob Nikom
Date: February 23, 2018 01:36PM

Hello Milosz,

Thank you for looking into my case.

>> So what version of WB do you use?

On CentOS 7.4.1708 I used WB 6.3.10 and 6.3.9

I used the latest freeTDS drivers
from http://www.freetds.org/files/stable/freetds-1.00.82.tar.gz
I think the fact that 90% of the table migrated correctly signifies
that the drivers' installation was successful.

Unfortunately, the WB 6.3.10 had different issue - it crashed immediately
after the start, so Scott Noyes gave me hotfix patch for that version.

Frankly speaking, I am not sure the bug has something to do with WB per se.
It looks like it has more to do with interaction of freeTDS drivers with
operating system. The reason for that is that I am migrating my data without
any WB running. I was just executing BASH migration script with
wbcopytables-bin executable only.

Does wbcopytables-bin depend upon WB in any way?

If yes, it means that this bug could have something to do with WB. If it
is not, I think it could be only freeTDS and CentOS interation issue.

I also think there is more than one bug related to that problem.

The bug that was addressed in WB 6.3.9 is the following:
https://dev.mysql.com/doc/relnotes/workbench/en/wb-news-6-3-9.html

"Having a single quotation mark (') in the text field of a table caused the
MySQL Schema Transfer wizard to fail. (Bug #24978403, Bug #83616)"

I think in my case the bug is different. It is more related to character
set conversion according to the error message from wbcopytables-bin:
"Error during charset conversion of wstring"

What surprises me that this error does not exist on CentOS 6.6. Exactly the
same BASH script works flawlessly on CentOS 6. It means that it is pure
regression bug. It could be result of the change of libraries.

According to Perry Harrington (support engineer at Oracle/MySQL) it could be
that CentOS 6 and 7 use different libraries for handling utf-8 characters. He
mentioned libiodbc.x86_64.

Did you change those libraries when you move your code from CentOS 6 to CentOS 7?

Best regards,

Jacob Nikom

Options: ReplyQuote




Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.