I think there may be more than one reason for this problem, so I collected some friends on the Internet to solve this problem for your reference, I hope you can help. First, open the my.ini file, find the default-storage-engine=InnoDB line, and change it to default-storage-engine=MyISAM.
2. Delete ib_logfile0 and ib_logfile1 in the Data directory under the MySQL installation directory. Find the InfoDB directory specified when configuring the MySQL server to remove ibdata1
According to the my.ini file:
#*** INNODB Specific options *** innodb_data_home_dir="D:/". 4. Restart MySQL Service
According to my own practice, just follow the third step to solve the problem.
two,
err contents of the file:
090417 9:02:55 InnoDB: Error: unable to create temporary file; errno: 2 090417 9:02:55 [ERROR] Plugin 'InnoDB' Init function returned error. 090417 9:02:55 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 090417 9:02:55 [ERROR] Unknown/unsupported table type: INNODB 090417 9:02:55 [ERROR] Aborting
090417 9:02:55 [Warning] Forcing shutdown of 1 plugins 090417 9:02:55 [Note] MySQL: Shutdown complete
After a Google scan, I found out why it could not be started: MySQL is installed The time does not automatically initialize tmpdir (temporary file directory), so add the following content in the configuration file my.ini:
[mysqld]
#自一个的暂文件目录#brmpdir="D :/MySQL/MySQL Server 5.1/Temp"
Starting MySQL again is fine. Some temporary files of *.tmp are generated in the Temp folder.
Finally, there are still some doubts: If it is because tmpdir is not initialized, why is it not initialized when I first installed it, but there is no such problem?
three,
before very smoothly when manually install windows service MySQL5.0.16 last night when 5.0.83 installation service, always prompt error 1067. Some people on the Internet said that putting my.ini under C:\\WINDOWS would be fine, but the situation I encountered was that the problem still remained unresolved. My solution is to --defaults-file parameter replaced with --defaults-extra-file, as follows:
mysqld --install MySQL --defaults-file = E: /mysql-5.0. 83-win32 /my.ini
changed
mysqld --install MySQL --defaults-extra-file = E: /mysql-5.0.83-win32/my.ini
execute mysqld --verbose --help can see the usage of mysqld, which has a description of these two parameters.
In my own practice, the most likely cause of this problem is a data table storage engine (Engine, in short, is the type of storage engine refers to the table, namely Table Type < Br>) caused. The MySQL database supports a variety of data table storage engines, which can be viewed with the command: show engines, which can also be seen in the MySQL configuration file my.ini (the default is MyISAM):
# The default storage engine that Will be used when create new tables when default-storage-engine=MyISAM.
also commonly used storage engine InnoDB, InnoDB has a variety of advantages, InnoDB to MySQL table provides transaction, rollback, crash repair capacity, transaction-safe multi-version concurrency control. At the same time, InnoDB also on MySQL The first engine to provide foreign key constraints, and the ability of the InnoDB storage engine to handle transactions is also unmatched by other MySQL storage engines.
The difference between InnoDB and MyISAM:
The table stored by the InnoDB storage engine, the .frm of the storage table structure is stored separately from the stored table data file (ibdata1), and the table data is stored. The file location can be set by modifying the my.ini file:
#*** INNODB Specific options ***
innodb_data_home_dir="D:/"
The table stored by the MyISAM storage engine includes a total of 3 files: .frm (structure of stored table) file, .MYD (abbreviation of MYouData, data of stored table) file, .MYI (abbreviation of MYIndex, index of storage table), these three files are stored in MySQL database at the same time. In the directory where the data is stored during installation, such as F:\\ProgramData\\MySQL\\MySQL Server 5.1\\data\\Databasename.
In addition, through the solution of this problem, I realized the importance of viewing the error log. When encountering problems, the first thing we should think of is to check the error log instead of thinking about going to Google or going. Baidu, in fact, from the error log, we can get the real cause of the problem, the right medicine, in order to get the medicine to the disease. The MySQL error log (.err) is located in the F:\\ProgramData\\MySQL\\MySQL Server 5.1\\data directory. The file name is usually your computer name.