欧美97色伦欧美一区二区日韩,国产福利片在线观看,freexxx性欧美vide0高清,西西亚洲,日本欧美国产精品第一页久久,成人18免费软件

當(dāng)前位置： 維易PHP培訓(xùn)學(xué)院 > MYSQL教程 > 內(nèi)容正文

Mysql學(xué)習(xí)將MySQL從MyISAM轉(zhuǎn)換成InnoDB錯誤和解決辦法

作者：VEPHP   時間 2017-11-21

《Mysql學(xué)習(xí)將MySQL從MyISAM轉(zhuǎn)換成InnoDB錯誤和解決辦法》要點：
本文介紹了Mysql學(xué)習(xí)將MySQL從MyISAM轉(zhuǎn)換成InnoDB錯誤和解決辦法，希望對您有用。如果有疑問，可以聯(lián)系我們。

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

MYSQL學(xué)習(xí)MySQL從MyISAM轉(zhuǎn)換成InnoDB錯誤和解決辦法 - DarkBlue - DarkBlue Log

MYSQL學(xué)習(xí)圖1?設(shè)置數(shù)據(jù)庫類型

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

MYSQL學(xué)習(xí)MySQL從MyISAM轉(zhuǎn)換成InnoDB錯誤和解決辦法 - DarkBlue - DarkBlue Log

?圖2 Start service出錯
想直接到services.msc里面啟動服務(wù),也不行.錯誤提示內(nèi)容為：“在 本地計算機 無法啟動mysql服務(wù) 錯誤1067：進(jìn)程意外中止.”
依照網(wǎng)上的某些做法,卸載了MySQL服務(wù),也沒重啟就重新設(shè)置,問題如故；把服務(wù)卸載了,重啟后再重新設(shè)置,則是啟動服務(wù)成功,但是在后面的Applying Security Settings的時候有新的問題,如下圖3.圖2那里的錯誤提示則變成“ERROR 2003: Can't connect to MySQL server on 'localhost' (10061)", 說明MySQL還是沒有啟動,或者啟動過,出錯又關(guān)了.
MySQL從MyISAM轉(zhuǎn)換成InnoDB錯誤和解決辦法 - DarkBlue - DarkBlue Log
?圖3
順便提一下,在MySQL5里(其他版本的我不知道)每運行一次設(shè)置向?qū)?只要按了execute執(zhí)行,都會在MySQL5的安裝目錄下自動生成一個原來的MySQL的設(shè)置文件my.ini的備份bak文件.并且將以修改的時間命名.因此如果設(shè)置出了問題,可以從備份文件恢復(fù).
后來還是在錯誤日志里找到思路.錯誤日志就是放在 MySQL5安裝目錄\Data 目錄里的那個以你的計算機名命名的.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錯誤.再去查看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).果真,把前面兩個ib_logfile刪了,重啟系統(tǒng)就搞定了.前面的可能是因為剛開機,所以也行.實際上是需要重啟系統(tǒng)的.這時的日志如下
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)在只剩下最后一個問題了Default storage engine (InnoDB) is not available.去services.msc里面啟動MySQL服務(wù),還是出錯.但是日志卻是顯示
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é)會了讀懂錯誤日志文件err文件了.不過我就在想了,如果從一開始就依照上面的做,不知道會怎么樣呢?
轉(zhuǎn)自 DarkBlue blog

維易PHP培訓(xùn)學(xué)院每天發(fā)布《Mysql學(xué)習(xí)將MySQL從MyISAM轉(zhuǎn)換成InnoDB錯誤和解決辦法》等實戰(zhàn)技能，PHP、MYSQL、LINUX、APP、JS,CSS全面培養(yǎng)人才。

轉(zhuǎn)載請注明本頁網(wǎng)址：
http://www.snjht.com/jiaocheng/13992.html


    標(biāo)簽：