mysql 5.5.42升級到5.6.24步驟
1、第一步:
首先找到5.6的yum源頭;
wget
rpm -ivh mysql-community-release-el6-5.noarch.rpm
yum -y update mysql-server
2、mysql5.6與mysql5.5的不同之處如下:
mysql 5.6會多五張表,分別為:slave_master_info
slave_relay_log_info
slave_worker_info
innodb_index_stats
innodb_table_stats
重啟mysql
3、檢查和執行mysql 資料庫表操作:
執行如下命令:
mysql_upgrade -uroot -h192.168.30.167 -p
輸入密碼即可;
如果這個地方執行不下去,可依次執行如下語句,逐條進行排錯:
mysqlcheck --all-databases --check-upgrade --auto-repair
mysql < fix_priv_tables
mysqlcheck --all-databases --check-upgrade --fix-db-names --fix-table-names
這步都ok之後,可嘗試進行第五步操作。
4、重啟mysqld,登陸進行驗證;看這五張表是否存在,或者檢視mysqld的錯誤日誌,看其是否報錯;
5、如果報錯,可登陸mysql;使用如下語句建表:
1、innodb_index_stats
CREATE TABLE IF NOT EXISTS innodb_index_stats ( database_name VARCHAR(64) NOT NULL, table_name VARCHAR(64) NOT NULL, index_name VARCHAR(64) NOT NULL, last_update TIMESTAMP NOT NULL NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP, /* there are at least: stat_name='size' stat_name='n_leaf_pages' stat_name='n_diff_pfx%' */ stat_name VARCHAR(64) NOT NULL, stat_value BIGINT UNSIGNED NOT NULL, sample_size BIGINT UNSIGNED, stat_description VARCHAR(1024) NOT NULL, PRIMARY KEY (database_name, table_name, index_name, stat_name) ) ENGINE=INNODB DEFAULT CHARSET=utf8 COLLATE=utf8_bin STATS_PERSISTENT=02、inndb_table_stats
CREATE TABLE IF NOT EXISTS innodb_table_stats ( database_name VARCHAR(64) NOT NULL, table_name VARCHAR(64) NOT NULL, last_update TIMESTAMP NOT NULL NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP, n_rows BIGINT UNSIGNED NOT NULL, clustered_index_size BIGINT UNSIGNED NOT NULL, sum_of_other_index_sizes BIGINT UNSIGNED NOT NULL, PRIMARY KEY (database_name, table_name) ) ENGINE=INNODB3、 slave_master_info;
CREATE TABLE `slave_master_info` (
`Number_of_lines` int(10) unsigned NOT NULL COMMENT 'Number of lines in the file.',
`Master_log_name` text CHARACTER SET utf8 COLLATE utf8_bin NOT NULL COMMENT 'The name of the master binary log currently being read from the master.',
`Master_log_pos` bigint(20) unsigned NOT NULL COMMENT 'The master log position of the last read event.',
`Host` char(64) CHARACTER SET utf8 COLLATE utf8_bin NOT NULL DEFAULT '' COMMENT 'The host name of the master.',
`User_name` text CHARACTER SET utf8 COLLATE utf8_bin COMMENT 'The user name used to connect to the master.',
`User_password` text CHARACTER SET utf8 COLLATE utf8_bin COMMENT 'The password used to connect to the master.',
`Port` int(10) unsigned NOT NULL COMMENT 'The network port used to connect to the master.',
`Connect_retry` int(10) unsigned NOT NULL COMMENT 'The period (in seconds) that the slave will wait before trying to reconnect to the master.',
`Enabled_ssl` tinyint(1) NOT NULL COMMENT 'Indicates whether the server supports SSL connections.',
`Ssl_ca` text CHARACTER SET utf8 COLLATE utf8_bin COMMENT 'The file used for the Certificate Authority (CA) certificate.',
`Ssl_capath` text CHARACTER SET utf8 COLLATE utf8_bin COMMENT 'The path to the Certificate Authority (CA) certificates.',
`Ssl_cert` text CHARACTER SET utf8 COLLATE utf8_bin COMMENT 'The name of the SSL certificate file.',
`Ssl_cipher` text CHARACTER SET utf8 COLLATE utf8_bin COMMENT 'The name of the cipher in use for the SSL connection.',
`Ssl_key` text CHARACTER SET utf8 COLLATE utf8_bin COMMENT 'The name of the SSL key file.',
`Ssl_verify_server_cert` tinyint(1) NOT NULL COMMENT 'Whether to verify the server certificate.',
`Heartbeat` float NOT NULL,
`Bind` text CHARACTER SET utf8 COLLATE utf8_bin COMMENT 'Displays which interface is employed when connecting to the MySQL server',
`Ignored_server_ids` text CHARACTER SET utf8 COLLATE utf8_bin COMMENT 'The number of server IDs to be ignored, followed by the actual server IDs',
`Uuid` text CHARACTER SET utf8 COLLATE utf8_bin COMMENT 'The master server uuid.',
`Retry_count` bigint(20) unsigned NOT NULL COMMENT 'Number of reconnect attempts, to the master, before giving up.',
`Ssl_crl` text CHARACTER SET utf8 COLLATE utf8_bin COMMENT 'The file used for the Certificate Revocation List (CRL)',
`Ssl_crlpath` text CHARACTER SET utf8 COLLATE utf8_bin COMMENT 'The path used for Certificate Revocation List (CRL) files',
`Enabled_auto_position` tinyint(1) NOT NULL COMMENT 'Indicates whether GTIDs will be used to retrieve events from the master.',
PRIMARY KEY (`Host`,`Port`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 STATS_PERSISTENT=0 COMMENT='Master Information' |
4、slave_worker_info
CREATE TABLE `slave_worker_info` (
`Id` int(10) unsigned NOT NULL,
`Relay_log_name` text CHARACTER SET utf8 COLLATE utf8_bin NOT NULL,
`Relay_log_pos` bigint(20) unsigned NOT NULL,
`Master_log_name` text CHARACTER SET utf8 COLLATE utf8_bin NOT NULL,
`Master_log_pos` bigint(20) unsigned NOT NULL,
`Checkpoint_relay_log_name` text CHARACTER SET utf8 COLLATE utf8_bin NOT NULL,
`Checkpoint_relay_log_pos` bigint(20) unsigned NOT NULL,
`Checkpoint_master_log_name` text CHARACTER SET utf8 COLLATE utf8_bin NOT NULL,
`Checkpoint_master_log_pos` bigint(20) unsigned NOT NULL,
`Checkpoint_seqno` int(10) unsigned NOT NULL,
`Checkpoint_group_size` int(10) unsigned NOT NULL,
`Checkpoint_group_bitmap` blob NOT NULL,
PRIMARY KEY (`Id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 STATS_PERSISTENT=0 COMMENT='Worker Information'
5、
CREATE TABLE `slave_relay_log_info` (
`Number_of_lines` int(10) unsigned NOT NULL COMMENT 'Number of lines in the file or rows in the table. Used to version table definitions.',
`Relay_log_name` text CHARACTER SET utf8 COLLATE utf8_bin NOT NULL COMMENT 'The name of the current relay log file.',
`Relay_log_pos` bigint(20) unsigned NOT NULL COMMENT 'The relay log position of the last executed event.',
`Master_log_name` text CHARACTER SET utf8 COLLATE utf8_bin NOT NULL COMMENT 'The name of the master binary log file from which the events in the relay log file were read.',
`Master_log_pos` bigint(20) unsigned NOT NULL COMMENT 'The master log position of the last executed event.',
`Sql_delay` int(11) NOT NULL COMMENT 'The number of seconds that the slave must lag behind the master.',
`Number_of_workers` int(10) unsigned NOT NULL,
`Id` int(10) unsigned NOT NULL COMMENT 'Internal Id that uniquely identifies this record.',
PRIMARY KEY (`Id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 STATS_PERSISTENT=0 COMMENT='Relay Log Information'
6、確保上面五張表都正確之後,重啟資料庫,就不會再有報錯資訊出現。
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/30129545/viewspace-1654589/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- MySQL 5.6.19升級到 5.7.9 步驟介紹MySql
- MySQL 5.6.27升級MySQL 5.7.18版本的升級步驟介紹MySql
- CentOS升級MySQL到5.5CentOSMySql
- MySQL 5.7 升級到 8.0MySql
- mysql 資料sqoop到hive 步驟MySqlOOPHive
- oracle 10.1.0.2 升級到10.2.0.4 步驟Oracle
- MySQL 升級詳細步驟 (包括 Percona)MySql
- MySQL 5.6.47升級到5.7.20(一)MySql
- AIX 5.3下 升級補丁到10.2.0.5步驟AI
- Oracle資料庫從 9.2.0.1 到 9.2.0.8升級步驟 for winOracle資料庫
- oracle 10.2.0.4 rac 升級到oracle 10.2.0.5 rac步驟Oracle
- Windows下Mysql5.6升級到5.7WindowsMySql
- MySQL5.5升級到MySQL5.7踩坑日記MySql
- Win8.1 Update降級到Win8.1的操作步驟
- 從 Angular 1 升級到 Angular 2 需要準備的步驟Angular
- Oracle資料庫從 9.2.0.1 到 9.2.0.8升級步驟for linuxOracle資料庫Linux
- 最少步驟安裝ora10g,升級到10.1.0.3
- MySQL升級從5.1.71到5.7.17版本MySql
- windows10怎樣升級到10586_windows10電腦升級到10586詳細步驟Windows
- 探索Oracle之資料庫升級二 11.2.0.3升級到11.2.0.4完整步驟Oracle資料庫
- 原始碼安裝mysql5.5.20升級到mysql5.6.25原始碼MySql
- 【UPGRADE】升級到Oracle18c基本步驟參考(留存)Oracle
- Oracle從10g升級到11g詳細步驟Oracle
- 9I 資料庫升級到10g的步驟資料庫
- Oracle10.2.0.1 升級到Oracle10.2.0.4 簡單步驟Oracle
- 部署MySQL步驟MySql
- oracle升級步驟Oracle
- Centos 7 升級通過 yum 安裝的 MySQL 5.7 到 MySQL 8.0CentOSMySql
- Oracle從10g升級到11g詳細操作步驟Oracle
- GitHub是怎樣把MySQL 5.7升級到8.0的?GithubMySql
- 升級到 MySQL 8.4,MySQL 啟動報錯:io_setup() failed with EAGAINMySqlAI
- linux 核心升級步驟,kernel升級Linux
- 允許遠端連線到MySQL資料庫伺服器的步驟MySql資料庫伺服器
- 不可不知的 MySQL 升級利器及 5.7 升級到 8.0 的注意事項MySql
- 升級到MySQL5.7版本需注意的問題MySql
- 升級到MySQL 5.0.17一定遇到的四個問題MySql
- Discuz論壇2.5 升級到PHP MySQL新版遇到的問題PHPMySql
- mysql升級MySql