Shulou(Shulou.com)05/31 Report--

This article introduces the relevant knowledge of "how to deal with log errors when mysql5.0 is upgraded to 5.1". In the operation of actual cases, many people will encounter such a dilemma, so let the editor lead you to learn how to deal with these situations. I hope you can read it carefully and be able to achieve something!

Today's production environment has been upgraded from 5.0 to 5.1, resulting in an error in the log, as follows

Event Scheduler: An error occurred when initializing system tables. Disabling the Event Scheduler.

Mysql.user has no `Event_ priv` column at position 29

Solution:

Repair mysql system table

Mysql_fix_privilege_tables

Or provide password repair

Mysql_fix_privilege_tables-password=root_password

The mysql_fix_privilege_tables script can perform any action that converts the system table to the current format. You may see some Duplicate column name warnings at run time; you can ignore them.

This is the end of the content of "how to deal with log errors when mysql5.0 is upgraded to 5.1". Thank you for reading. If you want to know more about the industry, you can follow the website, the editor will output more high-quality practical articles for you!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.