Bug #107202 Error importing to MySql from an SqlLite database
Submitted: 3 May 2022 19:31 Modified: 11 May 2022 12:14
Reporter: Nuno Vilhena Santos Email Updates:
Status: Won't Fix Impact on me:
None 
Category:MySQL Workbench: Migration Severity:S1 (Critical)
Version:8.0.29 OS:Windows (Microsoft Windows 10 Pro)
Assigned to: CPU Architecture:Any
Tags: WBBugReporter

[3 May 2022 19:31] Nuno Vilhena Santos 
Description:
Attempted migration SqlLite fails using MySQL Workbench Migration Wizard.

Then in the Bulk Data Transfer get the message below:

Starting...
Prepare information for data copy...
Prepare information for data copy done
Determine number of rows to copy....
Counting number of rows in tables...
wbcopytables.exe --count-only --passwords-from-stdin --pythondbapi-source="sqlite3://'C:\Users\nunov\OneDrive\Ambiente de Trabalho\MyVideos116.db'" --source-rdbms-type=SQLite --source-timeout= --target-timeout=None --table-file=C:\Users\nunov\AppData\Local\Temp\tmpxctz0yn6
--table "MyVideos116"	"version"
18:52:33 [INF][      copytable]: --table "MyVideos116"	"bookmark"
18:52:33 [INF][      copytable]: --table "MyVideos116"	"settings"
18:52:33 [INF][      copytable]: --table "MyVideos116"	"stacktimes"
18:52:33 [INF][      copytable]: --table "MyVideos116"	"genre"
18:52:33 [INF][      copytable]: --table "MyVideos116"	"genre_link"
18:52:33 [INF][      copytable]: --table "MyVideos116"	"country"
18:52:33 [INF][      copytable]: --table "MyVideos116"	"country_link"
18:52:33 [INF][      copytable]: --table "MyVideos116"	"movie"
18:52:33 [INF][      copytable]: --table "MyVideos116"	"actor"
18:52:33 [INF][      copytable]: --table "MyVideos116"	"actor_link"
18:52:33 [INF][      copytable]: --table "MyVideos116"	"director_link"
18:52:33 [INF][      copytable]: --table "MyVideos116"	"writer_link"
18:52:33 [INF][      copytable]: --table "MyVideos116"	"path"
18:52:33 [INF][      copytable]: --table "MyVideos116"	"files"
18:52:33 [INF][      copytable]: --table "MyVideos116"	"tvshow"
18:52:33 [INF][      copytable]: --table "MyVideos116"	"episode"
18:52:33 [INF][      copytable]: --table "MyVideos116"	"tvshowlinkpath"
18:52:33 [INF][      copytable]: --table "MyVideos116"	"movielinktvshow"
18:52:33 [INF][      copytable]: --table "MyVideos116"	"studio"
18:52:33 [INF][      copytable]: --table "MyVideos116"	"studio_link"
18:52:33 [INF][      copytable]: --table "MyVideos116"	"musicvideo"
18:52:33 [INF][      copytable]: --table "MyVideos116"	"streamdetails"
18:52:33 [INF][      copytable]: --table "MyVideos116"	"sets"
18:52:33 [INF][      copytable]: --table "MyVideos116"	"seasons"
18:52:33 [INF][      copytable]: --table "MyVideos116"	"art"
18:52:33 [INF][      copytable]: --table "MyVideos116"	"tag"
18:52:33 [INF][      copytable]: --table "MyVideos116"	"tag_link"
18:52:33 [INF][      copytable]: --table "MyVideos116"	"rating"
18:52:33 [INF][      copytable]: --table "MyVideos116"	"uniqueid"

Active code page: 65001

ERROR: Determine number of rows to copy: Error getting row count from source tables, wbcopytables exited with code 3221225477
Failed

How to repeat:
repeating the process again, i will send the database.
[3 May 2022 19:33] Nuno Vilhena Santos 
Database file with data to import to MySql

Attachment: MyVideos116.db (application/octet-stream, text), 540.00 KiB.
[3 May 2022 19:35] Nuno Vilhena Santos 
log file from the Workbench: Current version given by meta info is: 8.0.29

Attachment: wb.log (application/octet-stream, text), 105.16 KiB.
[11 May 2022 12:14] MySQL Verification Team 
Hello,

Thank you for the bug report.
Verified as described.

Regards,
Ashwini Patil
[11 May 2022 12:15] MySQL Verification Team 
8.0.29 test results

Attachment: 107202_test_results.PNG (image/png, text), 256.45 KiB.
[14 Sep 18:06] Omer Barnir 
Posted by developer:

This issue applies to the legacy MySQL Workbench 8.x implementation that is no longer supported or maintained.
MySQL Workbench 26.7 is a complete rewrite using a new technology stack and does not use the affected legacy implementation.
Therefore, this issue is not applicable to the current MySQL Workbench product and as such is closed.