Bug #30093 | MySQL Migration direct from mysqlserver to another .. | ||
---|---|---|---|
Submitted: | 27 Jul 2007 9:43 | Modified: | 27 Jul 2007 12:50 |
Reporter: | paul sanz | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Migration Toolkit | Severity: | S3 (Non-critical) |
Version: | 5.0 | OS: | Windows (xp pro sp2) |
Assigned to: | CPU Architecture: | Any | |
Tags: | MySQL Migration toolkit .. Plan: Bulk Transfer - gets suck doesnt transfer data |
[27 Jul 2007 9:43]
paul sanz
[27 Jul 2007 9:50]
Sveta Smirnova
Thank you for the report. Please indicate accurate version of MySQL Migration Toolkit you use.
[27 Jul 2007 12:00]
paul sanz
Hi group FYI .. problem resolution I realised that this is not a bug yet a problem of access control and permissions. I suggest that you use an admin user with write and read permission. i was as a recap, i was migrating an exisiting mysql server db (Win vista) to mysql server (fedora 7) and i got many grant drop errors and when transfering data the objects were created but did not transfer any data. Note: I recomend you create the db with its permissions and users needed then migrate but becareful if you do create the db first, you must edit the "sql create script of selected objects in scheme creation and erase DROP VIEW IF EXISTS `dbname`.`tablename`;" apply changes and recreate objects. Next! hope this will help other novices like myself Paul System Admin
[27 Jul 2007 12:50]
Sveta Smirnova
Thank you for the feedback. According to last comment I'll close the report as "Not a Bug"