Not the answer you need?
Register and ask your own question!

Schema mismatch when loading innobackupex backup of Percona 5.6 server to another

Melvin.RossMelvin.Ross EntrantInactive User Role Beginner
I'm attempting to restore an individual innodb table from one Percona 5.6 server to another, though the source database was originally Percona 5.5.

The command used to back up the original server was :
innobackupex --socket=/mysql/other/mysql.sock --user=xx --password=xx --no-timestamp /mysql/backup/bacula/

After the backup was complete, it was prepared with the following command:
innobackupex --socket=/mysql/other/mysql.sock --apply-log --export /mysql/backup/bacula/
I then copy a tables ibd, cfg, and exp files into the data dir, and change the owner to mysql.

I then discard the tablespace. If I import the tablespace with the cfg file present, I get : Schema mismatch (Column a precise type mismatch.) on datetime column

I can delete the cfg file and import the tablespace without the schema verification and it imports, but there is certainly something wrong with the data. The data types aren't the same so all data up until a datetime field are just fine, but from the datetime filed on the data is actually misaligned between the columns. MySQL changed how datatime columns are stored in MySQL 5.6, and the table was originally created on a MySQL 5.5 server. That being said, this table is truncated and reloaded every day.

Any ideas on what I have to do to get the transportable tablespace working?

Comments

Sign In or Register to comment.

MySQL, InnoDB, MariaDB and MongoDB are trademarks of their respective owners.
Copyright ©2005 - 2020 Percona LLC. All rights reserved.