mysqldump: Couldn’t execute ‘SELECT @@GTID_MODE...
在使用MySQL 5.6的mysqldump備份5.6以前版本的MySQL時會遇到異常 mysql
mysqldump: Couldn't execute 'SELECT @@GTID_MODE': Unknown system variable 'GTID_MODE' (1193)
形成此錯誤的緣由是由於5.6引入了Global Transaction Identifiers (GTIDs) 。GTIDs可讓主從結構複製的跟蹤和比較變得簡單。mysqldump會試圖查詢這個系統變量，但這個變量在5.6以前的版本中不存在，因此產生錯誤。的方法很簡單。在mysqldump後加上–set-gtid-purged=OFF命令。 sql
mysqldump -h dbHost -u dbuser dbName --set-gtid-purged=OFF
相關文章
- 1. mysqldump: Couldn't execute 'SELECT @@GTID_MODE':
- 2. mysqldump:Couldn't execute ‘SELECT @@GTID_MODE':Un
- 3. mysqldump: Couldn't execute 'SELECT COLUMN_NAME
- 4. mysqldump: Couldn't execute 'SELECT COLUMN_NAME, JSON_EXTRACT(HISTOGRAM, '$."n
- 5. mysqldump 導出提示Couldn't execute SELECT COLUMN_NAME...
- 6. mysqldump: Couldn't execute 'show table status '解決方法
- 7. Couldn't execute 'SELECT COLUMN_NAME, JSON_EXTRACT(HISTOGRAM, '$."number-of-b
- 8. 導出提示Couldn't execute 'SELECT COLUMN_NAME,JSON_EXTRACT(HISTOGRAM, '$."number-of-buckets-specified"')
- 9. DataGrip 導出表結構和數據 mysqldump: Couldn't execute
- 10. mysqldump
- 更多相關文章...
- • PDOStatement::execute - PHP參考手冊
- • ASP Execute 方法 - ASP 教程
- • 漫談MySQL的鎖機制
- • 三篇文章瞭解 TiDB 技術內幕 —— 說計算
相關標籤/搜索
每日一句
-
每一个你不满意的现在，都有一个你没有努力的曾经。
歡迎關注本站公眾號,獲取更多信息
相關文章
- 1. mysqldump: Couldn't execute 'SELECT @@GTID_MODE':
- 2. mysqldump:Couldn't execute ‘SELECT @@GTID_MODE':Un
- 3. mysqldump: Couldn't execute 'SELECT COLUMN_NAME
- 4. mysqldump: Couldn't execute 'SELECT COLUMN_NAME, JSON_EXTRACT(HISTOGRAM, '$."n
- 5. mysqldump 導出提示Couldn't execute SELECT COLUMN_NAME...
- 6. mysqldump: Couldn't execute 'show table status '解決方法
- 7. Couldn't execute 'SELECT COLUMN_NAME, JSON_EXTRACT(HISTOGRAM, '$."number-of-b
- 8. 導出提示Couldn't execute 'SELECT COLUMN_NAME,JSON_EXTRACT(HISTOGRAM, '$."number-of-buckets-specified"')
- 9. DataGrip 導出表結構和數據 mysqldump: Couldn't execute
- 10. mysqldump