I used it for installation. Therefore, when setting databaseusage (for example, 1), follow the official discuz suggestions, all selected are Non-TransactionalDatabaseOnly (only Non-transaction databases of MyISAM data engine are supported). InnoDB is not required for MyISAM databases, so INNODB engine is not directly loaded.
It was originally used for installation. Therefore, when setting database usage (for example, 1), follow the official discuz suggestions, all selected are Non-Transactional Database Only (Only Non-transaction databases of MyISAM data engine are supported). InnoDB is not required for MyISAM databases, so INNODB engine is not directly loaded.
Later, I was working on WordPress. I didn't know that WordPress was using the InnoDB Data Engine at the beginning, so I built a database in the original database. I didn't find any problems at the beginning, it's okay to import the SQL statement. I didn't think much about it at the time. The problem is that one more WordPress is installed and phpmyadmin is used to access the database a little more. The error message"
Set Database Type
After a long struggle, I forgot what articles I saw triggered the inspiration. Later I realized that it was a disaster caused by different data engines. So I thought of re-running the settings wizard and changing the database type to support the InnoDB engine. Set the database type (that is, database usage) in the wizard and set it to the second item. In the InnoDB Tablespace Settings section, set the InnoDB data file to D: \ MySQL InnoDB Datafiles directory. But at the end of execute, there is always a problem with Start Service, such as 2.
If you want to Start the service directly in services. msc, you cannot Start the service. The error message "" indicates that, according to some practices on the Internet, the MySQL service has been uninstalled and is reset without restarting. If the problem persists, uninstall the service and restart the service before resetting, the service is successfully started, but there are new problems in the following Applying Security Settings, such as 3. The error message is "by the way, in MySQL5 (I don't know about other versions), every time you run the setup wizard, you only need to execute the execute Command, will automatically generate an original MySQL setting file in the installation directory of mysql5. ini. And it will be named after the modification time. Therefore, if an error occurs, you can recover from the backup file.
Later, I found the idea in the error log. The error log is the. err file named after your computer in the MySQL5 installation directory \ Data directory. First, I found the following section: InnoDB: Error: log file. \ ib_logfile0 is of different size 0 52428800 bytesInnoDB: than specified in the. cnf file 0 10485760 bytes! 101001 9:47:42 [ERROR] Default storage engine (InnoDB) is not available101001 9:47:42 [ERROR] Aborting
101001 9:47:42 [Note] D: \ MySQL5 \ bin \ mysqld-nt: Shutdown complete
Therefore, the ib_logfile0 log file is deleted in the "MySQL5 installation directory \ Data", and the MySQL service is restarted. The error 10067 is returned. Check the err file again. 101001 18:39:29 InnoDB: Log file. \ ib_logfile0 did not exist: new to be createdInnoDB: Setting log file. \ ib_logfile0 size to 109 MBInnoDB: Database physically writes the file full: wait... innoDB: Progress in MB: 100 InnoDB: Error: log file. \ ib_logfile1 is of different size 0 52428800 bytesInnoDB: than specified in. cnf file 0 114294784 bytes! 101001 18:39:30 [ERROR] Default storage engine (InnoDB) is not available101001 18:39:30 [ERROR] Aborting
101001 18:39:30 [Note] D: \ MySQL5 \ bin \ mysqld-nt: Shutdown complete
We can see that the ib_logfile0 problem is solved, but the same problem lies in ib_logfile1. Therefore, I drew a gourd, deleted ib_logfile1, and restarted the MySQL service, but it was useless. Is it necessary to restart the system. If you delete the first two ib_logfiles, restart the system. The reason may be that you just started the instance.
Actually, the system needs to be restarted.. The Log is as follows: 101001 19:19:24 InnoDB: Log file. \ ib_logfile0 did not exist: new to be createdInnoDB: Setting log file. \ ib_logfile0 size to 109 MBInnoDB: Database physically writes the file full: wait... innoDB: Progress in MB: 100101001 19:19:26 InnoDB: Log file. \ ib_logfile1 did not exist: new to be createdInnoDB: Setting log file. \ ib_logfile1 size to 109 MBInnoDB: Database physically writes the file full: wait... innoDB: Progress in MB: 100 InnoDB: Cannot initialize created log files becauseInnoDB: data files are stored upt, or new data files wereInnoDB: created when the database was started previusinnodb: time but the database was not shut downInnoDB: normally after that.101001 19:19:27 [ERROR] Default storage engine (InnoDB) is not available101001 19:19:27 [ERROR] Aborting
101001 19:19:27 [Note] D: \ MySQL5 \ bin \ mysqld-nt: Shutdown complete
Now there is only one last problem. Default storage engine (InnoDB) is not available. Go to services. msc to start the MySQL service, or an error occurs. However, the log shows 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 managedInnoDB: to create the InnoDB data files, but log file creation failed. innoDB: If that is the case, please refer toInnoDB: http://dev.mysql.com/doc/mysql/en/Error_creating_InnoDB.html101001 20:45:09 [ERROR] Default storage engine (InnoDB) is not available101001 20:45:09 [ERROR] Aborting
101001 20:45:09 [Note] D: \ MySQL5 \ bin \ mysqld-nt: Shutdown complete
So I searched the internet and found that the prompt "No valid checkpoint found." was displayed.
