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

Orphan InnoDB entries after renaming table

msuticmsutic EntrantCurrent User Role Novice

I have renamed table to another database:
mysql> create database test_rename;
Query OK, 1 row affected (0.00 sec)

mysql> rename table test.pages to test_rename.pages;
Query OK, 0 rows affected (0.00 sec)

Then uninstalled existing 5.6.41 version and installed performed installation of 5.7 version.
$ sudo apt-get remove percona-xtrabackup* percona-xtradb-cluster*
$ sudo apt-get install percona-xtradb-cluster-57

In error log I receive ERRORS for orphan entries:
2019-01-07T21:42:21.105554Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2019-01-07T21:42:21.105631Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2019-01-07T21:42:21.105785Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2019-01-07T21:42:21.105886Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: './test/pages.ibd' OS error: 71

Everything seems to be OK with the table.

Is this expected behavior (to receive such errors) when you rename table to another database?

Thank you for the answer.

Best regards,
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.