Bug #84777 Database Migration only partially successful
Submitted: 1 Feb 2017 16:34 Modified: 10 Dec 2018 20:54
Reporter: David Hodgkinson Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench: Migration Severity:S3 (Non-critical)
Version:6.3.6/6.3.10 OS:Ubuntu (16)
Assigned to: CPU Architecture:Any

[1 Feb 2017 16:34] David Hodgkinson 
Description:
Database was only partially migrated over UnixODBC(FreeTDS). From Linux SQL Server.

For example:

`ApolloData`.`tblAWAnalysts`:Copying 10 columns of 3193 rows from table [ApolloData].[dbo].[tblAWAnalysts]
16:12:58 [WRN][      copytable]: Forcing wchar_t but SQLWCHAR is of different type which shouldn't happen. Potential problems during migration may occur.
ERROR:`ApolloData`.`tblAWAnalysts`:Error during charset conversion of wstring: Success

Should I change data types in the columns of the source table?

How to repeat:
You will need a copy of my SQL Server database!
[1 Feb 2017 16:35] David Hodgkinson 
log output from mysql-workbench

Attachment: log.txt (text/plain), 11.22 KiB.
[1 Feb 2017 19:08] MySQL Verification Team 
Thank you for the bug report. Are you able to provide a test case with create table + insert data for Linux SQL Server which presents the same issue?. Thanks.
[2 Feb 2017 11:09] David Hodgkinson 
Sadly, without giving away the schema, no.

What do the error messages actually mean?
[28 Jun 2017 8:44] Martynas Jusevicius 
Is there a workaround for this issue? wbcopytables is unusable as it is.
[28 Jun 2017 9:12] Martynas Jusevicius 
I can provide schema examples that fail with this error when wbcopytables is invoked. Column name is not indicated in the error message, so I changed the names.

1 [WRN] message from this table:

  CREATE TABLE "X"."Y" 
   (	"A" NUMBER(38,0), 
	"B" NUMBER(38,0), 
	"C" VARCHAR2(100 CHAR), 
	"D" VARCHAR2(50 CHAR), 
	"E" NUMBER(38,0), 
	"F" NUMBER(38,0), 
	"G" NUMBER(38,0), 
	"H" NUMBER(5,2), 
	"I" NUMBER(38,0), 
	"J" DATE, 
	"K" DATE, 
	"L" NUMBER(38,0), 
	"M" VARCHAR2(20 CHAR), 
	"N" NUMBER(38,0)
   )

3 [WRN] messages from this table:

  CREATE TABLE "X"."Z" 
   (	"A" NUMBER(38,0), 
	"B" VARCHAR2(100 CHAR), 
	"C" VARCHAR2(100 CHAR), 
	"D" VARCHAR2(50 CHAR), 
	"E" VARCHAR2(20 CHAR), 
	"F" VARCHAR2(100 CHAR), 
	"G" VARCHAR2(100 CHAR), 
	"H" VARCHAR2(20 CHAR), 
	"I" TIMESTAMP (6), 
	"J" NUMBER(38,0), 
	"K" DATE, 
	"L" DATE, 
	"M" VARCHAR2(100 CHAR), 
	"N" DATE, 
	"O" DATE, 
	"P" VARCHAR2(255 CHAR), 
	"Q" DATE, 
	"R" VARCHAR2(20 CHAR), 
	"S" NUMBER(38,0), 
	"T" VARCHAR2(20 CHAR), 
	"U" VARCHAR2(20 CHAR), 
	"V" NUMBER(38,0), 
	"W" NUMBER(38,0)
   )

Using wbcopytables-bin CE (GPL) 6.3.6 CE build 511.
The source is Oracle Database 11g Express Edition Release 11.2.0.2.0 - 64bit Production, connected using Instant Client 12.2 and unixODBC 2.3.1.
[10 Dec 2018 20:54] Christine Cole 
Posted by developer:
 
Fixed as of the upcoming MySQL Workbench 8.0.14 release, and here's the changelog entry:

Some columns within a Microsoft SQL Server database table were not
migrated as expected. The operation returned an error when copying mixed
data types.

Thank you for the bug report.