MYSQL問題解決

標籤：

1、MySQL錯誤記錄檔裡出現：140331 10:08:18 [ERROR] Error reading master configuration140331 10:08:18 [ERROR] Failed to initialize the master info structure140331 10:08:18 [Note] Event Scheduler: Loaded 0 events 從錯誤提示就可以看出和mster info相關，找到資料目錄下的master.info檔案，直接cat查看# cat master.info  18luocs-mysql- bin.0000042671.1.1.1rep1PASSWORD3306600     01800.000 0 可以看出格式不對，解決方案非常簡單，reset slave即可，這樣將會清空master.info檔案，錯誤也將消失。 ———————————————————————————————————————————————————————–2、MySQL 往一張大表添加欄位時報如下錯誤：ERROR 1799 (HY000) at line 1: Creating index ‘PRIMARY‘ required more than ‘innodb_online_alter_log_max_size‘ bytes of modification log. Please try again.  解決方案：我的資料庫為MySQL 5.5版本，innodb_online_alter_log_max_size值為預設大小128M。mysql> show variables like ‘innodb_online_alter_log_max_size‘;+——————————————+———————-+| Variable_name                            | Value                |+——————————————+———————-+| innodb_online_alter_log_max_size         | 134217728            |+——————————————+———————-+1 rows in set (0.00 sec) 該參數為動態參數且全域的，可通過如下命令加大mysql> set global innodb_online_alter_log_max_size=402653184;Query OK, 0 rows affected (0.03 sec) 加到合適大小，我往120G大小表裡添加欄位設定該值4G，成功執行。 ———————————————————————————————————————————————————————–3、MySQL日誌：140306 12:03:25  InnoDB: ERROR: the age of the last checkpoint is 9434024,InnoDB: which exceeds the log group capacity 9433498.InnoDB: If you are using big BLOB or TEXT rows, you must set theInnoDB: combined size of log files at least 10 times bigger than theInnoDB: largest such row. 應該是Innodb引擎下日誌大小設定過小導致的，某個事物產生大量日誌，但innodb_log_file_size設定過小，可以加大解決。 解決方案：直接貼網上找到的方法，如下STEP 01) Change the following in /etc/my.cnf[mysqld]innodb_log_buffer_size          = 32Minnodb_buffer_pool_size         = 3Ginnodb_log_file_size            = 768MSTEP 02) mysql -uroot -p -e"SET GLOBAL innodb_fast_shutdown = 0;"STEP 03) service mysql stopSTEP 04) rm -f /var/lib/mysql/ib_logfile*STEP 05) service mysql startI added SET GLOBAL innodb_fast_shutdown = 0;. What does that do? It forces InnoDB to completely purge transactional changes from all of InnoDB moving parts, including the transactional logs (ib_logfile0, ib_logfile1). Thus, there is no need to backup the old ib_logfile0, ib_logfile1. If deleting them makes you nervous, then make Step 04 mv /var/lib/mysql/ib_logfile* .. ———————————————————————————————————————————————————————–4、使用pt-online-schema-change工具添加欄位時，收到錯誤如下：# pt-online-schema-change –alter="add column tag_common text default null" –user=root –password=xxxxxxxx D=MYDB,t=MYTB –executeCannot connect to D=lsedata_13Q1,h=10.13.7.47,p=…,u=rootNo slaves found.  See –recursion-method if host BJL1-Y13-10-ops.gaoder.net has slaves.Not checking slave lag because no slaves were found and –check-slave-lag was not specified. # A software update is available:#   * Percona Toolkit 2.2.6 has a possible security issue (CVE-2014-2029) upgrade is recommended. The current version for Percona::Toolkit is 2.2.7. The table `MYDB`.`MYTB` has triggers.  This tool needs to create its own triggers, so the table cannot already have triggers. 這是MYTB表上之前就有觸發器的原因，可以從pt-online-schema-change的工作機制瞭解到： 1) 如果存在外鍵，根據alter-foreign-keys-method參數值，檢測外鍵相關的表，針對相應的設定進行處理；2) 建立一個新的表，表結構修改後的資料表，用於從來源資料表向新表中匯入資料；3) 建立觸發器，在複製資料開始之後，將對來源資料表繼續進行資料修改的操作記錄下來，以便在資料複製結束後執行這些操作，保證資料不會丟失；4) 複製資料，從來源資料表中複製資料到新表中；5) 修改外鍵相關的子表，根據修改後的資料，修改外部索引鍵關聯的子表；6) 更改來源資料表為old表，把新表更改為源表名，並將old表刪除；7) 刪除觸發器； pt-online-schema-change詳細文檔，請閱讀：http://www.percona.com/doc/percona-toolkit/2.1/pt-online-schema-change.html ———————————————————————————————————————————————————————–5、我們在使用mysqldump的時候可能會遇到如下錯誤：mysqldump: Got error: 1044: Access denied for user ‘lseread‘@‘IP‘ to database ‘lsedata_13q1‘ when doing LOCK TABLES 解決方案：加上–skip-lock-tables即可，類似如下：mysqldump -h1.1.1.1  -uuser   -ppassword   -P3306 mydb mytb –where "time <= cast(‘2014-04-03 16:00‘ as datetime)" –skip-lock-tables –default-character-set=utf8  > mytb.txt  MySQL5.6開始提供新特性GTID模式，我們的研發人員在我提供的從庫上dump的時候遇到如下警告：Warning: Using a password on the command line interface can be insecure.Warning: A partial dump from a server that has GTIDs will by default include the GTIDs of all transactions, even those that changed suppressed parts of the database. If you don‘t want to restore GTIDs, pass –set-gtid-purged=OFF. To make a complete dump, pass –all-databases –triggers –routines –events. 雖然有警告，但資料還是可以dump出來，鬱悶的是，想把dump檔案匯入到其他版本資料庫的時候將會遇到：ERROR 1839 (HY000) at line 24: @@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_MODE = ON. 參考如下文：gtid_executed:WHEN used WITH global scope, this variable contains a representation OF the SET OF ALL transactions that are logged IN the BINARY log. WHEN used WITH SESSION scope, it contains a representation OF the SET OF transactions that are written TO the cache IN the CURRENT SESSION.Issuing RESET MASTER causes the global VALUE (but NOT the SESSION VALUE) OF this variable TO be reset TO an empty string. 解決方案：dump的時候加上參數–gtid-mode=OFF，類似如下：mysqldump -h1.1.1.1  -uuser   -ppassword   -P3306 mydb mytb –where "time <= cast(‘2014-04-03 16:00‘ as datetime)" –skip-lock-tables –default-character-set=utf8 –gtid-mode=OFF > mytb.txt  ———————————————————————————————————————————————————————–6、給一張大表添加欄位，過了一段時間系統HANG住，添加欄位工作中斷。系統重啟之後，想重新添加欄位，卻遇到如下錯誤：mysql> alter table mytb add column yyy text default null;ERROR 1050 (42S01): Table ‘mydb/#sql-ib54‘ already exists 查看MySQL err日誌：2014-04-04 09:10:12 10578 [Note] /opt/mysql5.6/bin/mysqld: ready for connections.Version: ‘5.6.17-log‘  socket: ‘/opt/mysql5.6/data/mysql.sock‘  port: 3307  Source distribution2014-04-04 09:10:24 10578 [ERROR] InnoDB: Failed to find tablespace for table ‘"mydb"."#sql-ib54"‘ in the cache. Attempting to load the tablespace with space id 54.2014-04-04 09:10:24 52e55940  InnoDB: Operating system error number 2 in a file operation.InnoDB: The error means the system cannot find the path specified.2014-04-04 09:10:24 10578 [ERROR] InnoDB: Could not find a valid tablespace file for ‘mydb/#sql-ib54‘. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue. 查看資料目錄，有#開頭的一些檔案，如下：# ls– 其他表資訊忽略，之所以.ibd檔案較多是因為動作表mytb為分區表#sql-ib58.ibd  #sql-ib65.ibd #sql-1935_2.frm  #sql-ib59.ibd  #sql-ib66.ibd#sql-1935_2.par  #sql-ib60.ibd  #sql-ib67.ibd #sql-ib54.ibd    #sql-ib61.ibd#sql-ib55.ibd    #sql-ib62.ibd #sql-ib56.ibd    #sql-ib63.ibd #sql-ib57.ibd    #sql-ib64.ibd 這個問題我頭一次碰到，沒深入研究過其中細節，只是想著#開頭為臨時檔案，覺得可以rm，不猶豫直接刪掉。然後重啟資料庫，結果報了大量ERROR：2014-04-04 09:10:12 2b1b9b20dfe0  InnoDB: Operating system error number 2 in a file operation.InnoDB: The error means the system cannot find the path specified.InnoDB: If you are installing InnoDB, remember that you must createInnoDB: directories yourself, InnoDB does not create them.2014-04-04 09:10:12 10578 [ERROR] InnoDB: Could not find a valid tablespace file for ‘mydb/#sql-ib54‘. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.2014-04-04 09:10:12 10578 [ERROR] InnoDB: Tablespace open failed for ‘"mydb"."#sql-ib54"‘, ignored.2014-04-04 09:10:12 2b1b9b20dfe0  InnoDB: Operating system error number 2 in a file operation.InnoDB: The error means the system cannot find the path specified.InnoDB: If you are installing InnoDB, remember that you must createInnoDB: directories yourself, InnoDB does not create them.2014-04-04 09:10:12 10578 [ERROR] InnoDB: Could not find a valid tablespace file for ‘mydb/#sql-ib55‘. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.2014-04-04 09:10:12 10578 [ERROR] InnoDB: Tablespace open failed for ‘"mydb"."#sql-ib55"‘, ignored.…… 遇到問題需要淡定，我嘗試繼續添加欄位，但報錯依然。然後我閱讀了下錯誤記錄檔裡給出的http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html文章，才瞭解到，在獨立資料表空間模式下通過shell命令刪除表結構和資料表空間檔案的話就會遇到這種問題。 文中還給出了搶救方法，我找到了如下文段：Problem with Temporary Table If MySQL crashes in the middle of an ALTER TABLE operation, you may end up with an orphaned temporary table inside the InnoDB tablespace. Using the Table Monitor, you can see listed a table with a name that begins with #sql-. You can perform SQL statements on tables whose name contains the character “#” if you enclose the name within backticks. Thus, you can drop such an orphaned table like any other orphaned table using the method described earlier. To copy or rename a file in the Unix shell, you need to put the file name in double quotation marks if the file name contains “#”. 我就建立了一個新庫，建立了同結構的表，然後再該表上進行添加欄位操作，這時候新庫資料目錄下又產生#sql-開頭的檔案，我把這些檔案全部拷貝到原庫目錄下。接著全部改名，如下：# mv \#sql-2ff9_1.frm sql-2ff9_1.frm# mv \#sql-2ff9_1.par sql-2ff9_1.par# mv \#sql-ib82.ibd sql-ib82.ibd # mv \#sql-ib83.ibd sql-ib83.ibd # mv \#sql-ib84.ibd sql-ib84.ibd # mv \#sql-ib85.ibd sql-ib85.ibd # mv \#sql-ib86.ibd sql-ib86.ibd # mv \#sql-ib87.ibd sql-ib87.ibd # mv \#sql-ib88.ibd sql-ib88.ibd # mv \#sql-ib89.ibd sql-ib89.ibd # mv \#sql-ib90.ibd sql-ib90.ibd # mv \#sql-ib91.ibd sql-ib91.ibd # mv \#sql-ib92.ibd sql-ib92.ibd # mv \#sql-ib93.ibd sql-ib93.ibd # mv \#sql-ib94.ibd sql-ib94.ibd # mv \#sql-ib95.ibd sql-ib95.ibd  這樣show tables能查看錶資訊： mysql> show tables;+———————+| Tables_in_mydb   |+———————+| #mysql50#sql-2ff9_1 |+———————+1 rows in set (0.01 sec) 但悲劇的是，我嘗試刪除#mysql50#sql-2ff9_1這個表，卻始終沒能刪掉。時間耗得也不少，開發那邊一直在詢問進展。我就想到別的方案：該表rename，建立結構一樣的新表，導資料到新表，再往新表裡增加欄位，rename的表刪除。 實際證明此方案可行。就是資料量大，導資料過程時間長，當然增加欄位時間也一樣長。 那網上有些人說刪除ibdata1和ib_logfile0、1，然後重啟資料庫就可以解決，這方法可行嗎？答案當然是NO，在獨立資料表空間模式下，ibdata裡儲存資料字典以及UNDO資訊，刪除之後重啟資料庫將會產生全新的ibdata，也就是丟失了字典資訊和UNDO了。 到時候會出現如下現象：mysql> show tables;+——————-+| Tables_in_mydb |+——————-+| t1          |+——————-+1 rows in set (0.01 sec) mysql> select count(*) from t1;ERROR 1146 (42S02): Table ‘mydb.t1‘ doesn‘t exist
———————————————————————————————————————————————————————–

 

 

7、主從複製失敗，查看slave日誌如下錯誤：140405  4:16:12 [ERROR] Slave I/O: error reconnecting to master ‘[email protected]:3306‘ – retry-time: 60  retries: 86400, Error_code: 2003140405  6:53:12 [Note] Slave: connected to master ‘[email protected]:3306‘,replication resumed in log ‘mysql-bin.000275‘ at position 192295247140405  6:53:12 [ERROR] Error reading packet from server: Could not find first log file name in binary log index file ( server_errno=1236)140405  6:53:12 [ERROR] Slave I/O: Got fatal error 1236 from master when reading data from binary log: ‘Could not find first log file name in binary log index file‘, Error_code: 1236140405  6:53:12 [Note] Slave I/O thread exiting, read up to log ‘mysql-bin.000275‘, position 192295247140405  6:54:11 [Note] Error reading relay log event: slave SQL thread was killed140405  6:54:11 [Note] Slave I/O thread: connected to master ‘[email protected]:3306‘,replication started in log ‘mysql-bin.000275‘ at position 192295247140405  6:54:11 [ERROR] Error reading packet from server: Could not find first log file name in binary log index file ( server_errno=1236)140405  6:54:11 [ERROR] Slave I/O: Got fatal error 1236 from master when reading data from binary log: ‘Could not find first log file name in binary log index file‘, Error_code: 1236140405  6:54:11 [Note] Slave I/O thread exiting, read up to log ‘mysql-bin.000275‘, position 192295247140405  6:54:11 [Note] Slave SQL thread initialized, starting replication in log ‘mysql-bin.000275‘ at position 192295247, relay log ‘./SHUBEI-34-198-relay-bin.000153‘ position: 192295393 從指定的binlog裡找到指定的position位置，我發現這已經到頭了，之後就是切了新binlog# mysqlbinlog mysql-bin.000275 | grep -A 10 192295247 #140405  3:16:06 server id 1  end_log_pos 192295247     Xid = 468032712COMMIT/*!*/;DELIMITER ;# End of log fileROLLBACK /* added by mysqlbinlog */;/*!50003 SET [email protected]_COMPLETION_TYPE*/; 這下問題好解決了，給從庫指定新的binlog即可。 主庫show master status;mysql> show master status;+——————+———-+————–+——————+| File             | Position | Binlog_Do_DB | Binlog_Ignore_DB |+——————+———-+————–+——————+| mysql-bin.000276 |      107 |              | test             |+——————+———-+————–+——————+1 row in set (0.00 sec) 從庫重新設定複製：mysql> stop slave;Query OK, 0 rows affected (0.00 sec) mysql> change master to master_host=‘10.13.34.199‘,master_port=3306,master_user=‘rep1‘,master_password=‘RepSlavE&2013‘, master_log_file=‘mysql-bin.000276‘,master_log_pos=107; Query OK, 0 rows affected (0.05 sec) mysql> start slave;Query OK, 0 rows affected (0.00 sec) 查看主從複製狀態：mysql> show slave status\G—-省略—-             Slave_IO_Running: Yes            Slave_SQL_Running: Yes

 

———————————————————————————————————————————————————————–8、解決ERROR 1872 (HY000): Slave failed to initialize relay log info structure from the repository修改了relay-log的輸出格式之後，重啟MySQL，同步失敗 mysql> start slave;ERROR 1872 (HY000): Slave failed to initialize relay log info structure from the repository MySQL Error日誌：2014-02-20 16:35:19 27094 [ERROR] Failed to open the relay log ‘./luocs166-relay-bin.000007‘ (relay_log_pos 359).2014-02-20 16:35:19 27094 [ERROR] Could not find target log file mentioned in relay log info in the index file ‘/opt/mysql/data/anav-relay-log.index‘ during relay log initialization. 解決方案：我在查看change master to命令的時候找到如下文段mysql> ? change master to– 省略大部分The next example shows an operation that is less frequently employed.It is used when the slave has relay log files that you want it toexecute again for some reason. To do this, the master need not bereachable. You need only use CHANGE MASTER TO and start the SQL thread(START SLAVE SQL_THREAD): CHANGE MASTER TO  RELAY_LOG_FILE=‘slave-relay-bin.006‘,  RELAY_LOG_POS=4025; 但我的資料庫版本為5.6，使用了GTID模式，使用報錯：mysql> CHANGE MASTER TO    -> RELAY_LOG_FILE=‘anav-relay-log.000001‘,    -> RELAY_LOG_POS=120;ERROR 1776 (HY000): Parameters MASTER_LOG_FILE, MASTER_LOG_POS, RELAY_LOG_FILE and RELAY_LOG_POS cannot be set when MASTER_AUTO_POSITION is active. 因此如下解決：mysql> reset slave;Query OK, 0 rows affected (0.00 sec) mysql> CHANGE MASTER TO    -> MASTER_HOST=‘10.19.3.168‘,    -> MASTER_USER=‘repl2‘,    -> MASTER_PASSWORD=‘oracle‘,    -> MASTER_AUTO_POSITION = 1;Query OK, 0 rows affected, 2 warnings (0.02 sec) mysql> start slave;Query OK, 0 rows affected, 1 warning (0.01 sec) mysql> show slave status\G…. 省略部分 ….             Slave_IO_Running: Yes            Slave_SQL_Running: Yes

MYSQL問題解決