blocks|key|616033|text|我在MAC上使用的是MySQL+5.5.9版。我通过运行以下命令修复了这个问题：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|616034|mysql_upgrade+-uroot+-p|code-block|syntax|javascript|616035|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I'm using MySQL version 5.5.9 on MAC. I fixed this problem by running: 

<pre><code>mysql_upgrade -uroot -p
</code></pre>

blocks|key|831481|text|我在CentOS中使用了XAMPP，并手动升级了XAMPP，但现有的data文件夹除外。使用新的服务器软件MySQL和旧的数据库文件，我得到了相同的错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|831482|我使用了这个解决方案，并且工作得很好：|831483|cd+/opt/lampp/bin
./mysql_upgrade+-uroot+-p|code-block|syntax|javascript|831484|它几乎遍历了系统中的所有表，但最终以一个固定问题结束。|831485|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|O|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

I used XAMPP in CentOS and manually upgraded the XAMPP except the existing data folder.
With the new server software of MySQL and old database files, I got the same error.

I did with this solution and worked fine:

<pre><code>cd /opt/lampp/bin
./mysql_upgrade -uroot -p
</code></pre>

It looped through almost all tables in the system, but ended with a fixed issue.

blocks|key|616638|text|在windows上，使用XAMPP，我设法通过转到以下目录解决了这个问题：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|616639|mysql并运行您将在其中找到的可执行mysql_upgrade.exe，确保您的mysql服务器正在运行。|offset|length|style|CODE|616640|entityMap^0|0|J|H|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

On windows, with XAMPP i managed to fix the issue by going to the directory:

<code>C:\xampp\mysql\bin</code> and running the executable <code>mysql_upgrade.exe</code> you'll find inside, make sure your mysql server is running.

blocks|key|831656|text|我在mac上使用MAMP，无法按照上面的建议通过命令行升级我的数据库，但当我使用MAMP+PRO->TOOLS菜单选项(+OS屏幕顶部)来“检查”、“修复”和“升级”数据库时，它就起作用了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|831657|我假设GUI为底层CLI工具提供了必要的选项，这样您就不必考虑这些选项需要是什么(而不是手动运行CLI工具)。|831658|以这种方式升级我的MAMP+(通过MAMP+PRO的图形用户界面工具)使我的(单独的)+Oracle+mysqlWorkbench+6.0应用程序在我的本地OS+X+10.8.5+(Mountain+Lion)上的MAMP+PRO+2.0.5数据库上工作得很好，mysqlworkbench之前曾说过它已经损坏(但MAMP的phpmyadmin在它们上运行得很好，但奇怪的是它们是“损坏”的)。现在，mysqlWorkbench+6.0和MAMP+PRO的phpmyadmin工具都很高兴，我也是。|831659|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

I use MAMP on mac and failed to upgrade the my databases via command line as suggested above, but it worked when i used MAMP PRO->TOOLS menu options (top of OS X screen) to 'Check', 'Repair' and 'Upgrade' databases. 

I presume that the GUI supplies the underlying CLI tools with the necessary options, so that you don't have to think about what those options need to be (as opposed to running the CLI tools manually). 

Upgrading my MAMP in this way (via MAMP PRO's GUI Tools) made my (separate) Oracle mysqlWorkbench 6.0 app work just fine with my local MAMP PRO 2.0.5 databases on OS X 10.8.5 (Mountain Lion), which mysqlworkbench had said were corrupt previously (but MAMP's phpmyadmin worked fine on them whilst they were "corrupt", curiously). Now, both mysqlWorkbench 6.0 and MAMP PRO's phpmyadmin tools are both happy, and so am I.

blocks|key|832154|text|如果在特定查询上发生这种情况，请注意，当您尝试使用未定义的函数时，也可能发生这种情况。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|832155|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

If this happens on a specific query, be aware that this can also happen when you try to use an undefined function.

blocks|key|831520|text|这是由于不同服务器版本所需的架构更改造成的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|831521|mysql_upgrade+-uroot+-p|code-block|syntax|javascript|831522|将会解决这个问题。|831523|有时您需要卸载服务器并清理其数据目录。并重新安装以制作数据文件的最新副本。|831524|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

This happens due to schema changes required for different server versions.

<pre><code>mysql_upgrade -uroot -p
</code></pre>

will filx the issue.

Sometimes you require to uninstall server and clean its data directory. And re-install to make a fresh copy of data files.

blocks|key|616338|text|使用MAMP+PRO+(版本2.2)，我尝试了pmking的建议，但仍然一无所获。所以我编辑了两个文件:+/Applications/MAMP/bin/repairMysql.sh+/Applications/MAMP/bin/upgradeMysql.sh|type|unstyled|depth|inlineStyleRanges|entityRanges|data|616339|将每个函数中的“proot”更改为“p”。这创建了一个输入MySQL根密码的提示，并且成功了！|616340|我希望这对其他人有帮助。|616341|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Using MAMP PRO (version 2.2) I tried pmking's suggestion and was still getting nowhere. So I edited the two files:
/Applications/MAMP/bin/repairMysql.sh
/Applications/MAMP/bin/upgradeMysql.sh

changing 'proot' to 'p' in each. This creates a prompt for the MySQL root password and it worked!

I hope that helps someone else.

blocks|key|831845|text|在Debian6，MySQL+5.1.73-1+(+debian+)上，我遇到了同样的问题，启动和停止帮助了我。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|831846|/etc/init.d/mysql+stop
/etc/init.d/mysql+start|code-block|syntax|javascript|831847|不知道发生了什么，但这个问题似乎在退出后停止并启动后消失了，只是想在这里添加它，以防其他人也有同样的问题。|831848|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

on debian 6, MySQL 5.1.73-1 (Debian), I had the same problem, and a start and stop helped me.

<pre><code>/etc/init.d/mysql stop
/etc/init.d/mysql start
</code></pre>

not sure what happen, but the problem seems to go away after this quit stop and start, just wanted to add it here, in case others have same problem.

blocks|key|831908|text|当我在join中的SQL查询中出现语法错误时，我得到了这个错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|831909|我做到了|831910|JOIN+shops+ON+s+(...)|offset|length|style|CODE|831911|而不是正确的|831912|JOIN+shops+s+ON+(...)|831913|这个错误真的很让人困惑，我不知道这和mysql.proc有什么关系，但是修复了查询解决了这个问题。由于显而易见的原因，上述解决方案都不起作用。|831914|entityMap^0|0|0|0|L|0|0|0|L|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|T|8|@$F|U|G|V|H|I]]|9|@]|A|$]]|$1|J|3|K|5|6|7|W|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|X|8|@$F|Y|G|Z|H|I]]|9|@]|A|$]]|$1|N|3|O|5|6|7|10|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|Q|$]]

I got this error, when I had a syntax error in my SQL query in a join.

I did

<code>JOIN shops ON s (...)</code>

instead of the correct

<code>JOIN shops s ON (...)</code>

This error was really confusing, I don't know what this has to do with mysql.proc, but fixing the query fixed the problem. None of the above solutions worked for obvious reasons.

blocks|key|616546|text|当架构中的更改需要不同版本的mysql服务器时，可能会发生这种情况。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|616547|要解决此问题，请遵循以下代码行：|616548|mysql_upgrade+-uroot+-p+--force

/usr/bin/mysql_upgrade+-uroot+-p+--force|code-block|syntax|javascript|616549|完整的帖子细节可以在这里找到：Cannot+load+from+mysql.proc.+The+table+is+probably+corrupted|offset|length|616550|entityMap|0|LINK|mutability|MUTABLE|url|http://unlimitedwebworks.guru/web/cannot-load-from-mysql-proc-the-table-is-probably-corrupted^0|0|0|0|F|1O|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|W|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|X|8|@]|9|@$K|Y|L|Z|1|10]]|A|$]]|$1|M|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|T]]]]

This probably happens when the changes in schema required different versions of mysql server.

To fix this, follow the line of codes below:

<pre><code>mysql_upgrade -uroot -p --force

/usr/bin/mysql_upgrade -uroot -p --force
</code></pre>

Complete details of post will find here: <a href="http://unlimitedwebworks.guru/web/cannot-load-from-mysql-proc-the-table-is-probably-corrupted" rel="nofollow">Cannot load from mysql.proc. The table is probably corrupted</a>

blocks|key|616592|text|如果你是基于Unix的(比如Ubuntu)，你可以试试这个：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|616593|sudo+./mysql_upgrade+-uroot+-p|code-block|syntax|javascript|616594|就像Bimal建议的那样。|616595|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

if you're on Unix based (like Ubuntu) you can try this :

<pre><code>sudo ./mysql_upgrade -uroot -p
</code></pre>

like Bimal suggested.

blocks|key|616682|text|我也犯过完全相同的错误，而且解决方案很愚蠢，所以我建议在开始升级之前先寻找简单的答案。在我的特殊情况下，问题是我做到了：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|616683|COUNT+(id)+AS+quantity+...+#+Fails:+notice+space+between+COUNT+and+(|code-block|syntax|javascript|616684|它应该在哪里显示|616685|COUNT(id)+AS+quantity+...+#+Works:+notice+no+space+between+COUNT+and+(|616686|当你不使用框架时，就会发生这种情况，你可以(应该)这样做，在这种情况下，在Laravel+5中：|offset|length|616687|$users+=+DB::table('users')->count();|616688|entityMap|0|LINK|mutability|MUTABLE|url|https://laravel.com/docs/5.1/queries^0|0|0|0|0|11|7|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|Z|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|10|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|11|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|12|8|@]|9|@$M|13|N|14|1|15]]|A|$]]|$1|O|3|P|5|D|7|16|8|@]|9|@]|A|$E|F]]|$1|Q|3|-4|5|6|7|17|8|@]|9|@]|A|$]]]|R|$S|$5|T|U|V|A|$W|X]]]]

I had exact same error, and solution was just stupid, so I recommend to look for simple answers before starting to upgrade stuff. In my particular case the problem was I did: 

<pre><code>COUNT (id) AS quantity ... # Fails: notice space between COUNT and (
</code></pre>

where it should read

<pre><code>COUNT(id) AS quantity ... # Works: notice no space between COUNT and (
</code></pre>

This happens when you don't use a framework, you could (should) do something like this, in this case with in <a href="https://laravel.com/docs/5.1/queries" rel="nofollow">Laravel</a> 5:

<pre><code>$users = DB::table('users')-&gt;count();
</code></pre>

blocks|key|832109|text|哇，我只是转到C:\xampp\mysql\bin并运行mysql_upgrade.exe|type|unstyled|depth|inlineStyleRanges|entityRanges|data|832110|它会自我修复，现在一切都运行得很好。|832111|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Wow, i just go to C:\xampp\mysql\bin and run mysql_upgrade.exe

It repair itself and now everithing is working great.

I am starting to use MySQL Workbench tool especially for data modeling. So, the first I would like to do is reverse engineering of my existing database on web server. But I not able to finish the process, because I alway get this strange error message:

<pre><code>Error: Cannot load from mysql.proc. The table is probably corrupted
</code></pre>

I tried to repair this table but it not help me. So, do you have any experience with this problem and know how to solve it?

MySQL Workbench cannot load mysql.proc

我开始使用MySQL工作台工具，特别是用于数据建模。所以，我想做的第一件事就是在web服务器上对我现有的数据库进行逆向工程。但是我无法完成这个过程，因为我总是收到这个奇怪的错误消息：Error: Cannot load from mysql.proc. The table is probably corrupted我试着修这张桌子，但它对我没有帮助。那么，你对这个问题有什么经验，知道如何解决它吗？

问MySQL工作台无法加载mysql.proc
EN

回答 13

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问MySQL工作台无法加载mysql.procEN

回答 13

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问MySQL工作台无法加载mysql.proc
EN