您好,登錄后才能下訂單哦!
Part1:寫在最前
提到MySQL升級,網上文章數之不盡,但大多數為老的版本,諸如5.1升級到5.5、5.5升級到5.6,今天給大家介紹下MySQL5.6升級到MySQL5.7版本的方法和注意事項。
Part2:升級方法
升級的方法一般有兩類:
1.利用mysqldump來直接導出sql文件,導入到新庫中,這種方法是最省事兒的,也是最保險的,缺點的話,也顯而易見,大庫的mysqldump費時費力。
2.直接替換掉mysql的安裝目錄和my.cnf,利用mysql_upgrade 來完成系統表的升級,這種方法需要備份原有的文件,但屬于物理拷貝,速度較快。缺點的話,跨版本升級不推薦這么做,比如mysql5.1升級到mysql5.6,mysql5.5升級到mysql5.7等。
本文采用的是第二種方法升級。
Part3:環境
數據庫軟件目錄:/usr/local/mysql
my.cnf位置:/etc/my.cnf
數據庫data目錄:/data/mysql
慢日志目錄:/data/slowlog
Part1:MySQL5.6.25
[root@HE3 ~]# mysql -uroot -p Enter password: Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 1 Server version: 5.6.25-log MySQL Community Server (GPL) Copyright (c) 2000, 2015, Oracle and/or its affiliates. All rights reserved. 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> select version(); +------------+ | version() | +------------+ | 5.6.25-log | +------------+ 1 row in set (0.00 sec) mysql> use helei; Database changed mysql> show tables; +-----------------+ | Tables_in_helei | +-----------------+ | helei | +-----------------+ 1 row in set (0.00 sec)
我這里用的是5.6.25版本作為待升級庫,庫中已經模擬和創建了數據庫helei和表helei,用以之后驗證升級。
Part2:備份
備份整體需要備份的是my.cnf、數據庫安裝目錄、還有數據目錄。
[root@HE3 ~]# /etc/init.d/mysqld stop
Shutting down MySQL.. SUCCESS!
[root@HE3 etc]# cp -rp my.cnf my_56_old.cnf
[root@HE3 local]# cp -rp mysql mysql_56_old
[root@HE3 ~]# rm -rf /usr/local/mysql
[root@HE3 data]# cp -rp mysql/ mysql_56_old
這里我直接采用cp的方式來進行。
Part3:替換
1.替換/etc/my.cnf為mysql5.7的my.cnf
[root@HE3 ~]#vi /etc/my.cnf [client] port=3306 socket=/tmp/mysql.sock default-character-set=utf8 [mysql] no-auto-rehash default-character-set=utf8 [mysqld] port=3306 character-set-server=utf8 socket=/tmp/mysql.sock basedir=/usr/local/mysql datadir=/data/mysql explicit_defaults_for_timestamp=true lower_case_table_names=1 back_log=103 max_connections=3000 max_connect_errors=100000 table_open_cache=512 external-locking=FALSE max_allowed_packet=32M sort_buffer_size=2M join_buffer_size=2M thread_cache_size=51 query_cache_size=32M #query_cache_limit=4M transaction_isolation=REPEATABLE-READ tmp_table_size=96M max_heap_table_size=96M ###***slowqueryparameters long_query_time=1 slow_query_log = 1 slow_query_log_file=/data/slowlog/slow.log ###***binlogparameters log-bin=mysql-bin binlog_cache_size=4M max_binlog_cache_size=8M max_binlog_size=1024M binlog_format=MIXED expire_logs_days=7 ###***relay-logparameters #relay-log=/data/3307/relay-bin #relay-log-info-file=/data/3307/relay-log.info #master-info-repository=table #relay-log-info-repository=table #relay-log-recovery=1 #***MyISAMparameters key_buffer_size=16M read_buffer_size=1M read_rnd_buffer_size=16M bulk_insert_buffer_size=1M #skip-name-resolve ###***master-slavereplicationparameters server-id=$SERVERID slave-skip-errors=all #***Innodbstorageengineparameters innodb_buffer_pool_size=512M innodb_data_file_path=ibdata1:10M:autoextend #innodb_file_io_threads=8 innodb_thread_concurrency=16 innodb_flush_log_at_trx_commit=1 innodb_log_buffer_size=16M innodb_log_file_size=512M innodb_log_files_in_group=2 innodb_max_dirty_pages_pct=75 innodb_buffer_pool_dump_pct=50 innodb_lock_wait_timeout=50 innodb_file_per_table=on innodb_buffer_pool_dump_at_shutdown=1 innodb_buffer_pool_load_at_startup=1 sql_mode=STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION [mysqldump] quick max_allowed_packet=32M [myisamchk] key_buffer=16M sort_buffer_size=16M read_buffer=8M write_buffer=8M [mysqld_safe] open-files-limit=8192 log-error=/data/mysql/error.log pid-file=/data/mysql/mysqld.pid
2.解壓新版mysql
[root@HE3 ~]# tar xvf mysql-5.7.15-linux-glibc2.5-x86_64.tar.gz
[root@HE3 ~]# mv mysql-5.7.15-linux-glibc2.5-x86_64 /usr/local/mysql
[root@HE3 ~]# chown -R mysql. /usr/local/mysql
3.替換新版mysqld啟動腳本
[root@HE3 ~]# cp /usr/local/mysql/support-files/mysql.server /etc/init.d/mysqld
cp: overwrite `/etc/init.d/mysqld'? y
Part1:啟動
[root@HE3 ~]# /etc/init.d/mysqld start Starting MySQL..... SUCCESS! [root@HE3 ~]# ps -ef|grep mysql root 26467 1 0 20:30 pts/2 00:00:00 /bin/sh /usr/local/mysql/bin/mysqld_safe --datadir=/data/mysql --pid-file=/data/mysql/HE3.pid mysql 27197 26467 4 20:30 pts/2 00:00:01 /usr/local/mysql/bin/mysqld --basedir=/usr/local/mysql --datadir=/data/mysql --plugin-dir=/usr/local/mysql/lib/plugin --user=mysql --log-error=/data/mysql/error.log --open-files-limit=8192 --pid-file=/data/mysql/HE3.pid --socket=/tmp/mysql.sock --port=3306 root 27235 25656 0 20:31 pts/2 00:00:00 grep mysql
這里雖然啟動成功了,但error日志里能捕捉到很多錯誤信息,因為沒有升級字典,諸如:
2016-10-20T03:30:27.375466Z 0 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_program' has the wrong structure 2016-10-20T03:30:27.375506Z 0 [ERROR] Native table 'performance_schema'.'events_transactions_current' has the wrong structure 2016-10-20T03:30:27.375536Z 0 [ERROR] Native table 'performance_schema'.'events_transactions_history' has the wrong structure 2016-10-20T03:30:27.375568Z 0 [ERROR] Native table 'performance_schema'.'events_transactions_history_long' has the wrong structure 2016-10-20T03:30:27.375598Z 0 [ERROR] Native table 'performance_schema'.'events_transactions_summary_by_thread_by_event_name' has the wrong structure
Part2:系統表升級
1.升級數據字典
[root@HE3 ~]# /usr/local/mysql/bin/mysql_upgrade -uroot -pMANAGER mysql_upgrade: [Warning] Using a password on the command line interface can be insecure. Checking if update is needed. Checking server version. Running queries to upgrade MySQL server. Checking system database. mysql.columns_priv OK mysql.db OK mysql.engine_cost OK mysql.event OK mysql.func OK mysql.general_log OK mysql.gtid_executed OK mysql.help_category OK mysql.help_keyword OK mysql.help_relation OK mysql.help_topic OK mysql.innodb_index_stats OK mysql.innodb_table_stats OK mysql.ndb_binlog_index OK mysql.plugin OK mysql.proc OK mysql.procs_priv OK mysql.proxies_priv OK mysql.server_cost OK mysql.servers OK mysql.slave_master_info OK mysql.slave_relay_log_info OK mysql.slave_worker_info OK mysql.slow_log OK mysql.tables_priv OK mysql.time_zone OK mysql.time_zone_leap_second OK mysql.time_zone_name OK mysql.time_zone_transition OK mysql.time_zone_transition_type OK mysql.user OK Upgrading the sys schema. Checking databases. helei.helei OK sys.sys_config OK Upgrade process completed successfully. Checking if update is needed.
2.重啟實例再次檢查error日志
[root@HE3 ~]# /etc/init.d/mysqld restart
Shutting down MySQL.. SUCCESS!
Starting MySQL. SUCCESS!
3.請保證一些路徑的設置和以前的my.cnf一致,如果設置錯誤,很可能導致啟動不了數據庫
[ERROR] Could not use /data/slowlog/slow.log for logging
我這里是由于慢日志的位置和老的mysql5.6路徑不一致,創建/data/slowlog即可,這里要仔細看報錯,然后根據報錯來發現和解決問題。
Part1:輸入用戶名密碼檢查結果
[root@HE3 ~]# mysql -uroot -p Enter password: Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 2 Server version: 5.7.15-log MySQL Community Server (GPL) Copyright (c) 2000, 2016, Oracle and/or its affiliates. All rights reserved. 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> select version(); +------------+ | version() | +------------+ | 5.7.15-log | +------------+ 1 row in set (0.00 sec)
Part2:驗證庫和表是否有丟失
mysql> show databases; +--------------------+ | Database | +--------------------+ | information_schema | | helei | | mysql | | performance_schema | | sys | | test | +--------------------+ 6 rows in set (0.00 sec)
升級5.7后,我們會發現多了一個sys庫,這個庫有很多的功能,以后再給大家慢慢介紹~
——總結——
MySQL升級有多種方式,但無論采用何種方式,都要做好備份和回滾的準備,以避免升級失敗所帶來的損失。由于筆者的水平有限,編寫時間也很倉促,文中難免會出現一些錯誤或者不準確的地方,不妥之處懇請讀者批評指正。
免責聲明:本站發布的內容(圖片、視頻和文字)以原創、轉載和分享為主,文章觀點不代表本網站立場,如果涉及侵權請聯系站長郵箱:is@yisu.com進行舉報,并提供相關證據,一經查實,將立刻刪除涉嫌侵權內容。