资料库名称：yuma 资料库版本：5.5.39 - MySQL Community Server (GPL) 内容/问题描述： 我在做一个资料表关联时发生错误。 资料表就不见了，而且不能新增同名资料表。 请问该如何解决。 谢谢。 错误讯息： This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information. 09:42:25 UTC - mysqld got exception 0x80000003 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=16777216 read_buffer_size=262144 max_used_connections=2 max_threads=151 thread_count=2 connection_count=2 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 133464 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x3b63188 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... 14fe6f0 mysqld.exe!my_thread_name() 1657cd4 mysqld.exe!my_mb_ctype_mb() 153a62d mysqld.exe!my_osmaperr() 153e279 mysqld.exe!my_osmaperr() 158a9dc mysqld.exe!my_osmaperr() Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (3b55d88): ALTER TABLE `purchase` ADD FOREIGN KEY (`com_id`) REFERENCES `yuma`.`company`(`com_id`) ON DELETE CASCADE ON UPDATE CASCADEConnection ID (thread ID): 116 Status: NOT_KILLED The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. --

※ 发信站: 批踢踢实业坊(ptt.cc), 来自: 211.76.32.193 ※ 文章网址: http://webptt.com/cn.aspx?n=bbs/Database/M.1416125020.A.F37.html ※ 编辑: doubleaisno1 (211.76.32.193), 11/16/2014 17:54:13