简体   繁体   English

如何修复致命错误:无法打开和锁定特权表:表 '.\mysql\proxies_priv' 被标记为已崩溃并且最后(自动?)修复失败

[英]How do I fix Fatal error: Can't open and lock privilege tables: Table '.\mysql\proxies_priv' is marked as crashed and last (automatic?) repair failed

Switching on my system this morning, MySQL immediately stops once started in XAMPP, windows 10. Last thing I did was install Windows Powertoys, not sure if it's the cause but it's the last change. Switching on my system this morning, MySQL immediately stops once started in XAMPP, windows 10. Last thing I did was install Windows Powertoys, not sure if it's the cause but it's the last change.

I found the subject-quoted error in Windows event viewer log but following Google searches for resolutions I see to run myisamchk: this gives me the error proxies_priv.mai is not a myisam table.我在 Windows 事件查看器日志中发现了主题引用的错误,但是在 Google 搜索我看到运行 myisamchk 的分辨率后:这给了我错误 proxies_priv.mai is not a myisam table。

How can I get things back to normal?我怎样才能让事情恢复正常?

Facing the same problem here.在这里面临同样的问题。 You are getting the error proxies_priv.mai is not a myisam table because you typed the file name wrong.您收到错误proxies_priv.mai is not a myisam table因为您输入了错误的文件名。 It's proxies_priv.MYI , not proxies_priv.mai .它是proxies_priv.MYI ,而不是proxies_priv.mai

Nevertheless, trying to fix it by ./myisamchk.exe -r../data/mysql/proxies_priv.MYI seems not working for me.尽管如此,尝试通过./myisamchk.exe -r../data/mysql/proxies_priv.MYI修复它似乎对我不起作用。 I got proxies_priv doesn't have a correct index definition.我得到了proxies_priv doesn't have a correct index definition. and don't know what to do next.并且不知道下一步该做什么。

Finally I deleted all the file in mysql data folders containing proxies_priv and at least got mysql running.最后我删除了 mysql 数据文件夹中包含proxies_priv的所有文件,至少让 mysql 运行。 According to apachefriends post根据apachefriends的帖子

Everything seems to work.一切似乎都奏效了。 I'm not entirely sure what those tables are used for, since I never used any proxy with my local mysql server.我不完全确定这些表的用途,因为我从未在本地 mysql 服务器上使用任何代理。

暂无
暂无

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 MySQL 表被标记为崩溃并且最后(自动?)修复失败 - MySQL table is marked as crashed and last (automatic?) repair failed 致命错误:无法打开和锁定权限表:表 'mysql.host' 不存在 - Fatal error: Can't open and lock privilege tables: Table 'mysql.host' doesn't exist MySQL致命错误:无法打开和锁定权限表:文件格式“用户”不正确 - MySQL Fatal error: Can't open and lock privilege tables: Incorrect file format 'user' 移动数据后无法运行mysql(严重错误:无法打开和锁定特权表:表'mysql.host'不存在) - Cannot run mysql after moving data (Fatal error: Can't open and lock privilege tables: Table 'mysql.host' doesn't exist) Docker中的Bootstraping Percona Xtradb Cluster出现错误:无法打开和锁定特权表:表'mysql.user'不存在 - Bootstraping Percona Xtradb Cluster in Docker gives the error: Can't open and lock privilege tables: Table 'mysql.user' doesn't exist Mysql/mariadb“无法打开和锁定权限表:表‘mysql.servers’不存在” - Mysql/mariadb "Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist" 无法打开和锁定权限表:表 'mysql.user' 不存在 - Can't open and lock privilege tables: Table 'mysql.user' doesn't exist Mysql给我:“无法打开和锁定特权表:表'主机'是只读的” - Mysql gives me:“Can't open and lock privilege tables: Table 'host' is read only” 当您无法修复表时,如何修复 MySQL“不正确的密钥文件”错误? - How do you fix a MySQL "Incorrect key file" error when you can't repair the table? MySQL表被标记为崩溃 - MySQL table is marked as crashed
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM