Getting "ERROR 1033 (HY000): Incorrect information in file: '.*.frm'" after upgrading to 5.1.54-12.5

[Pavel Shevaev]

Folks, I upgraded my previous Percona server installation(5.1.52) to
the new one and now I'm getting this error while accessing some
tables. The old installation worked just fine.

I tried to stop the server in a clean way, reset ib_logfile files and
restart it but all in vain. I'm still getting this error :(

At the moment I simply don't know what to do. Please help.

--
Best regards, Pavel

[Pavel Shevaev]

> At the moment I simply don't know what to do. Please help.

Sorry, I'm replying to myself but here is what I did: fortunately I
had table creation sql and I simply recreated the new tables with
"new_" prefix and then copied their *.frm files over the corrupted
ones. So far everything works just fine... I'm still wondering why
this could happen :(

--
Best regards, Pavel

[Baron Schwartz]

Hi Pavel,

This is usually because InnoDB failed to start. Check your server's log
files, and check SHOW ENGINES.

[Pavel Shevaev]

Here is the part of the error.log starting from the moment of the new
Percona server installation till the very first .frm related error:

110217 1:34:29 [Note] /usr/sbin/mysqld: Normal shutdown

110217 1:34:29 [Note] Event Scheduler: Purging the queue. 0 events
110217 1:34:29 InnoDB: Starting shutdown...
110217 1:36:15 InnoDB: Shutdown completed; log sequence number 280373653372
110217 1:36:15 [Note] /usr/sbin/mysqld: Shutdown complete

110217 1:36:23 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Compressed tables use zlib 1.2.3.3
110217 1:36:23 InnoDB: Initializing buffer pool, size = 16.0G
110217 1:36:24 InnoDB: Completed initialization of buffer pool
110217 1:36:24 InnoDB: highest supported file format is Barracuda.
110217 1:36:26 Percona XtraDB (http://www.percona.com) 1.0.14-12.5
started; log sequence number 280373653372
110217 1:36:26 InnoDB: Starting shutdown...
110217 1:36:27 InnoDB: Shutdown completed; log sequence number 280373653372
110217 1:36:27 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Compressed tables use zlib 1.2.3.3
110217 1:36:27 InnoDB: Initializing buffer pool, size = 16.0G
110217 1:36:28 InnoDB: Completed initialization of buffer pool
110217 1:36:28 InnoDB: highest supported file format is Barracuda.
110217 1:36:30 Percona XtraDB (http://www.percona.com) 1.0.14-12.5
started; log sequence number 280373653372
ERROR: 1064 You have an error in your SQL syntax; check the manual
that corresponds to your MySQL server version for the right syntax to
use near 'ALTER TABLE user
ADD column Show_view_priv enum('N','Y') CHARACTER SET utf8 NOT ' at line 1
110217 1:36:30 [ERROR] Aborting

110217 1:36:30 InnoDB: Starting shutdown...
110217 1:36:32 InnoDB: Shutdown completed; log sequence number 280373653372
110217 1:36:32 [Note] /usr/sbin/mysqld: Shutdown complete

110217 1:36:32 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Compressed tables use zlib 1.2.3.3
110217 1:36:32 InnoDB: Initializing buffer pool, size = 16.0G
110217 1:36:33 InnoDB: Completed initialization of buffer pool
110217 1:36:33 InnoDB: highest supported file format is Barracuda.
110217 1:36:34 Percona XtraDB (http://www.percona.com) 1.0.14-12.5
started; log sequence number 280373653372
110217 1:36:34 InnoDB: Starting shutdown...
110217 1:36:35 InnoDB: Shutdown completed; log sequence number 280373653372
110217 1:36:35 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Compressed tables use zlib 1.2.3.3
110217 1:36:35 InnoDB: Initializing buffer pool, size = 16.0G
110217 1:36:36 InnoDB: Completed initialization of buffer pool
110217 1:36:36 InnoDB: highest supported file format is Barracuda.
110217 1:36:37 Percona XtraDB (http://www.percona.com) 1.0.14-12.5
started; log sequence number 280373653372
ERROR: 1050 Table 'plugin' already exists
110217 1:36:37 [ERROR] Aborting

110217 1:36:37 InnoDB: Starting shutdown...
110217 1:36:39 InnoDB: Shutdown completed; log sequence number 280373653372
110217 1:36:39 [Note] /usr/sbin/mysqld: Shutdown complete

110217 1:36:39 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Compressed tables use zlib 1.2.3.3
110217 1:36:39 InnoDB: Initializing buffer pool, size = 16.0G
110217 1:36:40 InnoDB: Completed initialization of buffer pool
110217 1:36:40 InnoDB: highest supported file format is Barracuda.
110217 1:36:41 Percona XtraDB (http://www.percona.com) 1.0.14-12.5
started; log sequence number 280373653372
110217 1:36:41 [Warning] 'user' entry 'ro...@w112.wahome.ru' ignored
in --skip-name-resolve mode.
110217 1:36:41 [Note] Event Scheduler: Loaded 0 events
110217 1:36:41 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.1.54-rel12.5-log' socket: '/var/run/mysqld/mysqld.sock'
port: 3306 (Percona Server (GPL), 12.5 , Revision 188)
110217 1:36:42 [ERROR] /usr/sbin/mysqld: Incorrect information in
file: '.xxxxxxxxx.frm'

Yep, there are some strage errors but I don't know why they happened.
I simply followed the standard upgrade procedure using aptitude....

--
Best regards, Pavel

[Baron Schwartz]

Hi Pavel,

It looks to me as though there were multiple MySQL instances running
simultaneously. Buggy init scripts or operator impatience are usually
the cause of this in my experience.

[Pavel Shevaev]

I guess you are right, thanks. Anyway it's good I could fix it, I got
really scared at first, it happened on a production database server...

--
Best regards, Pavel