Shulou(Shulou.com)06/01 Report--

The following talk about MySQL official source from 8.0.3 directly through the yum source to 8.0.4 to start the unsuccessful solution, the secret of the text is close to the topic. So, forget the gossip, let's go straight to the following. I'm sure you'll benefit from the article that mysql official sources upgrade from 8.0.3 directly through yum sources to 8.0.4 after starting unsuccessful solutions.

CVM environment: centos7.4.14

Problem: mysql does not start properly

View the log

2018-02-23T02:10:08.371209Z 0 [System] [MY-010116] / usr/sbin/mysqld (mysqld 8.0.4-rc-log) starting as process 27702... 2018-02-23T02:10:08.737713Z 1 [ERROR] [MY-011096] No data dictionary version number found.2018-02-23T02:10:08.737989Z 0 [ERROR] [MY-010020] Data Dictionary initialization failed.2018-02-23T02:10:08.738038Z 0 [ERROR] [MY-010119] Aborting

Later, it was found that the caching_sha2_password authentication mechanism was enabled by default after the upgrade, and the previous data could not be run directly.

You can only restore the original version, export the data from the original version, re-import it for use, or upgrade and import it.

1. Uninstall 8.0.4

Backup data

Mv / var/lib/ {mysql,mysql.bak} chown-R mysql:mysql / var/lib/mysql.bakchmod 755-R / var/lib/mysql.bak

Direct yum uninstall

Rpm-qa | grep'^ mysql'

Then uninstall all the 8.0.4 packages queried by yum

II. Install 8.0.3

Download 8.0.3 from the official

Https://downloads.mysql.com/archives/community/

Download the packed version of mysql-8.0.3-0.1.rc.el7.x86_64.rpm-bundle.tar

Decompression

Tar-xvf mysql-8.0.3-0.1.rc.el7.x86_64.rpm-bundle.tar

Then install common, libs, client, server in turn

Rpm-ivh mysql-community-common-8.0.3-0.1.rc.el7.x86_64.rpmrpm-ivh mysql-community-libs-8.0.3-0.1.rc.el7.x86_64.rpmrpm-ivh mysql-community-client-8.0.3-0.1.rc.el7.x86_64.rpmrpm-ivh mysql-community-server-8.0.3-0.1.rc.el7.x86_64.rpm

Start mysql

Systemctl start msyqld.service

At this point / var/lib/ regenerates a new mysql folder

III. Data export

Modify / etc/my.cnf to point to old data

[mysqld] innodb_force_recovery = 6datadir=/var/lib/mysql.bak

Forcing InnoDB Recovery provides 6 levels of repair mode

Innodb_force_recovery reference: http://blog.csdn.net/weitao_11/article/details/55050200

Full library export:

Mysqldump-uroot-p-- all-databases > / home/sqlfile.sql

IV. Data recovery

Modify / etc/my.cnf data path, remove repair mode, not writable in repair mode

[mysqld] datadir=/var/lib/mysql

View temporary password

[root@soft] # cat / var/log/mysqld.log | grep password2018-02-23T08:06:36.785974Z 5 [Note] A temporary password is generated for root@localhost: Leyk2qO_75ER

Log in to mysql with a temporary password and change the password

Abandon the upgrade and import data directly

Mysql-uroot-pmysql > GRANT ALL PRIVILEGES ON *. * TO 'root'@'localhost' IDENTIFIED BY' abcdef@' WITH GRANT OPTION;mysql > flush privileges;mysql > source / home/sqlfile.sql

After rebooting, everything is fine. Be sure to back up before upgrading, be sure to back up frequently.

Is there anything you don't understand about the above mysql official source upgrading from 8.0.3 directly through the yum source to 8.0.4 after starting the unsuccessful solution? Or if you want to know more about it, you can continue to follow our industry information section.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.