Table performance schema session variables doesn t exist

Question

After upgrading MySQL to 5 7 8-rc and loging to server I got error   Table  performance schema session variables  doesn t exist   I can t find any solution for this  Can you help

User · Answer

mysql -u app -p mysql gt  set   global show compatibility 56 ON    as per http   bugs mysql com bug php id 78159 worked for me

User · Answer

If  while using the mysql upgrade -u root -p --force command You get this error   Could not create the upgrade info file   var lib mysql mysql upgrade info  in the MySQL Servers datadir  errno  13   just add the sudo before the command  That worked for me  and I solved my problem  So  it s  sudo mysql upgrade -u root -p --force

User · Answer

The mysql upgrade worked for me as well     mysql upgrade -u root -p --force   systemctl restart mysqld   Regards  MSz

User · Answer

sometimes mysql upgrade -u root -p --force is not realy enough   please refer to this question   Table   39 performance schema session variables  39  doesn  39 t exist  according to it     open cmd cd  installation path  eds-binaries dbserver mysql5711x86x160420141510 bin mysql upgrade -u root -p --force

User · Answer

Follow these steps without -p      mysql upgrade -u root systemctl restart mysqld   I had the same problem and it works

User · Answer

For my system the problem ended up being that I still had Mysql 5 6 installed and so the mysql upgrade exe from that installation was being called instead of the one for 5 7  Navigate to C  Program Files MySQL MySQL Server 5 7 bin and run   mysql upgrade exe -u root

User · Answer

As sixty4bit question  if your mysql root user looks to be misconfigured  try to install the configurator extension from mysql official source   https   dev mysql com downloads repo apt   It will help you to set up a new root user password   Make sure to update your repository  debian ubuntu     apt-get update

User · Answer

Since none of the answers above actually explain what happened  I decided to chime in and bring some more details to this issue   Yes  the solution is to run the MySQL Upgrade command  as follows  mysql upgrade -u root -p --force  but what happened   The root cause for this issue is the corruption of performance schema  which can be caused by    Organic corruption  volumes going kaboom  engine bug  kernel driver issue etc  Corruption during mysql Patch  it is not unheard to have this happen during a mysql patch  specially for major version upgrades  A simple  drop database performance schema  will obviously cause this issue  and it will present the same symptoms as if it was corrupted   This issue might have been present on your database even before the patch  but what happened on MySQL 5 7 8 specifically is that the flag show compatibility 56 changed its default value from being turned ON by default  to OFF  This flag controls how the engine behaves on queries for setting and reading variables  session and global  on various MySQL Versions    Because MySQL 5 7  started to read and store these variables on performance schema instead of on information schema  this flag was introduced as ON for the first releases to reduce the blast radius of this change and to let users know about the change and get used to it   OK  but why does the connection fail  Because depending on the driver you are using  and its configuration   it may end up running commands for every new connection initiated to the database  like show variables  for instance   Because one of these commands can try to access a corrupted performance schema  the whole connection aborts before being fully initiated   So  in summary  you may  it s impossible to tell now  have had performance schema either missing or corrupted before patching  The patch to 5 7 8 then forced the engine to read your variables out of performance schema  instead of information schema  where it was reading it from because of the flag being turned ON   Since performance schema was corrupted  the connections are failing   Running MySQL upgrade is the best approach  despite the downtime  Turning the flag on is one option  but it comes with its own set of implications as it was pointed out on this thread already   Both should work  but weight the consequences and know your choices

User · Answer

I was able to log on to the mysql server after running the command  robregonm suggested   mysql upgrade -u root -p --force   A MySQL server restart is required

[mysql] Table 'performance_schema.session_variables' doesn't exist

Examples related to mysql

Examples related to upgrade