后來(lái)在做WordPress，一開始還不知道原來(lái)WordPress用的是InnoDB數(shù)據(jù)引擎，于是在原來(lái)的數(shù)據(jù)庫(kù)里面就建了一個(gè)數(shù)據(jù)庫(kù),一開始也沒發(fā)覺問題，安裝，導(dǎo)入sql，都沒問題，當(dāng)時(shí)也沒多想。直到這幾天因?yàn)橛忠b多一個(gè)WordPress，用phpmyadmin訪問數(shù)據(jù)庫(kù)多一點(diǎn)，問題來(lái)了。老是一訪問WordPress的數(shù)據(jù)庫(kù)，就彈出錯(cuò)誤提示“Mysqld-nt.exe應(yīng)用程序錯(cuò)誤：“0x005346c4”指令引用的“0x00786000”內(nèi)存，該內(nèi)存不能為讀...”，然后就MySQL服務(wù)也停了，登錄不了，整個(gè)數(shù)據(jù)庫(kù)都訪問不了。

圖1 設(shè)置數(shù)據(jù)庫(kù)類型

糾結(jié)了挺久，也忘了是看到什么文章觸發(fā)了靈感，反正后來(lái)才知道原來(lái)是數(shù)據(jù)引擎不同惹的禍。于是就想到重新版運(yùn)行次設(shè)置向?qū)?#xff0c;把數(shù)據(jù)庫(kù)類型改成支持InnoDB引擎的。馬上行動(dòng)，在向?qū)Ю镌O(shè)置數(shù)據(jù)庫(kù)類型(也就是圖1的database usage)那里，設(shè)置成第二項(xiàng)，還在后面的InnoDB Tablespace Settings里把InnoDB數(shù)據(jù)文件設(shè)置放在D:\MySQL InnoDB Datafiles目錄里。但是在最后execute執(zhí)行的時(shí)候，卻老是在Start Service那里出問題，如下圖2。

圖2 Start service出錯(cuò)

想直接到services.msc里面啟動(dòng)服務(wù)，也不行。錯(cuò)誤提示內(nèi)容為：“在 本地計(jì)算機(jī) 無(wú)法啟動(dòng)mysql服務(wù) 錯(cuò)誤1067：進(jìn)程意外中止。”

按照網(wǎng)上的某些做法，卸載了MySQL服務(wù)，也沒重啟就重新版設(shè)置，問題如故；把服務(wù)卸載了，重啟后再重新版設(shè)置，則是啟動(dòng)服務(wù)成功，但是在后面的Applying Security Settings的時(shí)候有新版的問題，如下圖3。圖2那里的錯(cuò)誤提示則變成“ERROR 2003: Can't connect to MySQL server on 'localhost' (10061)"， 介紹MySQL還是沒有啟動(dòng)，或者啟動(dòng)過，出錯(cuò)又關(guān)了。

圖3

順便提一下，在MySQL5里(其他版本的我不知道)每運(yùn)行一次設(shè)置向?qū)?#xff0c;只要按了execute執(zhí)行，都會(huì)在MySQL5的安裝目錄下自動(dòng)生成一個(gè)原來(lái)的MySQL的設(shè)置文件my.ini的備份bak文件。并且將以改的時(shí)間命名。因此如果設(shè)置出了問題，可以從備份文件恢復(fù)。

后來(lái)還是在錯(cuò)誤日志里找到思路。錯(cuò)誤日志就是放在 MySQL5安裝目錄\Data 目錄里的那個(gè)以你的計(jì)算機(jī)名命名的.err文件。

首先我找到以下一段：

InnoDB: Error: log file .\ib_logfile0 is of different size 0 52428800 bytes

InnoDB: than specified in the .cnf file 0 10485760 bytes!

101001 9:47:42 [ERROR] Default storage engine (InnoDB) is not available

101001 9:47:42 [ERROR] Aborting

101001 9:47:42 [Note] D:\MySQL5\bin\mysqld-nt: Shutdown complete

于是就到“MySQL5安裝目錄\Data ”目錄里把ib_logfile0日志文件刪掉，重啟MySQL服務(wù)，還是提示10067錯(cuò)誤。再去查看err文件。

101001 18:39:29 InnoDB: Log file .\ib_logfile0 did not exist: new to be created

InnoDB: Setting log file .\ib_logfile0 size to 109 MB

InnoDB: Database physically writes the file full: wait...

InnoDB: Progress in MB: 100

InnoDB: Error: log file .\ib_logfile1 is of different size 0 52428800 bytes

InnoDB: than specified in the .cnf file 0 114294784 bytes!

101001 18:39:30 [ERROR] Default storage engine (InnoDB) is not available

101001 18:39:30 [ERROR] Aborting

101001 18:39:30 [Note] D:\MySQL5\bin\mysqld-nt: Shutdown complete

可以看到，ib_logfile0的問題解決了，但是同樣的問題卻出在ib_logfile1上面了。于是依樣畫葫蘆，把ib_logfile1刪了，再重啟MySQL服務(wù)，卻發(fā)現(xiàn)沒用。難道是還要重啟系統(tǒng)。果真，把前面兩個(gè)ib_logfile刪了，重啟系統(tǒng)就搞定了。前面的可能是因?yàn)閯傞_機(jī)，所以也行。實(shí)際上是需要重啟系統(tǒng)的。這時(shí)的日志如下

101001 19:19:24 InnoDB: Log file .\ib_logfile0 did not exist: new to be created

InnoDB: Setting log file .\ib_logfile0 size to 109 MB

InnoDB: Database physically writes the file full: wait...

InnoDB: Progress in MB: 100

101001 19:19:26 InnoDB: Log file .\ib_logfile1 did not exist: new to be created

InnoDB: Setting log file .\ib_logfile1 size to 109 MB

InnoDB: Database physically writes the file full: wait...

InnoDB: Progress in MB: 100

InnoDB: Cannot initialize created log files because

InnoDB: data files are corrupt, or new data files were

InnoDB: created when the database was started previous

InnoDB: time but the database was not shut down

InnoDB: normally after that.

101001 19:19:27 [ERROR] Default storage engine (InnoDB) is not available

101001 19:19:27 [ERROR] Aborting

101001 19:19:27 [Note] D:\MySQL5\bin\mysqld-nt: Shutdown complete

好了，現(xiàn)在只剩下最后一個(gè)問題了Default storage engine (InnoDB) is not available。去services.msc里面啟動(dòng)MySQL服務(wù)，還是出錯(cuò)。但是日志卻是顯示

InnoDB: No valid checkpoint found.

InnoDB: If this error appears when you are creating an InnoDB database,

InnoDB: the problem may be that during an earlier attempt you managed

InnoDB: to create the InnoDB data files, but log file creation failed.

InnoDB: If that is the case, please refer to

InnoDB: http://dev.mysql.com/doc/mysql/en/Error_creating_InnoDB.html

101001 20:45:09 [ERROR] Default storage engine (InnoDB) is not available

101001 20:45:09 [ERROR] Aborting

101001 20:45:09 [Note] D:\MySQL5\bin\mysqld-nt: Shutdown complete

于是去網(wǎng)上搜索了一下，發(fā)現(xiàn)提示No valid checkpoint found.的解決辦法：刪除所有現(xiàn)有的ibdataN和ib_logfileN文件后，重啟Mysql。于是照做，果然行了。

InnoDB: The first specified data file D:\MySQL InnoDB Datafiles\ibdata1 did not exist:

InnoDB: a new database to be created!

101001 21:04:24 InnoDB: Setting file D:\MySQL InnoDB Datafiles\ibdata1 size to 10 MB

InnoDB: Database physically writes the file full: wait...

101001 21:04:25 InnoDB: Log file .\ib_logfile0 did not exist: new to be created

InnoDB: Setting log file .\ib_logfile0 size to 109 MB

InnoDB: Database physically writes the file full: wait...

InnoDB: Progress in MB: 100

101001 21:04:27 InnoDB: Log file .\ib_logfile1 did not exist: new to be created

InnoDB: Setting log file .\ib_logfile1 size to 109 MB

InnoDB: Database physically writes the file full: wait...

InnoDB: Progress in MB: 100

InnoDB: Doublewrite buffer not found: creating new

InnoDB: Doublewrite buffer created

InnoDB: Creating foreign key constraint system tables

InnoDB: Foreign key constraint system tables created

101001 21:04:31 InnoDB: Started; log sequence number 0 0

101001 21:04:32 [Note] D:\MySQL5\bin\mysqld-nt: ready for connections.

Version: '5.0.18-nt' socket: '' port: 3306 MySQL Community Edition (GPL)

奮斗了一天，總算成功地把MySQL從MyISAM轉(zhuǎn)換成InnoDB引擎了。也學(xué)會(huì)了讀懂錯(cuò)誤日志文件err文件了。不過我就在想了，如果從一開始就按照上面的做，不知道會(huì)如何樣呢？

轉(zhuǎn)自 DarkBlue blog

總結(jié)

以上是生活随笔為你收集整理的mysql中non用什么_mysql Non-Transactional Database Only(只支持MyISAM)的全部?jī)?nèi)容，希望文章能夠幫你解決所遇到的問題。

如果覺得生活随笔網(wǎng)站內(nèi)容還不錯(cuò)，歡迎將生活随笔推薦給好友。