# Incorrect definition of table mysql.proc

**URL:** <https://forums.percona.com/t/incorrect-definition-of-table-mysql-proc/4189>\
**Category:** Percona XtraDB Cluster 5.x\
**Created:** [April 27, 2015, 8:42pm UTC](https://forums.percona.com/t/incorrect-definition-of-table-mysql-proc/4189 "2015-04-27T20:42:06Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![umarzuki](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/umarzuki/32/1064_2.png) [@umarzuki](https://forums.percona.com/u/umarzuki)\
**Post date:** [April 27, 2015, 8:42pm UTC](https://forums.percona.com/t/incorrect-definition-of-table-mysql-proc/4189/1 "2015-04-27T20:42:06Z")

</div>

Restoring all databases from MariaDB 10 to Percona Xtradb Cluster, I saw an error on mysql.log on one of db nodes as below

[ERROR] Incorrect definition of table mysql.proc: expected column ‘definer’ at position 11 to have type char(77), found type char(141).

percona-xtradb-cluster-galera-3.x  
3.9.3494.trusty

Do I simply change char(77) to char(141) on one of the node or there’s a few extra steps?

---

<div class="post-metadata">

**Author:** ![jaime](https://avatars.discourse-cdn.com/v4/letter/j/4bbf92/32.png) [@jaime](https://forums.percona.com/u/jaime)\
**Post date:** [April 27, 2015, 10:38pm UTC](https://forums.percona.com/t/incorrect-definition-of-table-mysql-proc/4189/2 "2015-04-27T22:38:29Z")

</div>

Hi umarzuki,  
It seems like MariaDB’s system tables are not compatible with Percona XtraDB Cluster. I would advise instead to reload your dump of all the data from mysqldump, but do not include the mysql database.

---

<div class="post-metadata">

**Author:** ![umarzuki](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/umarzuki/32/1064_2.png) [@umarzuki](https://forums.percona.com/u/umarzuki)\
**Post date:** [April 28, 2015, 1:18am UTC](https://forums.percona.com/t/incorrect-definition-of-table-mysql-proc/4189/3 "2015-04-28T01:18:11Z")

</div>

How do I do that?

Delete mysql db then restore from mysql db backup from another percona server?

---

<div class="post-metadata">

**Author:** ![jrivera](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/jrivera/32/13_2.png) [@jrivera](https://forums.percona.com/u/jrivera)\
**Post date:** [April 28, 2015, 11:20pm UTC](https://forums.percona.com/t/incorrect-definition-of-table-mysql-proc/4189/4 "2015-04-28T23:20:29Z")

</div>

You can either create a new dump taken from the MariaDB 10 cluster node excluding the ‘mysql’ database. Use either of the following workaround:  
[url][http://datacharmer.blogspot.com/2012/04/few-hacks-to-simulate-mysqldump-ignore.html[/url]](http://datacharmer.blogspot.com/2012/04/few-hacks-to-simulate-mysqldump-ignore.html%5B/url%5D)  
[url][http://ronaldbradford.com/blog/i-want-a-mysqldump-ignore-database-option-2012-04-18/[/url]](http://ronaldbradford.com/blog/i-want-a-mysqldump-ignore-database-option-2012-04-18/%5B/url%5D)

OR

Using your existing mysqldump file (if you have the latest one), use an open source tool - mysqldumpsplitter, to ‘split’ the dump file and only extract the databases you need to reload to the new cluster.  
[url][https://github.com/kedarvj/mysqldumpsplitter[/url]](https://github.com/kedarvj/mysqldumpsplitter%5B/url%5D)

You could try to do an ALTER TABLE on mysql.proc and see if that works.