Bug #14595 | Migration report confirms data transfer however tables are empty | ||
---|---|---|---|
Submitted: | 2 Nov 2005 23:03 | Modified: | 5 Dec 2005 13:38 |
Reporter: | Alphonse Hoge | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Migration Toolkit | Severity: | S3 (Non-critical) |
Version: | 1.0.20-rc | OS: | Windows (Win XP) |
Assigned to: | CPU Architecture: | Any |
[2 Nov 2005 23:03]
Alphonse Hoge
[9 Nov 2005 0:13]
MySQL Verification Team
Why you think it is a bug of MySQL Migration Toolkit if you know that can't access the sysobj which need the user and password required for not to get permission denied. ? Looks to me an expected behavior. I am able for to migrate Access DB without any problems when I have the required privileges. Thanks in advance.
[10 Nov 2005 11:08]
Alphonse Hoge
Hi Miguel As I mentioned in the issue I know there is problem that has to be resolved. What is misleading is that the migration report "data bulk transfer" section clearly states that data was transfered 360 row(s) transfered. 2069 row(s) transfered. 842 row(s) transfered. etc etc and I therefore expected data to be present in the tables.
[21 Nov 2005 23:09]
Fred Tremblay
I have a similar problem. I am attempting to migrate a MS SQL Server 2000 DB (Development Version) to MySQL 5.0 using the MySQL Migration Toolkit (Winows XP). Several of the tables are empty after the process is complete. In each case the message is as follows with specific references to the table and column. The column data type in question is floating point in SQL Server and no mapping errors are given during the migration process. In the case of this table the message indicates that 86 rows were transfered, but zero rows actually were transfered. `E-T_LeadsApp_dbo`.`ET_Leads_Data_Import` ----------------------------------------- Data truncation: Out of range value adjusted for column 'LeadsRating' at row 3 86 row(s) transfered.
[22 Nov 2005 20:06]
Jorge del Conde
This is indeed a bug. MT is incorrectly reporting that the data migration completed successfully.
[24 Nov 2005 11:47]
Hari Kumar
I am using win2k and a MS Access db. After migration the report states that around half of the rows of the original table were transferred and because of a duplicate key it could not continue. (?) But the tranferred table doesn't show any row.
[5 Dec 2005 13:38]
Michael G. Zinner
Thank you for your bug report. This issue has been committed to our source repository of that product and will be incorporated into the next release. If necessary, you can access the source repository and build the latest available version, including the bugfix, yourself. More information about accessing the source trees is available at http://www.mysql.com/doc/en/Installing_source_tree.html