mysql5.6 1067問題

轉載至：http://aiilive.blog.51cto.com/1925756/1243894

上一次安裝完成Mysql5.6服務，一段時間後發生異常，Mysql服務無法啓動進程終止： 1067；網上找了好多方法還是沒能解決這個問題，今天重新安裝Mysql5.6，同樣出現這個問題，後來通過閱讀

MySQL 5.6 Reference Manual Including MySQL Cluster NDB 7.3 Reference Guide

這個問題最終得以解決了。

  下面是安裝Mysql On Windows 解壓安裝方式。

1. 下載Mysql安裝包：mysql-5.6.12-win32.zip；

2. 解壓安裝到D:\__dev下；

3. 添加環境變量，創建MYSQL_HOME變量，

   1	MYSQL_HOME=D:\__dev\mysql-5.6.12-win32

   配置Path路徑，、bin

   1	%MYSQL_HOME%\bin;

4. 修改mysql-5.6.12-win32下的my-default.ini文件

1 2 3 4 5 6

#Path to installation directory. All paths are usually resolved relative to this. #basedir="C:/Program Files/MySQL/MySQL Server 5.0/" basedir = D:/__dev/mysql-5.6.12-win32 #Path to the database root #datadir="C:/Program Files/MySQL/MySQL Server 5.0/Data/" datadir = D:/__dev/mysql-5.6.12-win32/data

  如上圖配置basedir和datadir.

  在開發指南上有精簡配置如下圖：

5. 使用管理員權限運行命令窗口，切換工作目錄爲Path目錄下，安裝Mysql服務

1 2 3

mysqld -install 出現Service successfully installed. 表示安裝服務成功

6. 啓動mysql服務

1	net start mysql

7.登錄到mysql，並修改root用戶密碼，默認爲空

1 2	mysql>mysq -uroot mysql>update mysql.user set password=PASSWORD('root') where User='root'

問題解決了，mysql5.6的配置文件在安裝目錄下，名字已經變爲my-default.ini.

詳細配置信息如下：

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132

[client] port=3306 [mysql] #default-character-set=latin1 default-character-set=utf8 [mysqld] # The TCP/IP Port the MySQL Server will listen on port=3306 #log-error=c:\error.log #Path to installation directory. All paths are usually resolved relative to this. #basedir="C:/Program Files/MySQL/MySQL Server 5.0/" basedir = D:/__dev/mysql-5.6.12-win32 #Path to the database root #datadir="C:/Program Files/MySQL/MySQL Server 5.0/Data/" datadir = D:/__dev/mysql-5.6.12-win32/data # The default character set that will be used when a new schema or table is # created and no character set is defined default-character-set=utf8 # The default storage engine that will be used when create new tables when default-storage-engine=INNODB # Set the SQL mode to strict sql-mode="STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION" # The maximum amount of concurrent sessions the MySQL server will # allow. One of these connections will be reserved for a user with # SUPER privileges to allow the administrator to login even if the # connection limit has been reached. max_connections=100 # Query cache is used to cache SELECT results and later return them # without actual executing the same query once again. Having the query # cache enabled may result in significant speed improvements, if your # have a lot of identical queries and rarely changing tables. See the # "Qcache_lowmem_prunes" status variable to check if the current value # is high enough for your load. # Note: In case your tables change very often or if your queries are # textually different every time, the query cache may result in a # slowdown instead of a performance improvement. query_cache_size=0 # The number of open tables for all threads. Increasing this value # increases the number of file descriptors that mysqld requires. # Therefore you have to make sure to set the amount of open files # allowed to at least 4096 in the variable "open-files-limit" in # section [mysqld_safe] table_cache=256 # Maximum size for internal (in-memory) temporary tables. If a table # grows larger than this value, it is automatically converted to disk # based table This limitation is for a single table. There can be many # of them. tmp_table_size=15M # How many threads we should keep in a cache for reuse. When a client # disconnects, the client's threads are put in the cache if there aren't # more than thread_cache_size threads from before.  This greatly reduces # the amount of thread creations needed if you have a lot of new # connections. (Normally this doesn't give a notable performance # improvement if you have a good thread implementation.) thread_cache_size=8 #*** MyISAM Specific options # The maximum size of the temporary file MySQL is allowed to use while # recreating the index (during REPAIR, ALTER TABLE or LOAD DATA INFILE. # If the file-size would be bigger than this, the index will be created # through the key cache (which is slower). myisam_max_sort_file_size=100G # If the temporary file used for fast index creation would be bigger # than using the key cache by the amount specified here, then prefer the # key cache method.  This is mainly used to force long character keys in # large tables to use the slower key cache method to create the index. myisam_max_extra_sort_file_size=100G # If the temporary file used for fast index creation would be bigger # than using the key cache by the amount specified here, then prefer the # key cache method.  This is mainly used to force long character keys in # large tables to use the slower key cache method to create the index. myisam_sort_buffer_size=30M # Size of the Key Buffer, used to cache index blocks for MyISAM tables. # Do not set it larger than 30% of your available memory, as some memory # is also required by the OS to cache rows. Even if you're not using # MyISAM tables, you should still set it to 8-64M as it will also be # used for internal temporary disk tables. key_buffer_size=22M # Size of the buffer used for doing full table scans of MyISAM tables. # Allocated per thread, if a full scan is needed. read_buffer_size=64K read_rnd_buffer_size=256K # This buffer is allocated when MySQL needs to rebuild the index in # REPAIR, OPTIMZE, ALTER table statements as well as in LOAD DATA INFILE # into an empty table. It is allocated per thread so be careful with # large settings. sort_buffer_size=256K #*** INNODB Specific options *** # Use this option if you have a MySQL server with InnoDB support enabled # but you do not plan to use it. This will save memory and disk space # and speed up some things. #skip-innodb # Additional memory pool that is used by InnoDB to store metadata # information.  If InnoDB requires more memory for this purpose it will # start to allocate it from the OS.  As this is fast enough on most # recent operating systems, you normally do not need to change this # value. SHOW INNODB STATUS will display the current amount used. innodb_additional_mem_pool_size=2M # If set to 1, InnoDB will flush (fsync) the transaction logs to the # disk at each commit, which offers full ACID behavior. If you are # willing to compromise this safety, and you are running small # transactions, you may set this to 0 or 2 to reduce disk I/O to the # logs. Value 0 means that the log is only written to the log file and # the log file flushed to disk approximately once per second. Value 2 # means the log is written to the log file at each commit, but the log # file is only flushed to disk approximately once per second. innodb_flush_log_at_trx_commit=1 # The size of the buffer InnoDB uses for buffering log data. As soon as # it is full, InnoDB will have to flush it to disk. As it is flushed # once per second anyway, it does not make sense to have it very large # (even with long transactions). innodb_log_buffer_size=1M # InnoDB, unlike MyISAM, uses a buffer pool to cache both indexes and # row data. The bigger you set this the less disk I/O is needed to # access data in tables. On a dedicated database server you may set this # parameter up to 80% of the machine physical memory size. Do not set it # too large, though, because competition of the physical memory may # cause paging in the operating system.  Note that on 32bit systems you # might be limited to 2-3.5G of user level memory per process, so do not # set it too high. innodb_buffer_pool_size=40M # Size of each log file in a log group. You should set the combined size # of log files to about 25%-100% of your buffer pool size to avoid # unneeded buffer pool flush activity on log file overwrite. However, # note that a larger logfile size will increase the time needed for the # recovery process. innodb_log_file_size=20M # Number of threads allowed inside the InnoDB kernel. The optimal value # depends highly on the application, hardware as well as the OS # scheduler properties. A too high value may lead to thread thrashing. innodb_thread_concurrency=8 log-error=D:/__dev/mysql-5.6.12-win32/err.log log=D:/__dev/mysql-5.6.12-win32/log.log

配置文件my-default.ini見附件下載，下載之後去掉後綴名（.txt）.