# 5.6.17-66.0 performance schema issues

**URL:** <https://forums.percona.com/t/5-6-17-66-0-performance-schema-issues/3544>\
**Category:** Percona Server for MySQL 5.6\
**Created:** [June 12, 2014, 2:22am UTC](https://forums.percona.com/t/5-6-17-66-0-performance-schema-issues/3544 "2014-06-12T02:22:05Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![WheresWardy](https://avatars.discourse-cdn.com/v4/letter/w/db5fbb/32.png) [@WheresWardy](https://forums.percona.com/u/WheresWardy)\
**Post date:** [June 12, 2014, 2:22am UTC](https://forums.percona.com/t/5-6-17-66-0-performance-schema-issues/3544/1 "2014-06-12T02:22:05Z")

</div>

I’ve just upgraded a server from Percona Server 5.6.16-64.1 to 5.6.17-66.0 and got the following error in the log for every performance\_schema table:

```auto

2014-06-12 08:29:14 21012 [ERROR] /usr/sbin/mysqld: Incorrect information in file: './performance_schema/accounts.frm'
2014-06-12 08:29:14 21012 [ERROR] Native table 'performance_schema'.'accounts' has the wrong structure

```

I ran mysql\_upgrade to see if this would solve the issue, which again produced the following error for every performance\_schema table:

```auto

2014-06-12 08:29:39 21012 [ERROR] /usr/sbin/mysqld: Incorrect information in file: './performance_schema/accounts.frm'

```

After which, whenever I try and read from a performance\_schema table in MySQL I get the following error:

```auto

[localhost] (root&#64;performance_schema) > SELECT * FROM accounts LIMIT 1;
ERROR 1682 (HY000): Native table 'performance_schema'.'accounts' has the wrong structure

```

There were no configuration changes during the upgrade, just a yum update on RHEL 6.5. Has this issue been reproduced at all? I’m not sure how to go about fixing this now, other than a downgrade to 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:** [June 13, 2014, 8:02am UTC](https://forums.percona.com/t/5-6-17-66-0-performance-schema-issues/3544/2 "2014-06-13T08:02:17Z")

</div>

Hi,

Thanks for reporting this to us.  
I’ve reported this as a bug, you may get updates from this link [url][https://bugs.launchpad.net/percona-server/+bug/1329772[/url]](https://bugs.launchpad.net/percona-server/+bug/1329772%5B/url%5D)

---

<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:** [June 17, 2014, 2:31am UTC](https://forums.percona.com/t/5-6-17-66-0-performance-schema-issues/3544/3 "2014-06-17T02:31:19Z")

</div>

I’ve tried this out on a VM and it looks like you have to do the following steps:

1. run # mysql\_upgrade --upgrade-system-tables
2. restart mysql server after mysql\_upgrade is ok
3. test with mysql\> select \* from performance\_schema.accounts limit 1;

Let me know if this solves it.

---

<div class="post-metadata">

**Author:** ![WheresWardy](https://avatars.discourse-cdn.com/v4/letter/w/db5fbb/32.png) [@WheresWardy](https://forums.percona.com/u/WheresWardy)\
**Post date:** [June 17, 2014, 2:34am UTC](https://forums.percona.com/t/5-6-17-66-0-performance-schema-issues/3544/4 "2014-06-17T02:34:53Z")

</div>

I can confirm that that solves the issue.