# Severe problems migrating MySQL/Windows to Percona/Linux **URL:** \ **Category:** Other MySQL® Questions\ **Created:** [February 17, 2012, 12:00pm UTC](https://forums.percona.com/t/severe-problems-migrating-mysql-windows-to-percona-linux/1764 "2012-02-17T12:00:44Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![maurizio](https://avatars.discourse-cdn.com/v4/letter/m/9de053/32.png) [@maurizio](https://forums.percona.com/u/maurizio)\ **Post date:** [February 17, 2012, 12:00pm UTC](https://forums.percona.com/t/severe-problems-migrating-mysql-windows-to-percona-linux/1764/1 "2012-02-17T12:00:44Z")
Hi, today I migrated a server from Windows to Linux. The main reason for this step was we want to switch to Percona Server and currently it is available only for Linux. We migrated the data at binary level and added lower\_case\_table\_names=1 to the my.cnf. The Percona Server (5.5.20) starts and shows all tables. Unpartitioned tables can be accessed without any problems. But we have some very big partitioned tables. These are listed by “SHOW TABLES” but cannot be accessed. Searching the web for solutions I found this bug report: [URL][MySQL Bugs: #47764: partitioned innodb tables can't be moved directly from windows to linux](http://bugs.mysql.com/bug.php?id=47764%5B/URL%5D) It is a MySQL/Innodb bug due to inconsistent table name normalisation. Seems like a very small code change could fix this problem. Could you please fix it in Percona Server or provide a patch? This would make the migration from Windows/MySQL to Percona possible for many others or at least facilitate it. I really need to take this server productive and there seems to be no workaround. Rebuilding the tables is not feasible due to their very big size. Thank you very much! ---
**Author:** ![xaprb](https://avatars.discourse-cdn.com/v4/letter/x/49beb7/32.png) [@xaprb](https://forums.percona.com/u/xaprb)\ **Post date:** [February 17, 2012, 3:14pm UTC](https://forums.percona.com/t/severe-problems-migrating-mysql-windows-to-percona-linux/1764/2 "2012-02-17T15:14:01Z")
This is something that could be fixed under a paid support contract. Understand that even things that look like small changes can be very expensive: fixing and properly testing a bug requires a lot of work and analysis of related source code. So this is unlikely to be something we would fix unless a paying customer is affected.