实现：mysql-5.7.42 到 mysql-8.2.0 的升级（二进制方式）

注：本文在测试环境升级测试，建议先在测试环境验证。在生产环境下还是先评估下，mysql-5.7.42为二进制方式安装，所以用mysql-8.2.0二进制包升级

1、操作环境

1、查看当前数据库版本

mysql> select@@version;
+-----------+
| @@version |
+-----------+
| 5.7.42    |
+-----------+
1 row in set (0.00 sec)mysql> 

2、操作系统版本

[root@zyl-server ~]#  cat /etc/redhat-release
CentOS Linux release 7.9.2009 (Core)
[root@zyl-server ~]# 
[root@zyl-server ~]# 

3、查看 Linux 系统上的 glibc（GNU C 库）版本（这里很重要，要下载对应的内核mysql版本）

ldd --version或者
rpm -q glibc**查看当前系统中的libstdc++版本：**strings /usr/lib64/libstdc++.so.6 | grep GLIBCXX
strings /usr/lib64/libstdc++.so.6 | grep CXXABI
strings /usr/lib64/libstdc++.so.6 | grep GLIBC
strings /usr/lib64/libstdc++.so.6 | grep GLIBCXX

否则后面升级完成后，启动mysql会报错：

报错如下：

错误表明在启动MySQL服务时出现了一些问题。主要的错误信息是关于缺少特定库文件的版本，比如GLIBCXX_3.4.20、CXXABI_1.3.9、CXXABI_1.3.8、GLIBCXX_3.4.21以及GLIBC_2.25。

这是由于安装的MySQL版本与系统中可用的标准库版本不兼容导致的（所以要对应下载相应的内核版本）。

Mar 20 21:10:55 db-mysql mysqld[7127]: /usr/local/mysql/bin/my_print_defaults: /lib64/libstdc++.so.6: version `CXXABI_1.3.9' not found (required by /usr/local/mysql/bin/my_print_defaults)
Mar 20 21:10:55 db-mysql mysqld[7127]: /usr/local/mysql/bin/my_print_defaults: /lib64/libstdc++.so.6: version `CXXABI_1.3.8' not found (required by /usr/local/mysql/bin/my_print_defaults)
Mar 20 21:10:55 db-mysql mysqld[7127]: /usr/local/mysql/bin/my_print_defaults: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by /usr/local/mysql/bin/my_print_defaults)
Mar 20 21:10:55 db-mysql mysqld[7127]: /usr/local/mysql/bin/my_print_defaults: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by /usr/local/mysql/bin/../lib/private/libcrypto.so.3
Mar 20 21:10:55 db-mysql mysqld[7127]: /usr/local/mysql/bin/my_print_defaults: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by /usr/local/mysql/bin/my_print_defaults)
Mar 20 21:10:55 db-mysql mysqld[7127]: /usr/local/mysql/bin/my_print_defaults: /lib64/libstdc++.so.6: version `CXXABI_1.3.9' not found (required by /usr/local/mysql/bin/my_print_defaults)
Mar 20 21:10:55 db-mysql mysqld[7127]: /usr/local/mysql/bin/my_print_defaults: /lib64/libstdc++.so.6: version `CXXABI_1.3.8' not found (required by /usr/local/mysql/bin/my_print_defaults)
Mar 20 21:10:55 db-mysql mysqld[7127]: /usr/local/mysql/bin/my_print_defaults: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by /usr/local/mysql/bin/my_print_defaults)
Mar 20 21:10:55 db-mysql mysqld[7127]: /usr/local/mysql/bin/my_print_defaults: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by /usr/local/mysql/bin/../lib/private/libcrypto.so.3

2、升级准备

1、数据备份：在升级之前，务必对当前的 MySQL 5.7 数据库进行完整备份，以防止数据丢失或损坏。确保备份文件的安全存储，并测试其可恢复性。

2、安全性考虑：建议在测试环境中进行升级测试，以模拟真实场景并检测潜在问题。这有助于减少生产环境中的不确定性和风险。

1、使用mysql-shell 检查工具检查兼容性

下载地址：https://downloads.mysql.com/archives/shell/

上传mysql-shell：

安装 mysql-shell rpm 软件包：：

rpm -Uvh mysql-shell-8.2.0-1.el7.x86_64.rpm --force --nodeps

查看 mysql-shel安装版本：

mysqlsh --version

检查该版本是否可以升级到MySQL 8.2.0：

mysqlsh -uroot -p -S /tmp/mysqld.sock -e "util.checkForServerUpgrade()" 

注意:mysql.sock 地址在/etc/my.cnf 文件中查看。

检查结果报告：

[root@db-mysql ~]# mysqlsh -uroot -p -S /tmp/mysqld.sock -e "util.checkForServerUpgrade()" 
Please provide the password for 'root@/tmp%2Fmysqld.sock': ******
Save password for 'root@/tmp%2Fmysqld.sock'? [Y]es/[N]o/Ne[v]er (default No): 
The MySQL server at /tmp%2Fmysqld.sock, version 5.7.42 - MySQL Community Server
(GPL), will now be checked for compatibility issues for upgrade to MySQL
8.2.0...1) Usage of old temporal typeNo issues found2) MySQL 8.0 syntax check for routine-like objectsNo issues found3) Usage of db objects with names conflicting with new reserved keywordsNo issues found4) Usage of utf8mb3 charsetWarning: The following objects use the utf8mb3 character set. It isrecommended to convert them to use utf8mb4 instead, for improved Unicodesupport.More information:https://dev.mysql.com/doc/refman/8.0/en/charset-unicode-utf8mb3.htmldb_update - schema's default character set: utf8db_update.users.name - column's default character set: utf8db_update.users.email - column's default character set: utf85) Table names in the mysql schema conflicting with new tables in 8.0No issues found6) Partitioned tables using engines with non native partitioningNo issues found7) Foreign key constraint names longer than 64 charactersNo issues found8) Usage of obsolete MAXDB sql_mode flagNo issues found9) Usage of obsolete sql_mode flagsNotice: The following DB objects have obsolete options persisted forsql_mode, which will be cleared during upgrade to 8.0.More information:https://dev.mysql.com/doc/refman/8.0/en/mysql-nutshell.html#mysql-nutshell-removalsglobal system variable sql_mode - defined using obsolete NO_AUTO_CREATE_USERoption10) ENUM/SET column definitions containing elements longer than 255 charactersNo issues found11) Usage of partitioned tables in shared tablespacesNo issues found12) Circular directory references in tablespace data file pathsNo issues found13) Usage of removed functionsNo issues found14) Usage of removed GROUP BY ASC/DESC syntaxNo issues found15) Removed system variables for error logging to the system log configurationTo run this check requires full path to MySQL server configuration file to be specified at 'configPath' key of options dictionaryMore information:https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-13.html#mysqld-8-0-13-logging16) Removed system variablesTo run this check requires full path to MySQL server configuration file to be specified at 'configPath' key of options dictionaryMore information:https://dev.mysql.com/doc/refman/8.0/en/added-deprecated-removed.html#optvars-removed17) System variables with new default valuesTo run this check requires full path to MySQL server configuration file to be specified at 'configPath' key of options dictionaryMore information:https://mysqlserverteam.com/new-defaults-in-mysql-8-0/18) Zero Date, Datetime, and Timestamp valuesNo issues found19) Schema inconsistencies resulting from file removal or corruptionNo issues found20) Tables recognized by InnoDB that belong to a different engineNo issues found21) Issues reported by 'check table x for upgrade' commandNo issues found22) New default authentication plugin considerationsWarning: The new default authentication plugin 'caching_sha2_password' offersmore secure password hashing than previously used 'mysql_native_password'(and consequent improved client connection authentication). However, it alsohas compatibility implications that may affect existing MySQL installations. If your MySQL installation must serve pre-8.0 clients and you encountercompatibility issues after upgrading, the simplest way to address thoseissues is to reconfigure the server to revert to the previous defaultauthentication plugin (mysql_native_password). For example, use these linesin the server option file:[mysqld]default_authentication_plugin=mysql_native_passwordHowever, the setting should be viewed as temporary, not as a long term orpermanent solution, because it causes new accounts created with the settingin effect to forego the improved authentication security.If you are using replication please take time to understand how theauthentication plugin changes may impact you.More information:https://dev.mysql.com/doc/refman/8.0/en/upgrading-from-previous-series.html#upgrade-caching-sha2-password-compatibility-issueshttps://dev.mysql.com/doc/refman/8.0/en/upgrading-from-previous-series.html#upgrade-caching-sha2-password-replication23) Columns which cannot have default valuesNo issues found24) Check for invalid table names and schema names used in 5.7No issues found25) Check for orphaned routines in 5.7No issues found26) Check for deprecated usage of single dollar signs in object namesNo issues found27) Check for indexes that are too large to work on higher versions of MySQL
Server than 5.7No issues found28) Check for deprecated '.<table>' syntax used in routines.No issues found29) Check for columns that have foreign keys pointing to tables from a diffrent
database engine.No issues foundErrors:   0
Warnings: 4
Notices:  1NOTE: No fatal errors were found that would prevent an upgrade, but some potential issues were detected. Please ensure that the reported issues are not significant before upgrading.

检查结果显示：

没有发现使用旧时态类型的问题
没有发现与MySQL 8.0语法相关的问题
没有发现与数据库对象名称与新保留关键字冲突的问题
发现某些对象使用了utf8mb3字符集，建议转换为utf8mb4以获得更好的Unicode支持
没有发现与mysql模式中的表名冲突的问题
没有发现使用具有非本地分区的引擎的分区表的问题
没有发现外键约束名称超过64个字符的问题
没有发现使用已弃用的MAXDB sql_mode标志的问题
发现一些DB对象已经使用了过时的sql_mode选项
没有发现ENUM/SET列定义中包含超过255个字符的元素的问题
没有发现在共享表空间中使用分区表的问题
没有发现表空间数据文件路径中存在循环目录引用的问题
没有发现使用已删除函数的问题
没有发现已删除的GROUP BY ASC/DESC语法的问题
无法运行需要指定完整MySQL服务器配置文件路径的日志系统变量检查
无法运行需要指定完整MySQL服务器配置文件路径的已删除系统变量检查
无法运行需要指定完整MySQL服务器配置文件路径的新默认值系统变量检查
没有发现零日期、日期时间和时间戳值的问题
没有发现由文件删除或损坏导致的模式不一致的问题
没有发现被InnoDB识别为属于不同引擎的表的问题
没有发现通过'check table x for upgrade'命令报告的问题
发现新的默认身份验证插件引入了兼容性问题，建议在升级后重新配置服务器以恢复到以前的默认身份验证插件
没有发现不能有默认值的列的问题
没有发现在5.7中使用的无效表名和模式名的问题
没有发现在5.7中遗留存储过程的问题
没有发现在对象名称中使用单个美元符号的已弃用用法
没有发现在高于MySQL Server 5.7版本上工作的索引过大的问题
没有发现在例程中使用已弃用'.<table>'语法的问题
没有发现具有外键指向不同数据库引擎的表的列的问题总结：错误：0
警告：4
注意事项：1

总结来说，检查未发现会阻止升级的致命错误，但检测到了一些潜在问题。在升级之前，请确保报告的问题并不重要。

3、mysqldump 导出数据文件和备份my.cnf

[root@db-mysql ~]#  mysqldump -hlocalhost -uroot -p --all-databases > /home/db_back_2024.sql
Enter password: 
[root@db-mysql ~]# cd /home/                 
[root@db-mysql home]# ll
total 872
-rw-r--r--  1 root   root     889253 Mar 20 20:25 db_back_2024.sql
drwx------  2 oracle oinstall    127 Mar 18 05:12 oracle
drwx------. 2 zyl    zyl          62 Mar 16 22:24 zyl
[root@db-mysql home]# cp /etc/my.cnf /home/5.7.37_my.cnf[root@zyl-mysql home]# 

升级前先停止数据库。

[root@db-mysql home]# systemctl stop mysqld

4、备份旧版mysql-5.7.42 安装目录下的文件和my.cnf文件（重要）

这里的安装目录在/usr/local/mysql，根据自己实际备份。

cd /usr/local/mkdir mysql-5.7.42_bk##全部备份 mysql目录下的文件
cp -R mysql/* mysql-5.7.42_bk### 或者直接压缩
### tar -zcvf mysql-5.7.42_bk.tar.gz mysql
[root@db-mysql bin]# tar zcf mysql-5.7.42_bk.tar.gz mysql

5、删除旧版安装目录/usr/local/mysql下(bin、docs、includ、lib、share、support-files、LICENSE、README)；

cd /usr/local/mysqlrm -rf bin
rm -rf docs
rm -rf include
rm -rf lib
rm -rf README
rm -rf LICENSE
rm -rf share
rm -rf support-files
rm -rf man

6、备份mysqld 启动文件

先备份/etc/init.d/ 下的mysqld 再 删除/etc/init.d/ 下的mysqld

cd /etc/init.d/tar zcf mysqld_5.7.42.tar.gz mysqldrm -rf /etc/init.d/mysqld

7、上传、解压安装包（开始升级）

下载mysql8.2.0:

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

创建"mysql8.2.0-glibc"的文件夹，用于存放解压文件。

mkdir /root/mysql8.2.0-glibc##解压
tar -xvf mysql-8.2.0-linux-glibc2.28-x86_64.tar -C /root/mysql8.2.0-glibc

##继续解压 
cd /root/mysql8.2.0-glibctar -xvf mysql-8.2.0-linux-glibc2.28-x86_64.tar.xz

将新解压的mysql-8.2.0目录复制到原来mysql安装目录下（/usr/local/mysql/），并修改文件权限。

[root@db-mysql mysql8.2.0-glibc]# mv mysql-8.2.0-linux-glibc2.17-x86_64/* /usr/local/mysql

##修改文件权限chown -R mysql:mysql /usr/local/mysql

8、复制新版启动文件到/etc/init.d/

将新解压的mysql-8.2.0 的mysqld复制到/etc/init.d/ 下。

cp /usr/local/mysql/support-files/mysql.server /etc/init.d/mysqld

9、修改mysqld参数

vi /etc/init.d/mysqld

和旧版保持一致。

datadir=/usr/local/mysql/data
basedir=/usr/local/mysql

10、启动数据库

[root@db-mysql ~]# systemctl daemon-reload
[root@db-mysql ~]# 
[root@db-mysql ~]# systemctl start mysqld
[root@db-mysql ~]# 
[root@db-mysql ~]# systemctl status mysqld

11、升级验证

1、检查登录正常

mysql -u root -p[root@db-mysql mysql]# mysql -u root -p
Enter password: 
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 10
Server version: 8.2.0 MySQL Community Server - GPLCopyright (c) 2000, 2023, Oracle and/or its affiliates.Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.mysql> 

2、检查升级版本

已由mysql-5.7.42 升级到 mysql-8.2.0 。

mysql> select@@version;
+-----------+
| @@version |
+-----------+
| 8.2.0     |
+-----------+
1 row in set (0.00 sec)mysql> 

3、检查数据

mysql> show databases;
+--------------------+
| Database           |
+--------------------+
| db_update          |
| information_schema |
| mysql              |
| performance_schema |
| sys                |
+--------------------+
5 rows in set (0.01 sec)mysql> use db_update;
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -ADatabase changed
mysql> show tables;
+---------------------+
| Tables_in_db_update |
+---------------------+
| users               |
+---------------------+
1 row in set (0.00 sec)mysql> select * from users;
+----+---------+------+---------------------+
| id | name    | age  | email               |
+----+---------+------+---------------------+
|  1 | Alice   |   25 | alice@example.com   |
|  2 | Bob     |   30 | bob@example.com     |
|  3 | Charlie |   22 | charlie@example.com |
|  4 | David   |   28 | david@example.com   |
|  5 | Eve     |   35 | eve@example.com     |
+----+---------+------+---------------------+
5 rows in set (0.00 sec)mysql> 

❤️‍🔥 写在最后：一定要下载与Linux 系统上的 glibc（GNU C 库）版本对应的mysql版本）